zephyr/drivers/hwspinlock/CMakeLists.txt

# SPDX-License-Identifier: Apache-2.0

zephyr_library()

zephyr_library_sources_ifdef(CONFIG_SQN_HWSPINLOCK sqn_hwspinlock.c)
zephyr_library_sources_ifdef(CONFIG_USERSPACE hwspinlock_handlers.c)
drivers: introduce hardware spinlock framework The intention of hardware spinlock is to allow two processors, that have no alternative mechanism for accomplish synchronization and mutual exclusion operations, to share resources (such as memory and/or any other element). Here, we add the hwspinlock framework, that makes possible to use those hwspinlock devices and stay platform-independent. Each platform wishing to support hardware spinlock must describe a driver using this framework. Signed-off-by: Aziz Idomar <aidomar@sequans.com> 2023-06-27 08:51:04 +02:00			`# SPDX-License-Identifier: Apache-2.0`

			`zephyr_library()`

drivers: hwspinlock: implement sqn hwspinlock driver When we lock an hwspinlock, we must write the CPU identifier to the hwspinlock register. If we want to unlock the locked hwspinlock, we have to rewrite the same CPU identifier. To define the CPU identifier, we use affinity 1 and affinity 2 fields of the MPIDR register. Signed-off-by: Aziz Idomar <aidomar@sequans.com> 2023-06-27 08:47:36 +02:00			`zephyr_library_sources_ifdef(CONFIG_SQN_HWSPINLOCK sqn_hwspinlock.c)`
drivers: introduce hardware spinlock framework The intention of hardware spinlock is to allow two processors, that have no alternative mechanism for accomplish synchronization and mutual exclusion operations, to share resources (such as memory and/or any other element). Here, we add the hwspinlock framework, that makes possible to use those hwspinlock devices and stay platform-independent. Each platform wishing to support hardware spinlock must describe a driver using this framework. Signed-off-by: Aziz Idomar <aidomar@sequans.com> 2023-06-27 08:51:04 +02:00			`zephyr_library_sources_ifdef(CONFIG_USERSPACE hwspinlock_handlers.c)`