From: Sean Anderson <sean.anderson@seco.com>
To: Joy Chakraborty <joychakr@google.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Dan Carpenter <dan.carpenter@linaro.org>
Cc: linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] rtc: abx80x: Fix return value of nvmem callback on read
Date: Thu, 13 Jun 2024 11:11:02 -0400 [thread overview]
Message-ID: <b26d352b-145f-4fdd-8e7c-2d67ef8967d7@seco.com> (raw)
In-Reply-To: <20240613120750.1455209-1-joychakr@google.com>
On 6/13/24 08:07, Joy Chakraborty wrote:
> Read callbacks registered with nvmem core expect 0 to be returned on
> success and a negative value to be returned on failure.
>
> abx80x_nvmem_xfer() on read calls i2c_smbus_read_i2c_block_data() which
> returns the number of bytes read on success as per its api description,
> this return value is handled as an error and returned to nvmem even on
> success.
Humm, I wish this were documented in nvmem-provider.h...
> Fix to handle all possible values that would be returned by
> i2c_smbus_read_i2c_block_data().
>
> Fixes: e90ff8ede777 ("rtc: abx80x: Add nvmem support")
> Cc: stable@vger.kernel.org
> Signed-off-by: Joy Chakraborty <joychakr@google.com>
> ---
> drivers/rtc/rtc-abx80x.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/rtc/rtc-abx80x.c b/drivers/rtc/rtc-abx80x.c
> index fde2b8054c2e..1298962402ff 100644
> --- a/drivers/rtc/rtc-abx80x.c
> +++ b/drivers/rtc/rtc-abx80x.c
> @@ -705,14 +705,18 @@ static int abx80x_nvmem_xfer(struct abx80x_priv *priv, unsigned int offset,
> if (ret)
> return ret;
>
> - if (write)
> + if (write) {
> ret = i2c_smbus_write_i2c_block_data(priv->client, reg,
> len, val);
> - else
> + if (ret)
> + return ret;
> + } else {
> ret = i2c_smbus_read_i2c_block_data(priv->client, reg,
> len, val);
> - if (ret)
> - return ret;
> + if (ret <= 0)
> + return ret ? ret : -EIO;
> + len = ret;
> + }
>
> offset += len;
> val += len;
Reviewed-by: Sean Anderson <sean.anderson@seco.com>
next prev parent reply other threads:[~2024-06-13 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 12:07 [PATCH v2] rtc: abx80x: Fix return value of nvmem callback on read Joy Chakraborty
2024-06-13 12:31 ` Dan Carpenter
2024-06-13 15:11 ` Sean Anderson [this message]
2024-06-21 6:23 ` Srinivas Kandagatla
2024-06-21 15:03 ` Alexandre Belloni
2024-06-21 21:21 ` Srinivas Kandagatla
2024-06-27 22:22 ` Alexandre Belloni
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=b26d352b-145f-4fdd-8e7c-2d67ef8967d7@seco.com \
--to=sean.anderson@seco.com \
--cc=alexandre.belloni@bootlin.com \
--cc=dan.carpenter@linaro.org \
--cc=joychakr@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=stable@vger.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