From mboxrd@z Thu Jan 1 00:00:00 1970 From: Esben Haabendal Subject: Re: [PATCH v2 3/4] i2c: imx: Simplify stopped state tracking Date: Fri, 10 Aug 2018 11:25:34 +0200 Message-ID: <87zhxuo9o1.fsf@gmail.com> References: <20180709094304.8814-1-esben.haabendal@gmail.com> <20180709094304.8814-4-esben.haabendal@gmail.com> <20180724075919.iyysd7dtbddvbavq@pengutronix.de> <87k1ozzquk.fsf@gmail.com> <20180809162652.r34omvkctzxte422@pengutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20180809162652.r34omvkctzxte422@pengutronix.de> ("Uwe =?utf-8?Q?Kleine-K=C3=B6nig=22's?= message of "Thu, 9 Aug 2018 18:26:52 +0200") Sender: linux-kernel-owner@vger.kernel.org To: Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= Cc: linux-i2c@vger.kernel.org, Wolfram Sang , Rob Herring , Mark Rutland , Yuan Yao , Philipp Zabel , Phil Reid , Lucas Stach , Clemens Gruber , Peter Rosin , Fabio Estevam , linux-kernel@vger.kernel.org List-Id: linux-i2c@vger.kernel.org Uwe Kleine-K=C3=B6nig writes: > On Thu, Aug 09, 2018 at 02:06:43PM +0200, Esben Haabendal wrote: >> Uwe Kleine-K=C3=B6nig writes: >>=20 >> > On Mon, Jul 09, 2018 at 11:43:03AM +0200, Esben Haabendal wrote: >> >> From: Esben Haabendal >> >>=20 >> >> Always update the stopped state when busy status have been checked. >> >> This is identical to what was done before, with the exception of error >> >> handling. >> >> Without this change, some errors cause the stopped state to be left in >> >> incorrect state in i2c_imx_stop(), i2c_imx_dma_read(), i2c_imx_read()= and >> >> i2c_imx_xfer(). >> >>=20 >> >> Signed-off-by: Esben Haabendal >> >> --- >> >> drivers/i2c/busses/i2c-imx.c | 12 ++++++------ >> >> 1 file changed, 6 insertions(+), 6 deletions(-) >> >>=20 >> >> diff --git a/drivers/i2c/busses/i2c-imx.c b/drivers/i2c/busses/i2c-im= x.c >> >> index d86f152176a4..1db8e6790afc 100644 >> >> --- a/drivers/i2c/busses/i2c-imx.c >> >> +++ b/drivers/i2c/busses/i2c-imx.c >> >> @@ -421,10 +421,14 @@ static int i2c_imx_bus_busy(struct imx_i2c_stru= ct *i2c_imx, int for_busy) >> >> return -EAGAIN; >> >> } >> >>=20=20 >> >> - if (for_busy && (temp & I2SR_IBB)) >> >> + if (for_busy && (temp & I2SR_IBB)) { >> >> + i2c_imx->stopped =3D 0; >> >> break; >> >> - if (!for_busy && !(temp & I2SR_IBB)) >> >> + } >> >> + if (!for_busy && !(temp & I2SR_IBB)) { >> >> + i2c_imx->stopped =3D 1; >> >> break; >> >> + } >> > >> > Would it make sense to assign to ->stopped independent of for_busy? >>=20 >> What do you mean? >>=20 >> Assigning to ->stopped on each check for I2SR_IBB in loop, independent >> of the for_busy argument? I don't think so. The additional assignments >> would be to the same value as it is set to already. > > Currently you have: > > if (for_busy && (temp & I2SR_IBB)) { > i2c_imx->stopped =3D 0; > break; > } > > if (!for_busy && !(temp & I2SR_IBB)) { > i2c_imx->stopped =3D 1; > break; > } > > The semantic of this is the same (apart from always updating .stopped) > but is imho easier: > > i2c_imx->stopped =3D !(temp & I2SR_IBB); > > if (for_busy !=3D i2c_imx->stopped) > break; Yes, that should work also. Shorter, but IMHO a bit more convoluted to read. Let me know if I should send a new version with this change. /Esben