From: Andi Shyti <andi.shyti@kernel.org>
To: Tao Lan <taolan@huawei.com>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c-hix5hd2: Add more debug info when transfer fail.
Date: Sat, 10 Jun 2023 16:01:51 +0200 [thread overview]
Message-ID: <20230610140151.dghq3g2xw5wx6g67@intel.intel> (raw)
In-Reply-To: <20220930014405.5469-1-taolan@huawei.com>
Hi Taolan,
On Fri, Sep 30, 2022 at 01:44:05AM +0000, Tao Lan wrote:
> From: taolan <taolan@huawei.com>
>
> The transfer result is checked, classified, and printed, which
> facilitates debugging.
you are missing your Signed-off-by here.
> ---
> drivers/i2c/busses/i2c-hix5hd2.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/i2c/busses/i2c-hix5hd2.c b/drivers/i2c/busses/i2c-hix5hd2.c
> index 61ae58f57047..e6ab8b20cd01 100644
> --- a/drivers/i2c/busses/i2c-hix5hd2.c
> +++ b/drivers/i2c/busses/i2c-hix5hd2.c
> @@ -366,8 +366,17 @@ static int hix5hd2_i2c_xfer(struct i2c_adapter *adap,
> goto out;
> }
>
> - ret = num;
> + if (i == num) {
> + ret = num;
> + } else {
it can't be, because if you are exiting normally from the for
loop, then i is equal to num.
You might want to put this inside the out label, or, even better:
stop = (i == num - 1);
ret = hix5hd2_i2c_xfer_msg(priv, msgs, stop);
if (ret < 0)
- goto out;
+ break;
}
- ret = num;
+ if (i == num) {
+ ret = num;
+ } else {
+ /* Only one message, cannot access the device */
...
+ }
-out:
What do you think?
> + /* Only one message, cannot access the device */
> + if (i == 1)
> + ret = -EREMOTEIO;
> + else
> + ret = i;
>
> + pr_warning("xfer message failed\n");
please use dev_warn here.
BTW, is it warning or error?
Andi
> + }
> out:
> pm_runtime_mark_last_busy(priv->dev);
> pm_runtime_put_autosuspend(priv->dev);
> --
> 2.22.0
>
prev parent reply other threads:[~2023-06-10 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 1:44 Tao Lan
2023-06-10 14:01 ` Andi Shyti [this message]
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=20230610140151.dghq3g2xw5wx6g67@intel.intel \
--to=andi.shyti@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=taolan@huawei.com \
/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
all inboxes | Powered by JetHome®