From: Wolfram Sang <wsa@the-dreams.de>
To: Andreas Werner <wernerandy@gmx.de>
Cc: khali@linux-fr.org, jacmet@sunsite.dk, hskinnemoen@gmail.com,
dianders@chromium.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] I2C: busses: i2c-eg20t Do not print error message in syslog if no ACK received
Date: Sun, 17 Nov 2013 18:08:38 +0100 [thread overview]
Message-ID: <20131117170838.GA8577@katana> (raw)
In-Reply-To: <20131117165329.GA1562@thinkpad.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
On Sun, Nov 17, 2013 at 05:53:29PM +0100, Andreas Werner wrote:
> On Sun, Nov 17, 2013 at 01:18:09PM +0100, Wolfram Sang wrote:
> >
> > > Is there another reason why pch_i2c_getack returned EPROTO?
> > > May be ENXIO was introduced later?
> >
> > Imperfect review :)
> >
> > > I think we can just replace the -EIO with -ENXIO or do you want to pick up the return
> > > vale of pch_i2c_getack and return that ?
> >
> > The latter. As a rule of thumb, it is usually more sustainable to pass
> > through error codes. Overloading them should only be done when really
> > necessary IMO.
> >
> Ok, if that will be ok in pch_i2c_wait_for_check_xfer i will resend
> the patch.
>
> ret = pch_i2c_getack(adap);
>
> if (ret)
> pch_dbg(adap, "Receive NACK for slave address setting\n");
>
> return (int)ret;
Hmm, the cast looks ugly. Looking at the driver more closely, my
preferred solution would be to elimiate the getack function and just do
that directly in wait_for_check_xfer:
if (ioread32(adap->pch_base_address + PCH_I2CSR) & PCH_GETACK) {
pch_dbg ...
return -ENXIO;
}
Something like that...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-11-17 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 8:58 Andreas Werner
2013-11-17 11:08 ` Wolfram Sang
2013-11-17 12:39 ` Andreas Werner
2013-11-17 12:18 ` Wolfram Sang
2013-11-17 16:53 ` Andreas Werner
2013-11-17 17:08 ` Wolfram Sang [this message]
2013-11-17 17:16 ` Andreas Werner
2013-11-17 17:31 ` 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=20131117170838.GA8577@katana \
--to=wsa@the-dreams.de \
--cc=dianders@chromium.org \
--cc=hskinnemoen@gmail.com \
--cc=jacmet@sunsite.dk \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wernerandy@gmx.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
all inboxes | Powered by JetHome®