dev

Oopenvela-robotdrivers/spi: Delete the return value check of the nxmutex_lock.

b4605707创建于 4月21日历史提交

文件	最后提交记录	最后更新时间
CMakeLists.txt	drivers: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com>	2 个月前
Kconfig	Merge branch 'master' into vela apache/nuttx commit id: eb27ebba8adfe29644a7b890f86e6f16941921dc Signed-off-by: ligd <liguiding1@xiaomi.com> Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>	2 个月前
Make.defs	drivers: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com>	2 个月前
ice40.c	Merge branch 'master' into vela apache/nuttx commit id: eb27ebba8adfe29644a7b890f86e6f16941921dc Signed-off-by: ligd <liguiding1@xiaomi.com> Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>	2 个月前
qspi_flash.c	drivers: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com>	2 个月前
spi_bitbang.c	drivers: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com>	2 个月前
spi_driver.c	drivers/spi: Delete the return value check of the nxmutex_lock. Signed-off-by: likun17 <likun17@xiaomi.com>	2 个月前
spi_flash.c	drivers: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com>	2 个月前
spi_slave_driver.c	drivers: Avoid causing a busy loop in the program due to context switching induced by sem_post. examples: There are two threads involved: thread A with a priority of 100 and thread B with a priority of 101. Here's how they interact: When thread A releases a semaphore, thread B is scheduled to execute some code and may reacquire the semaphore. If no other tasks are ready, thread A will be scheduled to run. This continuous process can lead to a busy loop. Thread A: Thread B: while (nxsem_get_value(&priv->wait, &semcount) >= 0 && <--- semcount <= 0) | 2)context switch { 1)contex switch | nxsem_post(&priv->wait); -------------> run some code and nxsem_wait again } Signed-off-by: dongjiuzhu1 <dongjiuzhu1@xiaomi.com>	2 个月前
spi_transfer.c	drivers: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com>	2 个月前