diff options
author | Subbaraman Narayanamurthy <subbaram@codeaurora.org> | 2021-02-11 19:14:17 -0800 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2021-02-12 12:26:46 +0100 |
commit | d19db80a366576d3ffadf2508ed876b4c1faf959 (patch) | |
tree | ca9deb8f158d49a5bbd62959ec58d844061ef656 /Documentation/driver-api/index.rst | |
parent | d77b44d0c0174708eaeaf27e8bfcb671a0225897 (diff) | |
download | linux-stable-d19db80a366576d3ffadf2508ed876b4c1faf959.tar.gz linux-stable-d19db80a366576d3ffadf2508ed876b4c1faf959.tar.bz2 linux-stable-d19db80a366576d3ffadf2508ed876b4c1faf959.zip |
spmi: spmi-pmic-arb: Fix hw_irq overflow
Currently, when handling the SPMI summary interrupt, the hw_irq
number is calculated based on SID, Peripheral ID, IRQ index and
APID. This is then passed to irq_find_mapping() to see if a
mapping exists for this hw_irq and if available, invoke the
interrupt handler. Since the IRQ index uses an "int" type, hw_irq
which is of unsigned long data type can take a large value when
SID has its MSB set to 1 and the type conversion happens. Because
of this, irq_find_mapping() returns 0 as there is no mapping
for this hw_irq. This ends up invoking cleanup_irq() as if
the interrupt is spurious whereas it is actually a valid
interrupt. Fix this by using the proper data type (u32) for id.
Cc: stable@vger.kernel.org
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
Link: https://lore.kernel.org/r/1612812784-26369-1-git-send-email-subbaram@codeaurora.org
Signed-off-by: Stephen Boyd <sboyd@kernel.org>
Link: https://lore.kernel.org/r/20210212031417.3148936-1-sboyd@kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/driver-api/index.rst')
0 files changed, 0 insertions, 0 deletions