Utilize a code spell-checking tool to scan for and correct spelling errors
in all files within:
- `drivers/i2s`
- `drivers/i3c`
- `drivers/ieee802154`
- `drivers/input`
Signed-off-by: Pisit Sawangvonganan <pisit@ndrsolution.com>
Utilize a code spell-checking tool to scan for and correct spelling errors
in all files within:
- `drivers/clock_control`
- `drivers/counter`
- `drivers/crypto`
- `drivers/dai`
- `drivers/debug`
Signed-off-by: Pisit Sawangvonganan <pisit@ndrsolution.com>
Utilize a code spell-checking tool to scan for and correct spelling errors
in all files within:
- `drivers/adc`
- `drivers/audio`
- `drivers/bluetooth`
- `drivers/can`
- `drivers/charger`
Signed-off-by: Pisit Sawangvonganan <pisit@ndrsolution.com>
By making `MBEDTLS_PSA_CRYPTO_EXTERNAL_RNG` depend on that neither
`CTR_DRBG_CSPRNG_GENERATOR` nor `PSA_CSPRNG_GENERATOR` is enabled so if
they are we automatically fall back to `MBEDTLS_PSA_CRYPTO_LEGACY_RNG`.
This combination is problematic because we get in a scenario where
`psa_generate_random()` => `get_random_data()` => `sys_csrand_get()` =>
`psa_generate_random()`.
Resolves#105626.
Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
Drop the apa102c_bitbang sample, this does not have many reason to
exists, the rtos has an LED subsystem, an spi bitbanged driver, an
APA102 driver, and the sample make use of none of those. Drop.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
These Kconfigs were showing up in my build for a completely different
vendor. These are meant to be hidden Kconfigs meaning they do not have
descriptor strings next to their type.
Signed-off-by: Tom Burdick <thomas.burdick@infineon.com>
Turn 5 paragraphs into 2 that are more concise and easier to read, as
there was in the end not that many concepts to explain that it would
justify this many paragraphs and vertical real-estate.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
- Move the Supported Releases section to the beginning of the document as
it contains the information relevant to most users interested in e.g.
release notes for latest release.
- Consolidate release notes and migration guides into the Supported
Releases table to make information about each release all in one place.
- Moved description of Release notes and Migration guides under "Release
Lifecycle and Maintenance" section.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
We fixed oversight that did not update the compatible in the
SPI loopback driver test for Microchip MEC174x/5x boards when
the SPI driver was last updated.
Signed-off-by: Scott Worley <scott.worley@microchip.com>
This introduces the release notes and migration guide for Zephyr 4.5.0
earlier so that people have a placeholder to start adding content as
they line up pull requests for the 4.5 release.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Added unit tests for `twister_main.py` module to increase code coverage.
Did minor refactoring in `twister_main.py`.
Fixed type hints and added type ignores.
Removed unused variables.
Signed-off-by: Łukasz Fundakowski <lukasz.fundakowski@nordicsemi.no>
Signed-off-by: Lukasz Fundakowski <lukasz.fundakowski@nordicsemi.no>
reset data->scan_cb on fail, otherwise we can't
try it again, because we check it at the begining
and return when it is already set.
Signed-off-by: Fin Maaß <f.maass@vogl-electronic.com>
- add "i2c" to the .yaml for both m33 and m55 cores' supported section
- slight order adjustment for existing "i2s"
Signed-off-by: McAtee Maxwell <maxwell.mcatee@infineon.com>
This PR removes duplicate properties in the same closure. The last
instance is the one the is keept.
This PR only cleans up current instances a separate PR will be done to
update the dts-linter to enforce this in the compliance check.
Signed-off-by: Kyle Bonnici <kylebonnici@hotmail.com>
For mcxw7x platforms SECURE_STORAGE_ITS_TRANSFORM_AEAD_KEY_PROVIDER
is set by default to AEAD_KEY_PROVIDER_DEVICE_ID_HASH however the
function used to generate the key (hwinfo_get_device_eui64)
is not implemented (returns -ENOSYS) causing various
storage errors such as:
"secure_storage: Failed to transform data from storage. (-147)",
-147 is PSA_ERROR_HARDWARE_FAILURE
Switch to using AEAD_KEY_PROVIDER_ENTRY_UID_HASH to bypass this.
Signed-off-by: Andrei Menzopol <andrei.menzopol@nxp.com>
pd_mac_sap_handler gPdDataInd_c case shouldn't free msg
as it is already freed by the rx_thread. The msg is put
in rx_msgq queue through k_msgq_put which does a shallow
copy.
Signed-off-by: Andrei Menzopol <andrei.menzopol@nxp.com>
coredump_thread have a limitation and can only work if
CONFIG_MP_MAX_NUM_CPUS == 1.
This cause build issue of the test harness otherwise.
Signed-off-by: Pierre-Henry Moussay <pierre-henry.moussay@microchip.com>
SoC, DTS, and board files should live in directories named after the
vendor prefix so rename all occurrences of synaptics/ to syna/.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
nRF USBD peripheral allows only one DMA to/from isochronous endpoint in
between two SOF packets. nRF UDC driver enforces this limitation using
m_ep_ready variable that has respective endpoint bit set to 1 inside SOF
handler. While this works most of the time, there is a corner case where
the DMA can start before SOF and finish after SOF.
Prevent issuing two DMA to/from isochronous endpoint within one frame by
not setting m_ep_ready bit if isochronous endpoint DMA was active during
SOF. This avoids failed assertion for iso IN endpoint being armed and
ready at the same time.
Signed-off-by: Tomasz Moń <tomasz.mon@nordicsemi.no>
Endpoint dequeue is inherently racing against bus transactions. It is
possible that transfer finishes right before dequeue. When this happens
it was possible for the endpoint queue to be empty during xfer finished
handling. Resolve the software thread race by performing dequeue in the
same thread that handles finished transfers.
Signed-off-by: Tomasz Moń <tomasz.mon@nordicsemi.no>
Use doxygen driver_ops commands to properly document the required/optional
sensor driver operations
Assisted-by: Cursor:composer-2
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
The counter_api_get_pending_int typedef returns uint32_t, but the
public counter_get_pending_int API, its inline implementation, and
its syscall handler all return int. Several drivers return raw hardware
register bitmasks that can have upper bits set; the implicit cast to
int would make those values appear negative, which callers could
misinterpret as error codes.
Change the public API, inline impl, and syscall handler to return
uint32_t to match the driver API typedef.
Signed-off-by: Ryan McClelland <ryanmcclelland@meta.com>
Add an internal cache buffer in Intel's
adsp mtrace backend to mitigate log overwrite
issue when slot window is full.
Signed-off-by: Jun Lai <jun.lai@dolby.com>
Use doxygen driver_ops commands to properly document the required/optional
clock control driver operations
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Fixes an unused function warning when compiling with llvm, looks like
that does not fire with gcc for inline functions but it does for llvm,
tested with:
west build -p -b nrf52840dk/nrf52840 samples/subsys/usb/cdc_acm --
-DTOOLCHAIN_VARIANT_COMPILER=llvm -DCONFIG_UART_LINE_CTRL=n
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Fixes:
zephyrproject/zephyr/subsys/usb/device_next/class/usbd_hid.c:635:19:
warning: unused function 'hid_dev_set_out_polling' [-Wunused-function]
zephyrproject/zephyr/subsys/usb/device_next/class/usbd_hid.c:665:19:
warning: unused function 'hid_dev_set_in_polling' [-Wunused-function]
When compiling with LLVM:
west build -p -b nrf52840dk/nrf52840 samples/subsys/usb/hid-keyboard --
-DTOOLCHAIN_VARIANT_COMPILER=llvm
Functions are only used when CONFIG_USBD_HID_SET_POLLING_PERIOD is
enabled, set as __maybe_unused instaed of inline.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Fixes:
zephyr/drivers/usb/common/nrf_usbd_common/nrf_usbd_common.c:414:23:
warning: unused function 'ep_to_hal' [-Wunused-function]
zephyr/drivers/usb/common/nrf_usbd_common/nrf_usbd_common.c:816:22:
warning: unused function 'usbd_ep_iso_capacity' [-Wunused-function]
When compiling with LLVM:
west build -p -b nrf52840dk/nrf52840 samples/subsys/usb/hid-keyboard --
-DTOOLCHAIN_VARIANT_COMPILER=llvm
Drop ep_to_hal since it's static and unused, usbd_ep_iso_capacity is
used in an assert just flag it as maybe unused.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
When the device is connected to the host, but the application shuts down
and initialize USB device again, there will be no UDC_EVT_VBUS_READ
event generated from USB VBUS regulator on nRF52840 and nRF5340
controller. We can track the state in the driver and resubmit the event
just at the beginning of the initialization. If the device gets
disconnected in between, there will be subsequent UDC_EVT_VBUS_REMOVED
event. Perhaps it could also be solved in more generic way, but other
controllers could behave differently. Also, it could be considered that
the application should track the state of the VBUS.
Signed-off-by: Johann Fischer <johann.fischer@nordicsemi.no>
Commit increases different stack sizes and
rediuces stack usage for mesh samples
to fix falling into hardfault on start.
Signed-off-by: Aleksandr Khromykh <aleksandr.khromykh@nordicsemi.no>
Currently flexCAN initialization failed when CONFIG_CAN_FD_MODE=y is
enabled on imx9 serial platforms. So remove CAN FD compatible from
flexcan device node to disable CAN FD on these platform temporarily,
and will add it back when the formal fix is available.
Signed-off-by: Jiafei Pan <Jiafei.Pan@nxp.com>
In the following commit:
commit 69a8ac6 ("bindings: tca954x: drop child compatible")
compatible = "ti,tca9548a-channel" property is dropped from dts binding,
so drop it accordingly in imx943_evk board dts, otherwise it can't work.
Signed-off-by: Jiafei Pan <Jiafei.Pan@nxp.com>
The real RAM size from DT is correct but the power manager API expect to
receive either 192/256/320 KB value, so we need to round it up to the
next boundary to avoid powering down the top M4 SRAM bank.
Signed-off-by: Martin Hoff <martin.hoff@silabs.com>
Use doxygen driver_ops commands to properly document the required/optional
display driver operations
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
