Add support for timer kernel clock for STM32F7.
The STM32F7 RCC clock driver complies with st,stm32f4-rcc
driver variant.
Signed-off-by: Guillaume Gautier <guillaume.gautier-ext@st.com>
Add support for timer kernel clock for STM32F4.
Define a new RCC binding to add the timer prescaler property (timpre).
This new binding is used for all STM32F4 except F405/F407/F415/F417 who do
not support it.
Signed-off-by: Guillaume Gautier <guillaume.gautier-ext@st.com>
Add support for timer kernel clock for STM32F3.
Also reorganizes the timer instances:
- TIM3 is not available on F301, F318, F302x6 or x8, but is available for
all others
- TIM4 is available on F302xB and higher, F303xB and higher, F358, F398,
F373 and F378
- TIM7 is not available on F301, F318, F302, but is available for all
others
- TIM8 is only available on F303xB and higher, F358 and F398
- TIM20 is only available on F303xD and xE,and on F398
Depending of the SoC version, some timers have access to one or two
distinct clock sources. Timers with NO_SEL selection only have access
to the base TIMPLCKx clock, those defined with TIMx_SEL(0) can use another
source clock: STM32_SRC_TIMPLLCLK. That's why some clocks are redefined.
Signed-off-by: Guillaume Gautier <guillaume.gautier-ext@st.com>
This helps anchoring the file to the proper section in the online
documentation when browsing by file.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
add a missing doc + actually show up the utilities from the gpio_utils.h
header file in the doxygen documentation.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Group the vendor headers into the doxygen group used for device-specific
GPIO API extensions as opposed to have them clutter top-level GPIO docs
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Add a new doxygen group for device-specific GPIO API extensions and
put vendor header files in it.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Not all combinations of main mode and sub mode are valid, so to make it
harder to select incorrect parameters, the main mode and sub mode
enums are combined into one.
Now the user chooses any valid option in enum bt_conn_le_cs_mode.
Signed-off-by: Olivier Lesage <olivier.lesage@nordicsemi.no>
Modify the struct bt_bap_stream to have a direct reference to the
bt_iso_chan, rather than having a reference to the parent
bt_bap_iso.
This change will allow users to more easily and directly access
the bt_iso_chan, instead of getting the reference via
bt_bap_ep_get_info.
Additionally, this allows users to access the bt_iso_chan for
streams that are not codec configured, and thus not have a
bt_bap_ep reference.
Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
Expose the IDs, handles and numbers of CIGs, BIGs, CISes and BISes
via the ISO info struct. This information may be needed by higher
layer (such as the Basic Audio Profile (BAP)) or used as indexes
for arrays in the application layer.
The location of the CIG_ID, CIS_ID, BIG_Handle and BIS_Number
are moved to the location struct inside of struct bt_conn_iso
instead of being stored directly in it.
Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
The comment about which drive strength option is high or low was
wrong and this commit fixes it. For example, ESP32_GPIO_DS_ALT
results in GPIO_DRIVE_CAP_0 being used which is the weakest
option according to the HAL file espressif-esp32-gpio.h.
Signed-off-by: Hein Wessels <heinwessels93@gmail.com>
Ensure the "Video Controls" do not show up as a top level device API
but are rather folded into the main video Doxygen group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
On stm32l4+ series, the SAI1 and SAI2 clock source selection fields
are within a different register hence a different binding header
file is introduced to allow proper field usage on those platforms.
Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
Do not clutter the "Device Drivers" documentation with emulation
headers.
Ensure each emulated device API appears both in the device group as
well as "Emulator interfaces" (e.g. bbram_emul is showing up in
both BBRAM docs as well as Emulator Interfaces docs)
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
The counter that is used in Power Mode 3 to track System time could
overflow for large timeouts.
Add an API that the power system could use to ignore wakeup events
from the timer.
Signed-off-by: Mahesh Mahadevan <mahesh.mahadevan@nxp.com>
Move MAX_WAIT define to the system timer header file
so system timer drivers can use this define.
Signed-off-by: Mahesh Mahadevan <mahesh.mahadevan@nxp.com>
Put every header defined in include/zephyr/drivers/usb_c/ into the same
doxygroup (`usb_type_c`) so as to not clutter the top-level
`io_interfaces` group with multiple USB-C related groups.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
This helps anchoring the file to the proper section in the online
documentation when browsing by file.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
This helps anchoring the file to the proper section in the online
documentation when browsing by file.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
This helps anchoring the file to the proper section in the online
documentation when browsing by file.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
This helps anchoring the file to the proper section in the online
documentation when browsing by file.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
new input_interface_ext group can be used for grouping device-specific
input API extensions together.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
This helps anchoring the file to the proper section in the online
documentation when browsing by file.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
UDP multicast uploads did not produce zperf-compatible server stats,
so the client waited for and tried to decode a non-existent reply,
causing “Unexpected response flags” and misleading
“LAST PACKET NOT RECEIVED!!!” output.
This change treats multicast as client-only: after sending
the negative-id FIN it does not wait for or decode server stats,
Instead transmits the FIN a few times to help receivers detect test end.
The shell prints a clear “Statistics (client only)” summary for multicast
and suppresses the error when client stats are valid.
Unicast behavior is unchanged.
Signed-off-by: Kapil Bhatt <kapil.bhatt@nordicsemi.no>
The ADC driver API already supports ADC readings which can return signed
values, these are differential readings. In Nordic's datasheet, we have
a mode called "single ended", but its just a name. "Single ended" is a
differential reading, with the negative channel tied to GND. This is not
compatible with zephyrs definition of a single ended reading.
To support Nordic's "single ended" mode, the user must configure
a differential reading, with the negative input tied to ground, which
the saadc driver can then use to configure the reading as Nordic SAADC
"single ended", and return negative values as expected.
Signed-off-by: Jakub Zymelka <jakub.zymelka@nordicsemi.no>
This change alignes HCI drivers behavior with Host expectation. That is:
if an HCI driver managed to send a packet to Controller, the HCI driver
also unreferences it. If the HCI driver didn't manage to send the
packet to Controller and returns an error code, it does not unreferences
buffer.
This change aligns the behavior of HCI drivers with the Host's
expectations. Specifically:
- If an HCI driver successfully sends a packet to the Controller, the
HCI driver also unreferences it.
- If the HCI driver fails to send the packet to the Controller and
returns an error code, it does not unreference the buffer.
Fixes#94445
Signed-off-by: Pavel Vasilyev <pavel.vasilyev@nordicsemi.no>
