diff options
| author | Kornel Dulęba <[email protected]> | 2023-04-21 07:06:23 -0500 |
|---|---|---|
| committer | Linus Walleij <[email protected]> | 2023-05-08 15:42:24 +0200 |
| commit | 0cf9e48ff22e15f3f0882991f33d23ccc5ae1d01 (patch) | |
| tree | eecdedcf740812c26270d27dd0c0766ba2b2e8ad /tools/perf/scripts/python/failed-syscalls-by-pid.py | |
| parent | a855724dc08b8cb0c13ab1e065a4922f1e5a7552 (diff) | |
pinctrl: amd: Detect and mask spurious interrupts
Leverage gpiochip_line_is_irq to check whether a pin has an irq
associated with it. The previous check ("irq == 0") didn't make much
sense. The irq variable refers to the pinctrl irq, and has nothing do to
with an individual pin.
On some systems, during suspend/resume cycle, the firmware leaves
an interrupt enabled on a pin that is not used by the kernel.
Without this patch that caused an interrupt storm.
Cc: [email protected]
Link: https://bugzilla.kernel.org/show_bug.cgi?id=217315
Signed-off-by: Kornel Dulęba <[email protected]>
Reviewed-by: Mario Limonciello <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Linus Walleij <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions