summaryrefslogtreecommitdiffstats
path: root/scripts/objdiff
diff options
context:
space:
mode:
authorBartosz Golaszewski <bartosz.golaszewski@linaro.org>2024-01-15 12:17:43 +0100
committerBartosz Golaszewski <bartosz.golaszewski@linaro.org>2024-01-17 09:52:37 +0100
commitefb8235bfdbe661c460f803150b50840a73b5f03 (patch)
tree193794eb3b6ba42ba5cd7de6ba6d2ce14a9c0e04 /scripts/objdiff
parentgpio: EN7523: fix kernel-doc warnings (diff)
downloadlinux-efb8235bfdbe661c460f803150b50840a73b5f03.tar.xz
linux-efb8235bfdbe661c460f803150b50840a73b5f03.zip
gpiolib: revert the attempt to protect the GPIO device list with an rwsem
This reverts commits 1979a2807547 ("gpiolib: replace the GPIO device mutex with a read-write semaphore") and 65a828bab158 ("gpiolib: use a mutex to protect the list of GPIO devices"). Unfortunately the legacy GPIO API that's still used in older code has to translate numbers from the global GPIO numberspace to descriptors. This results in a GPIO device lookup in every call to legacy functions. Some of those functions - like gpio_set/get_value() - can be called from atomic context so taking a sleeping lock that is an RW semaphore results in an error. We'll probably have to protect this list with SRCU. Reported-by: Dan Carpenter <dan.carpenter@linaro.org> Closes: https://lore.kernel.org/linux-wireless/f7b5ff1e-8f34-4d98-a7be-b826cb897dc8@moroto.mountain/ Fixes: 1979a2807547 ("gpiolib: replace the GPIO device mutex with a read-write semaphore") Fixes: 65a828bab158 ("gpiolib: use a mutex to protect the list of GPIO devices") Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Diffstat (limited to 'scripts/objdiff')
0 files changed, 0 insertions, 0 deletions