From: Jan Glauber <jglauber@cavium.com>
To: George Cherian <george.cherian@cavium.com>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
wsa@the-dreams.de
Subject: Re: [PATCHv2 1/3] i2c: xlp9xx: Check for Bus state before every transfer
Date: Tue, 6 Mar 2018 09:48:29 +0100 [thread overview]
Message-ID: <20180306084829.GB11729@wintermute> (raw)
In-Reply-To: <1519737980-27997-1-git-send-email-george.cherian@cavium.com>
I don't know how valuable same-company reviewed-by's are in the end,
but the patches look good to me with the small change in SMBalert, so you
could add:
Reviewed-by: Jan Glauber <jglauber@cavium.com>
--Jan
On Tue, Feb 27, 2018 at 01:26:18PM +0000, George Cherian wrote:
> I2C bus enters the STOP condition after the DATA_DONE interrupt is raised.
> Essentially the driver should be checking the bus state before sending
> any transaction. In case a transaction is initiated while the
> bus is busy, the prior transaction's stop condition is not achieved.
> Add the check to make sure the bus is not busy before every transaction.
>
> Signed-off-by: George Cherian <george.cherian@cavium.com>
> ---
> drivers/i2c/busses/i2c-xlp9xx.c | 32 ++++++++++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
>
> diff --git a/drivers/i2c/busses/i2c-xlp9xx.c b/drivers/i2c/busses/i2c-xlp9xx.c
> index 1f6d780..42dd1fa 100644
> --- a/drivers/i2c/busses/i2c-xlp9xx.c
> +++ b/drivers/i2c/busses/i2c-xlp9xx.c
> @@ -16,6 +16,7 @@
> #include <linux/kernel.h>
> #include <linux/module.h>
> #include <linux/platform_device.h>
> +#include <linux/delay.h>
>
> #define XLP9XX_I2C_DIV 0x0
> #define XLP9XX_I2C_CTRL 0x1
> @@ -36,6 +37,8 @@
> #define XLP9XX_I2C_TIMEOUT 0X10
> #define XLP9XX_I2C_GENCALLADDR 0x11
>
> +#define XLP9XX_I2C_STATUS_BUSY BIT(0)
> +
> #define XLP9XX_I2C_CMD_START BIT(7)
> #define XLP9XX_I2C_CMD_STOP BIT(6)
> #define XLP9XX_I2C_CMD_READ BIT(5)
> @@ -71,6 +74,7 @@
> #define XLP9XX_I2C_HIGH_FREQ 400000
> #define XLP9XX_I2C_FIFO_SIZE 0x80U
> #define XLP9XX_I2C_TIMEOUT_MS 1000
> +#define XLP9XX_I2C_BUSY_TIMEOUT 50
>
> #define XLP9XX_I2C_FIFO_WCNT_MASK 0xff
> #define XLP9XX_I2C_STATUS_ERRMASK (XLP9XX_I2C_INTEN_ARLOST | \
> @@ -241,6 +245,26 @@ static irqreturn_t xlp9xx_i2c_isr(int irq, void *dev_id)
> return IRQ_HANDLED;
> }
>
> +static int xlp9xx_i2c_check_bus_status(struct xlp9xx_i2c_dev *priv)
> +{
> + u32 status;
> + u32 busy_timeout = XLP9XX_I2C_BUSY_TIMEOUT;
> +
> + while (busy_timeout) {
> + status = xlp9xx_read_i2c_reg(priv, XLP9XX_I2C_STATUS);
> + if ((status & XLP9XX_I2C_STATUS_BUSY) == 0)
> + break;
> +
> + busy_timeout--;
> + usleep_range(1000, 1100);
> + }
> +
> + if (!busy_timeout)
> + return -EIO;
> +
> + return 0;
> +}
> +
> static int xlp9xx_i2c_init(struct xlp9xx_i2c_dev *priv)
> {
> u32 prescale;
> @@ -363,6 +387,14 @@ static int xlp9xx_i2c_xfer(struct i2c_adapter *adap, struct i2c_msg *msgs,
> int i, ret;
> struct xlp9xx_i2c_dev *priv = i2c_get_adapdata(adap);
>
> + ret = xlp9xx_i2c_check_bus_status(priv);
> + if (ret) {
> + xlp9xx_i2c_init(priv);
> + ret = xlp9xx_i2c_check_bus_status(priv);
> + if (ret)
> + return ret;
> + }
> +
> for (i = 0; i < num; i++) {
> ret = xlp9xx_i2c_xfer_msg(priv, &msgs[i], i == num - 1);
> if (ret != 0)
> --
> 2.1.4
next prev parent reply other threads:[~2018-03-06 8:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 13:26 [PATCHv2 1/3] i2c: xlp9xx: Check for Bus state before every transfer George Cherian
2018-02-27 13:26 ` [PATCH 2/3] i2c: xlp9xx: Handle NACK on DATA properly George Cherian
2018-02-27 13:26 ` [PATCH 3/3] i2c: xlp9xx: Add support for SMBAlert George Cherian
2018-03-06 8:36 ` Jan Glauber
2018-03-06 9:18 ` Phil Reid
2018-03-06 14:23 ` George Cherian
2018-03-06 8:48 ` Jan Glauber [this message]
2018-03-06 15:40 ` [PATCHv2 1/3] i2c: xlp9xx: Check for Bus state before every transfer Wolfram Sang
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=20180306084829.GB11729@wintermute \
--to=jglauber@cavium.com \
--cc=george.cherian@cavium.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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;
as well as URLs for NNTP newsgroup(s).