This patch fixes memory corruption that can happen when running in
multi-thread and multi-core environment with heavy scheduling stress.
In SMP configuration, we must ensure that all thread's context is
stored before writing the switch_handle flag. Otherwise some of the
thread context writes could be delayed after another CPU begins to
schedule this thread which could lead to memory corruptions.
Signed-off-by: Sylvain Chouleur <schouleur@snapchat.com>
There is an issue that the buffer cannot be allocated by the function
`read_payload()` in UART ISR context. Then the UART RX will be
disabled. The H4 driver hopes to get the receive buffer in the HCI RX
thread and then open the UART RX again. However, there is a situation
where the HCI RX thread is blocked in getting the received data
buffer. However, since the UARt RX has been disabled, the HCI RX
thread cannot get the received data buffer. Therefore, the RX thread
is always blocked here, causing the Bluetooth host to not work
properly.
Add a semaphore `rx.ready` to notify new received data buffer has
been added to H4 RX queue.
Wait for the semaphore `rx.ready` instead of H4 RX queue in HCI RX
thread.
Wake up the HCI RX thread when failing to allocate the RX buffer.
Fixes#89879.
Signed-off-by: Lyle Zhu <lyle.zhu@nxp.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Don’t insert empty lines before a dedenting };.
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Indent with tabs.
- Don’t insert empty lines before a dedenting };.
- Insert a single empty line to separate nodes at the same hierarchy level.
Also remove a few spurious space characters.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Indent with tabs.
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Don’t insert empty lines before a dedenting };.
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Indent with tabs.
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Indent with tabs.
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Insert a single empty line to separate nodes at the same hierarchy level.
By the way, also correct indentation in node stm32_lp_tick_source of
b_g474e_dpow1.dts.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Indent with tabs.
- Don’t insert empty lines before a dedenting };.
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Indent with tabs.
- Don’t insert empty lines before a dedenting };.
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Indent with tabs.
- Don’t insert empty lines before a dedenting };.
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Fix board DTS coding style issues to prevent they spread when a new
board is introduced and used this DTS as example start point.
Issues addressed from Zephyr devicetree style guidelines [1]:
- Don’t insert empty lines before a dedenting };.
- Insert a single empty line to separate nodes at the same hierarchy level.
No functional change.
Link: https://docs.zephyrproject.org/latest/contribute/style/devicetree.html [1]
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
When nvs_write is called, the nvs_flash_block_cmp is used to check if
the new data to be written matches the data already on flash. This check
always fail when CONFIG_NVS_DATA_CRC is enabled, caused by the
NVS_DATA_CRC_SIZE being added to the len parameter. The pointer to the
new data does not already have the CRC part added, while the data on
flash does, and the size to be compared includes CRC section.
By removing the addition of NVS_DATA_CRC_SIZE to the compare size, only
the data without CRC is compared, which will make the compare work in
both cases.
Signed-off-by: Yonas Alizadeh <yonas.alizadeh@alfalaval.com>
The CR bit in DISC frames should be set as a command rather than a
response.
This patch fixes the rfcomm_send_disc function to correctly use
BT_RFCOMM_CMD_CR instead of BT_RFCOMM_RESP_CR when setting the CR bit in
the address field of DISC frames.
Signed-off-by: Jiawei Yang <jiawei.yang_1@nxp.com>
Introduces one of the official flash tools for bouffalolab platforms.
Co-authored-by: Gerson Fernando Budke <nandojve@gmail.com>
Signed-off-by: Camille BAUD <mail@massdriver.space>
The original filtering condition was only whether ambient-temp0
device existed or not. However, registering ambient temp0 does
not mean that NET-related devices have been enabled.
Signed-off-by: Lucien Zhao <lucien.zhao@nxp.com>
Add support for p3t1755 temperature sensor on RT700 cm33_cpu1 core
Add net driver condition to exclude rt700 platform
Signed-off-by: Lucien Zhao <lucien.zhao@nxp.com>
Added IAR support to the macros ARCH_ISR_DIAG_OFF and
ARCH_ISR_DIAG_ON and updated the IAR warning macros.
Signed-off-by: Lars-Ove Karlsson <lars-ove.karlsson@iar.com>
The IAR C/C++ compiler can't resolve a cast on a pointer
to a constant expression. This is used in the
_ARCH_MEM_PARTITION_ALIGN_CHECK macro.
This fix checks if an IAR compiler is used and disables the
start-alignment check if it is.
This was already fixed for v7 in rev d34d554d.
Signed-off-by: Lars-Ove Karlsson <lars-ove.karlsson@iar.com>
Update hal_wch.
As the hal upstream changed name, there is now a name conflict.
Rename ch32fun.h to hal_ch32fun.h to fix this conflict.
Signed-off-by: Miguel Gazquez <miguel.gazquez@bootlin.com>
Add Variscite DART-MX93 board support. This SoM is based on NXP's
i.MX93 SoC. It includes Cortex-A55 and Cortex-M33 support.
Signed-off-by: Andre Morishita <andre.m@variscite.com>
The PR for this shield was in-flight while shield.yml was being introduced.
Add the missing file so that this shield is properly listed in the
board catalog.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Added custom mcuboot cmake for sign/encrypt by using cysecuretools
Signed-off-by: Sreeram Tatapudi <sreeram.praveen@infineon.com>
Signed-off-by: Nazar Palamar <nazar.palamar@infineon.com>
Enable support of SECURE LCS stage. In this stage, the protection
state is set to “secure”. A secured device will boot only when the
authentication of its flash boot and application code succeeds
Signed-off-by: Sreeram Tatapudi <sreeram.praveen@infineon.com>
Instead of using app_header.c generate the app header using python
script and merge with final binary post build
Signed-off-by: Sreeram Tatapudi <sreeram.praveen@infineon.com>
