Closes#94549
Removed vestigial d and d_len variables from le_adv_update()
and replaced them with a single bt_ad wrapper. This simplifies
the function while maintaining identical functionality.
Signed-off-by: Ayman Elfayoumi <aelfayoumi2@gmail.com>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for this sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Complete the Doxygen documentation for the ADLTC2990 sensor driver,
put in sensor_interface_ext group.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Re-work the Espressif supported boards documentation:
* Include repeated parts into included block
* Flatten the headers hierarchy
* Update the board variants usage.
* Fix references
Signed-off-by: Marek Matej <marek.matej@espressif.com>
Add a doxygen group for PWM api extensions and mount the now cleaned up
documentation for the MAX31790 driver into it.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Clean up some redundant or paraphrasing Doxygen comments.
Add documentation for the MIPI CSI-2 data types.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
If the GDB stub is enabled the exception handler will jump to the GDB
stub to allow remote GDB debugging.
Signed-off-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
1. Add config and overlay file in test scatter_gather for adp_xc7k_ae350
and adp_xc7k_ae350_clic to support the test case.
2. Modify the config file in test chan_blen_transfer and loop_transfer
because the tests do not support the NOCACHE memory configuration,
the DCACHE configuration needs to be disabled.
Signed-off-by: Kevin Wang <kevinwang821020@google.com>
1. Upgrade the ATCDMAC driver to make it compatible with multiple
ATCDMAC series drivers.
2. Rename the driver from ATCDMAC300 to ATCDMACX00.
Signed-off-by: Kevin Wang <kevinwang821020@google.com>
To generate the GATT Database Hash characteristic, the function
`db_hash_setup` is called. It allocates an entry for the AES key that will
be used in the CMAC calculation. Next, `db_hash_update` is called to feed
all GATT database entries into the hash. Finally, `db_hash_finish`
produces the resulting hash.
However, the AES key entry allocated in `db_hash_setup` was not being
destroyed after the hash generation completed. This caused a memory
leak, eventually leading to the error `PSA_ERROR_INSUFFICIENT_MEMORY`
(`-134`).
This commit fixes the issue by destroying the allocated AES key after
the GATT Database Hash calculation is complete, by calling
`psa_destroy_key` in `db_hash_finish`.
Signed-off-by: Pavel Vasilyev <pavel.vasilyev@nordicsemi.no>
Use CONFIG_USE_USB_AUDIO_OUTPUT instead of CONFIG_USB_DEVICE_AUDIO
when assigning USB streams, as CONFIG_USB_DEVICE_AUDIO is unused
by the sample.
Additionally the BSIM test for the sample also incorrectly used it,
so the Cmakelist.txt file was updated to correctly include sources.
Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
PocketBeagle 2 contains an MSPM0L1105 soc which emulates ADC and EEPROM.
It is connected to the AM62xx soc over I2C and SPI.
The initial support just allows building the minimal zephyr sample. Due
to the constraints and the purpose of the SOC, most peripherals should
not be enabled in the main dts.
Signed-off-by: Ayush Singh <ayush@beagleboard.org>
- Not all MSPM0L series socs seem to have MPU. After a glance at the TI
website for features, only MSPM0L222x class socs seem to have MPU.
Signed-off-by: Ayush Singh <ayush@beagleboard.org>
This commit adds support for the new cs-high-time devicetree property.
The QUADSPI_DCR_CSHT is now configured according to the value indicated
in the devicetree, for both single and dual flash modes.
Signed-off-by: Thomas Altenbach <altenbach.thomas@gmail.com>
This commit set the value of the cs-high-time property for all
STM32-based boards defined in Zephyr and having a QSPI flash memory.
The value is chosen according to the flash memory requirements (often
named 'tSHSL' in the datasheets) and the maximum QSPI frequency.
Signed-off-by: Thomas Altenbach <altenbach.thomas@gmail.com>
The STM32 QUADSPI peripheral allows to configure, in clock cycles, the
duration the chip select signal must stay high between each command sent
to the flash memory controller (QUADSPI_DCR_CSHT).
Currently, this value is set by the flash driver to 1 clock cycle in
single flash mode and 3 clock cycles in dual flash mode. However, the
minimal duration depends on the flash memory (typically 30-50 ns) and
the number of clock cycles on the QSPI's clock frequency. So, adding
this new property allows to select the value of CSHT to match the
requirement of the flash memory used. Also note that in single flash
mode, the current configuration is out-of-spec for most flash memories.
Signed-off-by: Thomas Altenbach <altenbach.thomas@gmail.com>
The QSPI 1/2 sample shift (SSHIFT) was only enabled in dual flash mode.
This feature is useful to guarantee that data is ready at the sampling
moment, even if the signals are a bit delayed due to PCB constraints.
Therefore, it should be enabled when possible (only supported in STR
mode).
Signed-off-by: Thomas Altenbach <altenbach.thomas@gmail.com>
Workaround test failures due to Zephyr Controller scheduling
overlap causing Periodic Advertising Sync timeouts, ACL
connection failed to be established or Controller assertion
when having latency at the CIS setup instant.
Workaround by using `-start_offset` to ensure that the ACL
established does not overlap the sink being established.
Relates to commit 490da9ec96 ("tests: bsim: Bluetooth:
Workaround overlapping ACL in BAP broadcast sink").
Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
Updated to test 250 ACL connections in the multiple
identity across nrf52_bsim, nrf5340bsim and nrf54l15bsim
targets.
Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
Fix assertion on BIG terminate sync and due to not receiving
terminate control procedure when there are no free buffers.
Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
IUT works as a l2cap client with basic mode. The peer device,
l2cap server with basic mode, is a PC with running bumble on it.
This test only performs the function of L2CAP basic mode.
Support multiple l2cap enerties in new shell l2cap_br,
which may support more test function.
In the test suite , there are two groups in test cases.
Group 1 Including case1-case24 focuses on connection and
disconnection around l2cap. The impact of active and passive
acl connectivity, disconnectivity and authentication as well as
disconnection from ACL without l2cap disconnect is tested.
Group2 Including case25-case31 revolves around the basic
parameters of L2CAPserver configuration, data transfer.
Case 25: Test l2cap connection with max MTU(0xffff).But the max mtu
which the stack supports is (CONFIG_BT_BUF_ACL_RX_SIZE - 4U = 196).
Case 26: Test l2cap multi_channel connection and data tranfer.
Case 27: Test l2cap connection with invaild PSM.
Case 28: Test l2cap re_connect after disconnected.
Case 29: Test l2cap connection with min MTU(0x30).set server mtu = 48,
client mtu=48. l2cap connect successfully,
both server and client mtu should be 48.
Case 30: Test l2cap connection with min MTU(0x30). set server mtu = 48,
client mtu=0x27. l2cap connect fail.
Case 31: Test l2cap connection with min MTU(0x30).set server mtu = 30,
client mtu=48.l2cap connect successfully,
both server and client mtu should be 48.
test_l2cap_client.py is a file containing real test cases.
test_l2cap_common.py is a common file. It encapsulates some
test function functions that are commonly used for test cases.
Signed-off-by: Cheng Chang <cheng.chang@nxp.com>
