8a9dbb779f
Previously, extcon used the spinlock before calling the notifier_call_chain
to prevent the scheduled out of task and to prevent the notification delay.
When spinlock is locked for sending the notification, deadlock issue
occured on the side of extcon consumer device. To fix this issue,
extcon consumer device should always use the work. it is always not
reasonable to use work.
To fix this issue on extcon consumer device, release locking when sending
the notification of connector state.
Fixes:
|
||
|---|---|---|
| .. | ||
| devres.c | ||
| extcon-adc-jack.c | ||
| extcon-arizona.c | ||
| extcon-axp288.c | ||
| extcon-gpio.c | ||
| extcon-intel-cht-wc.c | ||
| extcon-intel-int3496.c | ||
| extcon-max3355.c | ||
| extcon-max8997.c | ||
| extcon-max14577.c | ||
| extcon-max77693.c | ||
| extcon-max77843.c | ||
| extcon-palmas.c | ||
| extcon-qcom-spmi-misc.c | ||
| extcon-rt8973a.c | ||
| extcon-rt8973a.h | ||
| extcon-sm5502.c | ||
| extcon-sm5502.h | ||
| extcon-usb-gpio.c | ||
| extcon-usbc-cros-ec.c | ||
| extcon.c | ||
| extcon.h | ||
| Kconfig | ||
| Makefile | ||