public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Luka Perkov <luka-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Tim Harvey <tharvey-UMMOYl/HMS+akBO8gow8eQ@public.gmane.org>
Subject: Re: [PATCH] i2c: imx: retry on NAK
Date: Tue, 18 Feb 2014 18:48:53 +0100	[thread overview]
Message-ID: <20140218174853.GC18768@katana> (raw)
In-Reply-To: <1378857490-30968-1-git-send-email-luka-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 570 bytes --]

On Wed, Sep 11, 2013 at 01:58:10AM +0200, Luka Perkov wrote:
> From: Tim Harvey <tharvey-UMMOYl/HMS+akBO8gow8eQ@public.gmane.org>
> 
> In case of busy i2c try again to get ACK.
> 
> Signed-off-by: Tim Harvey <tharvey-UMMOYl/HMS+akBO8gow8eQ@public.gmane.org>
> Tested-by: Luka Perkov <luka-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>

-EAGAIN is for lost arbitration (see Documentation/i2c/fault-codes).
In that case, the core will try again. NACK needs to be reported, so the
caller can decide what to do in that case. -ENXIO would be the best
response here.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2014-02-18 17:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10 23:58 [PATCH] i2c: imx: retry on NAK Luka Perkov
     [not found] ` <1378857490-30968-1-git-send-email-luka-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
2014-02-18 17:48   ` Wolfram Sang [this message]

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=20140218174853.GC18768@katana \
    --to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=luka-p3rKhJxN3npAfugRpC6u6w@public.gmane.org \
    --cc=tharvey-UMMOYl/HMS+akBO8gow8eQ@public.gmane.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