From: Wolfram Sang <wsa@the-dreams.de>
To: Jan Glauber <jglauber@cavium.com>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
Dmitry Bazhenov <dmitry.bazhenov@auriga.com>
Subject: Re: [PATCH v2 2/2] i2c: octeon: thunderx: Limit register access retries
Date: Sat, 24 Sep 2016 11:24:36 +0200 [thread overview]
Message-ID: <20160924092436.GH1434@katana> (raw)
In-Reply-To: <1140690b8b727cd09afb9c5867983815f33a08c7.1474565039.git.jglauber@cavium.com>
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
On Fri, Sep 23, 2016 at 11:40:39AM +0200, Jan Glauber wrote:
> Do not infinitely retry register readq and writeq operations
> in order to not lock up the CPU in case the TWSI gets stuck.
>
> Return -ETIMEDOUT in case of a failed data read. For all other
> cases just return so subsequent operations will fail
> and trigger the recovery.
>
> Signed-off-by: Jan Glauber <jglauber@cavium.com>
Deleted the last 4 words from commit message (previous recovery patch
needs more discussion) and applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-09-24 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 9:40 [PATCH v2 0/2] i2c: octeon: thunderx: Recovery fixes and improvements Jan Glauber
2016-09-23 9:40 ` [PATCH v2 1/2] i2c: octeon: thunderx: Check bus state before starting a transaction Jan Glauber
2016-09-24 9:24 ` Wolfram Sang
2016-09-26 5:58 ` Jan Glauber
2016-09-26 5:58 ` Jan Glauber
2016-09-23 9:40 ` [PATCH v2 2/2] i2c: octeon: thunderx: Limit register access retries Jan Glauber
2016-09-24 9:24 ` 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=20160924092436.GH1434@katana \
--to=wsa@the-dreams.de \
--cc=dmitry.bazhenov@auriga.com \
--cc=jglauber@cavium.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@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.