Correct the description in the "What Cannot be Expected to Work" section
to state that the listed functionality fails when CONFIG_MULTITHREADING
is **disabled**, as the previous wording implied the opposite.
Fixeszephyrproject-rtos/zephyr#101718
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Fixes a small typo in the example which, if copied, would result
in a error in the python file
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
gpio_pin_set_dt() return value was not assigned when pulling the
reset GPIO high, making the subsequent error check always false.
Store the return value to properly detect and report failures.
Signed-off-by: Gaetan Perrot <gaetan.perrot@spacecubics.com>
This commit replaces in the documentation of uart_tx_abort()
function, the generated event type `UART_TX_DONE` with the
correct one: `UART_TX_ABORTED`.
Signed-off-by: Sebastian Panceac <spanceac@gmail.com>
frdm_mcxaxx6: frdm_mcxa266, frdm_mcxa346, frdm_mcxa366
1. enable power_mgmt_soc test for NXP frdm_mcxaxx6 board.
2. enable systick and disable ostimer, this enabled systick
as system timer.
Signed-off-by: Zhaoxiang Jin <Zhaoxiang.Jin_1@nxp.com>
mcxaxx6: mcxa266, mcxa346, mcxa366.
1. Add power state nodes for mcxaxx6, including
sleep, deepsleep and powerdown.
2. Add power management related peripheral nodes
for mcxaxx6, including spc, cmc, vbat and wuu.
3. Add 'zephyr,cortex-m-idle-timer' node in frdm_mcxaxx6.
Signed-off-by: Zhaoxiang Jin <Zhaoxiang.Jin_1@nxp.com>
1. enable power_mgmt_soc test for NXP frdm_mcxa153 board.
2. enable systick and disable ostimer, this enabled systick
as system timer.
Signed-off-by: Zhaoxiang Jin <Zhaoxiang.Jin_1@nxp.com>
1. Add power state nodes for mcxa153, including
sleep, deepsleep and powerdown.
2. Add power management related peripheral nodes
for mcxa153, including spc, cmc, vbat and wuu.
3. Add 'zephyr,cortex-m-idle-timer' node in frdm_mcxa153.
Signed-off-by: Zhaoxiang Jin <Zhaoxiang.Jin_1@nxp.com>
1. enable power_mgmt_soc test for NXP frdm_mcxa156 board.
2. enable systick and disable ostimer, this enabled systick
as system timer.
Signed-off-by: Zhaoxiang Jin <Zhaoxiang.Jin_1@nxp.com>
1. Add power state nodes for mcxa156, including
sleep, deepsleep and powerdown.
2. Add power management related peripheral nodes
for mcxa156, including spc, cmc, vbat and wuu.
3. Add 'zephyr,cortex-m-idle-timer' node in frdm_mcxa156.
Signed-off-by: Zhaoxiang Jin <Zhaoxiang.Jin_1@nxp.com>
- Moves nxp,imx-gpt.yaml from the timer to the counter folder,
as this is the binding for the counter driver
drivers/counter/counter_mcux_gpt.c
- Fixes: #100947
Signed-off-by: Andrej Butok <andrey.butok@nxp.com>
this commit enables building and running the sample on
stm32h573i_dk board,stm32h735g_disco board, arduino_giga_r1
board, and b_u585i_iot02a board by providing the required overlay
and configuration updates.
Signed-off-by: Sara Touqan <zephyr@exalt.ps>
Signed-off-by: Sarah Younis <zephyr@exalt.ps>
Signed-off-by: Mohammad Odeh <zephyr@exalt.ps>
This commit introduces support for the mspi and ospi drivers on STM32,
enabling functionality APIs for MSPI/OSPI/QSPI host controllers..
Signed-off-by: Sara Touqan <zephyr@exalt.ps>
Signed-off-by: Sarah Younis <zephyr@exalt.ps>
Signed-off-by: Mohammad Odeh <zephyr@exalt.ps>
This commit adds the main DTS configurations required
to enable MSPI/OSPI/QSPI support on STM32.
Signed-off-by: Sara Touqan <zephyr@exalt.ps>
Signed-off-by: Sarah Younis <zephyr@exalt.ps>
Signed-off-by: Mohammad Odeh <zephyr@exalt.ps>
Raspberry pi based boards are now using binary info by default
(96b9b0f2df), and that limits pinctrl groups to 4 or 6 nodes. Split
this node in multiple groups.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
set_iir_config() dereferences the device pointer before checking it
against NULL, making the defensive check ineffective.
Remove the redundant check.
Signed-off-by: Gaetan Perrot <gaetan.perrot@spacecubics.com>
Product photo from https://learn.adafruit.com/assets/121788,
with the license CC BY-SA 3.0
Tested with the commands mentioned in index.rst
Signed-off-by: Jonas Berg <jonas.s.t.berg@gmail.com>
This patch adds support for the QSPI memory controller (for the
SiWG917 SoC) in order to enable PSRAM testing. It also adds board
overlays for this family that include PSRAM.
Signed-off-by: Martin Hoff <martin.hoff@silabs.com>
Previously, eventfd file descriptors were not being counted against the
required size for the global file descriptor table, which would result
in the function `eventfd()` (and `zvfs_eventfd()`) failing due to
insufficient resources.
Signed-off-by: Chris Friedt <chris@fr4.co>
This driver uses math functions that require the math.h header. If not
included a lot of implicit declaration warnings are generated during
build.
Signed-off-by: Tanguy Raufflet <tanguy.raufflet@savoirfairelinux.com>
This commit adds the i3c4 node to the device tree for the
STM32MP257F-EV1 and the STM32MP257F-DK boards. This node corresponds to
the i3c exposed by the GPIO expansion connector [1], [2] and not used by
the cortex A35.
According to the STM32MP257F-EV1 and STM32MP257F-DK schematics, the I3C4
are connected to the same pins as the I2C8. Therefore, both nodes cannot
be enabled together.
[1]: https://wiki.st.com/stm32mpu/wiki/STM32MP257x-EV1_-_hardware_description
[1]: https://www.st.com/resource/en/user_manual/um3385-discovery-kit-with-stm32mp257f-mpu-stmicroelectronics.pdf
Table 24. GPIO connector pinout
Co-authored-by: Charles Wenger <charles.wenger@savoirfairelinux.com>
Signed-off-by: Tanguy Raufflet <tanguy.raufflet@savoirfairelinux.com>
This commit adds the i2c8 node to the device tree for the
STM32MP257F-DK board. This node corresponds to the i2c exposed by the
GPIO expansion connector [1] and not used by the cortex A35.
[1]: https://www.st.com/resource/en/user_manual/um3385-discovery-kit-with-stm32mp257f-mpu-stmicroelectronics.pdf
Table 24. GPIO connector pinout
Co-authored-by: Charles Wenger <charles.wenger@savoirfairelinux.com>
Signed-off-by: Tanguy Raufflet <tanguy.raufflet@savoirfairelinux.com>
The I2C and SPI features have been added to the supported features for
the stm32mp257f_ev1 but were missing from the stm32mp257f_dk board file.
Co-authored-by: Charles Wenger <charles.wenger@savoirfairelinux.com>
Signed-off-by: Tanguy Raufflet <tanguy.raufflet@savoirfairelinux.com>
The I3C is now supported on the STM32MP257F-DK and STM32MP257F-EV1
boards.
Co-authored-by: Charles Wenger <charles.wenger@savoirfairelinux.com>
Signed-off-by: Tanguy Raufflet <tanguy.raufflet@savoirfairelinux.com>
Add the node I3C4 in non-secure context to dtsi. Others I3C nodes cannot
be added as they rely on EXTI1 interrupt lines that is not supported yet
for the STM32MP2.
Co-authored-by: Charles Wenger <charles.wenger@savoirfairelinux.com>
Signed-off-by: Tanguy Raufflet <tanguy.raufflet@savoirfairelinux.com>
Add reset bindings for I3C peripherals for the STM32MP2 series.
Co-authored-by: Charles Wenger <charles.wenger@savoirfairelinux.com>
Signed-off-by: Tanguy Raufflet <tanguy.raufflet@savoirfairelinux.com>
Add clock bindings for I3C peripherals for the STM32MP2 series.
Co-authored-by: Charles Wenger <charles.wenger@savoirfairelinux.com>
Signed-off-by: Tanguy Raufflet <tanguy.raufflet@savoirfairelinux.com>
Since the STM32MP2 I3C controller uses a combined interrupt line for I3C
events and errors, add the support for handling this type of interrupt
in the I3C driver.
Signed-off-by: Tanguy Raufflet <tanguy.raufflet@savoirfairelinux.com>
This adds a test case to the access BSIM tests to check that vendor
models can specify a handler for and receive messages using a
SIG-defined 1-byte opcode.
Signed-off-by: Ludvig Jordet <ludvig.jordet@nordicsemi.no>
This fixes a limitation where the stack assumed that vendor models could
not specify handlers for SIG-defined (1- or 2-byte) opcodes. This
assumption does not exist in the specification. In fact, the
specification expects this very use-case to be possible, in MeshPRT 1.1,
section 3.8.3:
> To exchange messages with a Bluetooth SIG adopted model, a Vendor Model
> shall use the Access message defined for the Bluetooth SIG model.
Signed-off-by: Ludvig Jordet <ludvig.jordet@nordicsemi.no>
This deprecates CONFIG_BT_MESH_MODEL_VND_MSG_CID_FORCE. This option was
added to allow an optimization that a) only can apply in edge case
networks that use multiple vendor models with different CIDs, b) doesn't
really have much potential gains even in this case unless there is a
large number of opcodes in these vendor models, and c) makes it
impractical to implement support for vendor models handling SIG opcodes.
Signed-off-by: Ludvig Jordet <ludvig.jordet@nordicsemi.no>
Since the entire cid checking function is conditionally included based
on KConfig, the usage site also needs to use #if instead of IS_ENABLED,
otherwise you get the following warning during compilation when the
option is disabled:
`error: implicit declaration of function
‘bt_mesh_vnd_mod_msg_cid_check’`
Signed-off-by: Ludvig Jordet <ludvig.jordet@nordicsemi.no>
Implement eeprom_target_program() using eeprom_target_write_data() and
eeprom_target_read() using eeprom_target_read_data() to limit redundant
code.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
