From: Wolfram Sang <wsa@the-dreams.de>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-kernel@lists.codethink.co.uk, linux-sh@vger.kernel.org,
horms+renesas@verge.net.au, linux-i2c@vger.kernel.org
Subject: Re: [PATCH 3/4] i2c: rcar: do not print error if device nacks transfer
Date: Fri, 24 Jan 2014 18:11:12 +0100 [thread overview]
Message-ID: <20140124171112.GD2629@katana> (raw)
In-Reply-To: <1389982298-23143-4-git-send-email-ben.dooks@codethink.co.uk>
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
On Fri, Jan 17, 2014 at 06:11:37PM +0000, Ben Dooks wrote:
> The i2c-rcar driver currently prints an error message if the master_xfer
> callback fails. However if the bus is being probed then lots of NAKs
> will be generated, causing the output of a number of errors printed.
>
> To solve this, disable the print if the error is not -EREMOTEIO.
Basically OK. Yet, according to 'fault-codes" it should be -ENXIO. May
be a good time to fix this as well.
Also, you might want to print for -EIO only? Or do you want to see
-EAGAIN, too?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-kernel@lists.codethink.co.uk, linux-sh@vger.kernel.org,
horms+renesas@verge.net.au, linux-i2c@vger.kernel.org
Subject: Re: [PATCH 3/4] i2c: rcar: do not print error if device nacks transfer
Date: Fri, 24 Jan 2014 17:11:12 +0000 [thread overview]
Message-ID: <20140124171112.GD2629@katana> (raw)
In-Reply-To: <1389982298-23143-4-git-send-email-ben.dooks@codethink.co.uk>
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
On Fri, Jan 17, 2014 at 06:11:37PM +0000, Ben Dooks wrote:
> The i2c-rcar driver currently prints an error message if the master_xfer
> callback fails. However if the bus is being probed then lots of NAKs
> will be generated, causing the output of a number of errors printed.
>
> To solve this, disable the print if the error is not -EREMOTEIO.
Basically OK. Yet, according to 'fault-codes" it should be -ENXIO. May
be a good time to fix this as well.
Also, you might want to print for -EIO only? Or do you want to see
-EAGAIN, too?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-24 17:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 18:11 Renesas i2c patches, R8A7790 support and Lager i2c enablemenet Ben Dooks
2014-01-17 18:11 ` [PATCH 3/4] i2c: rcar: do not print error if device nacks transfer Ben Dooks
2014-01-24 17:11 ` Wolfram Sang [this message]
2014-01-24 17:11 ` Wolfram Sang
2014-01-26 15:32 ` Ben Dooks
2014-01-26 15:57 ` Ben Dooks
2014-01-17 18:11 ` [PATCH 4/4] i2c: rcar: use devm_clk_get to ensure clock is properly ref-counted Ben Dooks
[not found] ` <1389982298-23143-5-git-send-email-ben.dooks-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>
2014-01-24 17:12 ` Wolfram Sang
2014-01-24 17:12 ` Wolfram Sang
2014-01-26 15:33 ` Ben Dooks
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=20140124171112.GD2629@katana \
--to=wsa@the-dreams.de \
--cc=ben.dooks@codethink.co.uk \
--cc=horms+renesas@verge.net.au \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-sh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.