From: Wolfram Sang <wsa@the-dreams.de>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: broonie@kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] i2c: sprd: Fix the i2c count issue
Date: Fri, 27 Apr 2018 14:14:21 +0200 [thread overview]
Message-ID: <20180427121421.fsh44y7gq3ehiqvx@ninjato> (raw)
In-Reply-To: <e42cc3e001d612e811166b8d21f44802ff20069e.1523255712.git.baolin.wang@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 369 bytes --]
On Mon, Apr 09, 2018 at 02:40:55PM +0800, Baolin Wang wrote:
> We found the I2C controller count register is unreliable sometimes,
> that will cause I2C to lose data. Thus we can read the data count
> from 'i2c_dev->count' instead of the I2C controller count register.
>
> Signed-off-by: Baolin Wang <baolin.wang@linaro.org>
Applied to for-current, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-27 12:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 6:40 [PATCH 1/2] i2c: sprd: Prevent i2c accesses after suspend is called Baolin Wang
2018-04-09 6:40 ` [PATCH 2/2] i2c: sprd: Fix the i2c count issue Baolin Wang
2018-04-27 12:14 ` Wolfram Sang [this message]
2018-04-09 20:56 ` [PATCH 1/2] i2c: sprd: Prevent i2c accesses after suspend is called Grygorii Strashko
2018-04-09 20:56 ` Grygorii Strashko
2018-04-10 8:08 ` Baolin Wang
2018-04-27 12:14 ` Wolfram Sang
2018-05-02 3:27 ` Baolin Wang
2018-05-02 5:23 ` Wolfram Sang
2018-05-02 5:48 ` Baolin Wang
2018-05-03 16:26 ` Grygorii Strashko
2018-05-03 16:26 ` Grygorii Strashko
2018-05-04 12:24 ` I2C PM overhaul needed? (Re: [PATCH 1/2] i2c: sprd: Prevent i2c accesses after suspend is called) Wolfram Sang
2018-05-05 1:54 ` Mark Brown
2018-05-05 8:32 ` Wolfram Sang
2018-05-09 8:18 ` Mark Brown
2018-05-07 17:48 ` Grygorii Strashko
2018-05-07 17:48 ` Grygorii Strashko
2018-05-08 16:32 ` Wolfram Sang
2018-05-08 18:31 ` Peter Rosin
2018-05-11 15:14 ` Grygorii Strashko
2018-05-11 15:14 ` Grygorii Strashko
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=20180427121421.fsh44y7gq3ehiqvx@ninjato \
--to=wsa@the-dreams.de \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--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.