diff options
| author | Pawel Osciak <posciak@chromium.org> | 2014-10-21 15:07:01 +0400 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@osg.samsung.com> | 2014-10-28 20:50:33 +0300 |
| commit | 9a7bc6b0c456bdc642269659fb13f29a8c13815b (patch) | |
| tree | 6868dd6da411436b2ac64c312c1c6bdd54d2658f /include/linux/node.h | |
| parent | 5932f74a116cf14b69b9b3e23dcaf8698151976e (diff) | |
| download | linux-9a7bc6b0c456bdc642269659fb13f29a8c13815b.tar.xz | |
[media] s5p-mfc: Don't crash the kernel if the watchdog kicks in
If the software watchdog kicks in, the watchdog worker is not synchronized
with hardware interrupts and does not block other instances. It's possible
for it to clear the hw_lock, making other instances trigger a BUG() on
hw_lock checks. Since it's not fatal to clear the hw_lock to zero twice,
just WARN in those cases for now. We should not explode, as firmware will
return errors as needed for other instances after it's reloaded, or they
will time out.
A clean fix should involve killing other instances when watchdog kicks in,
but requires a major redesign of locking in the driver.
Signed-off-by: Pawel Osciak <posciak@chromium.org>
Signed-off-by: Kiran AVND <avnd.kiran@samsung.com>
Signed-off-by: Arun Kumar K <arun.kk@samsung.com>
Signed-off-by: Kamil Debski <k.debski@samsung.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Diffstat (limited to 'include/linux/node.h')
0 files changed, 0 insertions, 0 deletions