Kuo-Lang Tseng 6911589c13 qmsi: pwm: Use locking mechanism to guard critical regions ... Guard critical section of the driver API, so that multiple simultaneous calls from tasks/fibers won't corrupt the driver state. The locking mechanism is by default disabled. To enable it, the following flag needs to be defined: CONFIG_PWM_QMSI_API_REENTRANCY Jira: ZEP-430 Change-Id: Ia3eb2a962f4176a3ac94163b9843ab068abe4b4e Signed-off-by: Kuo-Lang Tseng <kuo-lang.tseng@intel.com> Signed-off-by: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>		2016-07-28 15:29:49 +00:00
..
Kconfig	pwm: restructure Kconfig options	2016-03-17 21:05:12 +00:00
Kconfig.dw	pwm: unify driver names	2016-04-22 20:46:29 -04:00
Kconfig.k64	Cleanup whitespace in Kconfig files	2016-05-25 13:28:07 -05:00
Kconfig.pca9685	pwm: unify driver names	2016-04-22 20:46:29 -04:00
Kconfig.qmsi	qmsi: pwm: Use locking mechanism to guard critical regions	2016-07-28 15:29:49 +00:00
Makefile	arm: K64F Pulse Width Modulation (PWM) support	2016-03-09 15:49:44 +00:00
pwm_dw.c	pwm: unify driver names	2016-04-22 20:46:29 -04:00
pwm_k64_ftm.c	pwm/k64_ftm: convert to use DEVICE_AND_API_INIT()	2016-04-15 22:06:13 +00:00
pwm_k64_ftm.h	drivers: Replace DEV_OK by 0	2016-03-16 19:30:04 -04:00
pwm_pca9685.c	pwm/pca_9685: move driver_api assignment later	2016-04-12 11:25:03 +00:00
pwm_pca9685.h	drivers: Replace DEV_OK by 0	2016-03-16 19:30:04 -04:00
pwm_qmsi.c	qmsi: pwm: Use locking mechanism to guard critical regions	2016-07-28 15:29:49 +00:00