[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160513115021.GK1778@katana>
Date: Fri, 13 May 2016 13:50:21 +0200
From: Wolfram Sang <wsa@...-dreams.de>
To: Sricharan R <sricharan@...eaurora.org>
Cc: devicetree@...r.kernel.org, architt@...eaurora.org,
linux-arm-msm@...r.kernel.org, ntelkar@...eaurora.org,
galak@...eaurora.org, linux-kernel@...r.kernel.org,
andy.gross@...aro.org, linux-i2c@...r.kernel.org,
iivanov@...sol.com, agross@...eaurora.org,
dmaengine@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
nkaje@...eaurora.org
Subject: Re: [PATCH V2 2/2] drivers: i2c: qup: Fix error handling
On Fri, May 13, 2016 at 01:48:23PM +0200, Wolfram Sang wrote:
> On Fri, May 06, 2016 at 05:01:14PM +0530, Sricharan R wrote:
> > Among the bus errors reported from the QUP_MASTER_STATUS register
> > only NACK is considered and transfer gets suspended, while
> > other errors are ignored. Correct this and suspend the transfer
> > for other errors as well. This avoids unnessecary 'timeouts' which
> > happens when waiting for events that would never happen when there
> > is already an error condition on the bus.
> >
> > Signed-off-by: Sricharan R <sricharan@...eaurora.org>
> > Reviewed-by: Andy Gross <andy.gross@...aro.org>
>
> Please check Documentation/i2c/fault-codes for proper fault codes.
And while we are here: NACK is not an error but a valid response. Can
you remove the dev_err related to that? Otherwise tools like i2cdetect
will probably flood your log.
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists