From: phucduc.bui@gmail.com
To: Kamal Dasu <kamal.dasu@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Andi Shyti <andi.shyti@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Wolfram Sang <wsa@kernel.org>, bui duc phuc <phucduc.bui@gmail.com>
Subject: [PATCH 0/3] Handle optional IRQs correctly
Date: Thu, 13 Aug 2026 15:52:10 +0700 [thread overview]
Message-ID: <20260813085213.44001-1-phucduc.bui@gmail.com> (raw)
From: bui duc phuc <phucduc.bui@gmail.com>
Hi all,
The changes were found through code inspection while reviewing optional
IRQ handling in I2C drivers.
I noticed that some drivers already handle the return value of
platform_get_irq_optional() explicitly, including i2c-designware-platdrv,
i2c-ocores, and i2c-sh_mobile.
This series updates the affected drivers to properly handle errors from
platform_get_irq_optional() and distinguish a missing optional IRQ from
other errors.
The series also fixes the handling of IRQ 0 in the brcmstb driver, since
0 is not a valid IRQ number returned by platform_get_irq_optional().
The series was only compile-tested.
Best regards,
Phuc
bui duc phuc (3):
i2c: pca-platform: Handle errors from optional IRQ lookup
i2c: brcmstb: Handle errors from optional IRQ lookup
i2c: brcmstb: Correct optional IRQ handling
drivers/i2c/busses/i2c-brcmstb.c | 6 ++++--
drivers/i2c/busses/i2c-pca-platform.c | 5 ++++-
2 files changed, 8 insertions(+), 3 deletions(-)
--
2.43.0
next reply other threads:[~2026-08-13 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 8:52 phucduc.bui [this message]
2026-08-13 8:52 ` [PATCH 1/3] i2c: pca-platform: Handle errors from optional IRQ lookup phucduc.bui
2026-08-13 8:52 ` [PATCH 2/3] i2c: brcmstb: " phucduc.bui
2026-08-13 8:52 ` [PATCH 3/3] i2c: brcmstb: Correct optional IRQ handling phucduc.bui
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260813085213.44001-1-phucduc.bui@gmail.com \
--to=phucduc.bui@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--cc=kamal.dasu@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox