From: Andi Shyti <andi.shyti@kernel.org>
To: Mans Rullgard <mans@mansr.com>
Cc: Oleksij Rempel <linux@rempel-privat.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: imx: add support for I2C_M_STOP flag
Date: Thu, 27 Jul 2023 22:30:45 +0200 [thread overview]
Message-ID: <20230727203045.2p7mbdtayca2hago@intel.intel> (raw)
In-Reply-To: <20230706125729.17335-1-mans@mansr.com>
Hi Mans,
on top of Oleksij's comments...
[...]
> --- a/drivers/i2c/busses/i2c-imx.c
> +++ b/drivers/i2c/busses/i2c-imx.c
> @@ -1262,10 +1262,17 @@ static int i2c_imx_xfer_common(struct i2c_adapter *adapter,
>
> /* read/write data */
> for (i = 0; i < num; i++) {
> - if (i == num - 1)
> - is_lastmsg = true;
> + if (is_lastmsg) {
> + /* previous message had I2C_M_STOP flag set */
> + temp = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2CR);
> + temp |= I2CR_MSTA;
> + imx_i2c_write_reg(temp, i2c_imx, IMX_I2C_I2CR);
> + result = i2c_imx_bus_busy(i2c_imx, 1, atomic);
> + if (result)
> + goto fail0;
> + }
>
> - if (i) {
> + if (i && !is_lastmsg) {
} else if (i) {
looks a bit simplier to me.
> dev_dbg(&i2c_imx->adapter.dev,
> "<%s> repeated start\n", __func__);
> temp = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2CR);
> @@ -1275,6 +1282,10 @@ static int i2c_imx_xfer_common(struct i2c_adapter *adapter,
> if (result)
> goto fail0;
> }
> +
> + if (i == num - 1 || (msgs[i].flags & I2C_M_STOP))
> + is_lastmsg = true;
you don't need this "i == num - 1" here.
Andi
> dev_dbg(&i2c_imx->adapter.dev,
> "<%s> transfer message: %d\n", __func__, i);
> /* write/read data */
next prev parent reply other threads:[~2023-07-27 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 12:57 [PATCH] i2c: imx: add support for I2C_M_STOP flag Mans Rullgard
2023-07-14 13:22 ` Oleksij Rempel
2023-07-27 20:30 ` Andi Shyti [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-27 18:21 Mans Rullgard
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=20230727203045.2p7mbdtayca2hago@intel.intel \
--to=andi.shyti@kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=mans@mansr.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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