From: Tom Rix <trix@redhat.com>
To: heikki.krogerus@linux.intel.com, gregkh@linuxfoundation.org,
nathan@kernel.org, ndesaulniers@google.com, sven@svenpeter.dev,
alyssa@rosenzweig.io, marcan@marcan.st, martink@posteo.de,
saranya.gopal@intel.com
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, Tom Rix <trix@redhat.com>
Subject: [PATCH] usb: typec: tipd: improve handling of failures in interrupt handlers
Date: Sat, 9 Apr 2022 09:00:13 -0400 [thread overview]
Message-ID: <20220409130013.1474412-1-trix@redhat.com> (raw)
clang static analysis reports this representative issue
core.c:516:6: warning: Branch condition evaluates
to a garbage value
if (event)
^~~~~
In cd321x_interrupt(), a successful call to
tps6598x_read64() is the only way event is set,
and if a failure happens the irq should not be
reported as handled.
Instead of initializing event, rework the
usage of ret by initializing it to IRQ_NONE
and then setting it when event is known to
be not zero. This removes the if-statement
before the return.
tps6598x_interrupt() is similar.
Fixes: 0a4c005bd171 ("usb: typec: driver for TI TPS6598x USB Power Delivery controllers")
Signed-off-by: Tom Rix <trix@redhat.com>
---
drivers/usb/typec/tipd/core.c | 24 +++++++++++-------------
1 file changed, 11 insertions(+), 13 deletions(-)
diff --git a/drivers/usb/typec/tipd/core.c b/drivers/usb/typec/tipd/core.c
index 16b4560216ba..88a20cc15da4 100644
--- a/drivers/usb/typec/tipd/core.c
+++ b/drivers/usb/typec/tipd/core.c
@@ -478,12 +478,11 @@ static irqreturn_t cd321x_interrupt(int irq, void *data)
struct tps6598x *tps = data;
u64 event;
u32 status;
- int ret;
+ int ret = IRQ_NONE;
mutex_lock(&tps->lock);
- ret = tps6598x_read64(tps, TPS_REG_INT_EVENT1, &event);
- if (ret) {
+ if (tps6598x_read64(tps, TPS_REG_INT_EVENT1, &event)) {
dev_err(tps->dev, "%s: failed to read events\n", __func__);
goto err_unlock;
}
@@ -492,6 +491,8 @@ static irqreturn_t cd321x_interrupt(int irq, void *data)
if (!event)
goto err_unlock;
+ ret = IRQ_HANDLED;
+
if (!tps6598x_read_status(tps, &status))
goto err_clear_ints;
@@ -513,9 +514,7 @@ static irqreturn_t cd321x_interrupt(int irq, void *data)
err_unlock:
mutex_unlock(&tps->lock);
- if (event)
- return IRQ_HANDLED;
- return IRQ_NONE;
+ return ret;
}
static irqreturn_t tps6598x_interrupt(int irq, void *data)
@@ -524,13 +523,12 @@ static irqreturn_t tps6598x_interrupt(int irq, void *data)
u64 event1;
u64 event2;
u32 status;
- int ret;
+ int ret = IRQ_NONE;
mutex_lock(&tps->lock);
- ret = tps6598x_read64(tps, TPS_REG_INT_EVENT1, &event1);
- ret |= tps6598x_read64(tps, TPS_REG_INT_EVENT2, &event2);
- if (ret) {
+ if (tps6598x_read64(tps, TPS_REG_INT_EVENT1, &event1) ||
+ tps6598x_read64(tps, TPS_REG_INT_EVENT2, &event2)) {
dev_err(tps->dev, "%s: failed to read events\n", __func__);
goto err_unlock;
}
@@ -539,6 +537,8 @@ static irqreturn_t tps6598x_interrupt(int irq, void *data)
if (!(event1 | event2))
goto err_unlock;
+ ret = IRQ_HANDLED;
+
if (!tps6598x_read_status(tps, &status))
goto err_clear_ints;
@@ -561,9 +561,7 @@ static irqreturn_t tps6598x_interrupt(int irq, void *data)
err_unlock:
mutex_unlock(&tps->lock);
- if (event1 | event2)
- return IRQ_HANDLED;
- return IRQ_NONE;
+ return ret;
}
static int tps6598x_check_mode(struct tps6598x *tps)
--
2.27.0
next reply other threads:[~2022-04-09 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 13:00 Tom Rix [this message]
2022-04-12 21:42 ` [PATCH] usb: typec: tipd: improve handling of failures in interrupt handlers Nathan Chancellor
2022-04-21 16:24 ` Greg KH
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=20220409130013.1474412-1-trix@redhat.com \
--to=trix@redhat.com \
--cc=alyssa@rosenzweig.io \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=marcan@marcan.st \
--cc=martink@posteo.de \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=saranya.gopal@intel.com \
--cc=sven@svenpeter.dev \
/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