From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] i2c: rk3x: fix bug that cause transfer fails in master receive mode
Date: Tue, 2 Sep 2014 13:01:59 +0200 [thread overview]
Message-ID: <20140902110159.GF1266@katana> (raw)
In-Reply-To: <1408730452-3552-1-git-send-email-addy.ke@rock-chips.com>
On Sat, Aug 23, 2014 at 02:00:52AM +0800, Addy Ke wrote:
> In rk3x SOC, the I2C controller can receive/transmit up to 32 bytes data
> in one chunk, so the size of data to be write/read to/from TXDATAx/RXDATAx
> must be less than or equal 32 bytes at a time.
>
> Tested on rk3288-pinky board, elan receive 158 bytes data.
>
> Suggested-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Signed-off-by: Addy Ke <addy.ke@rock-chips.com>
> Acked-by: Max Schwarz <max.schwarz@online.de>
Applied to for-current, thanks! Please don't send new versions of a
patch as reply-to of a previous version.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140902/b1524370/attachment.sig>
next prev parent reply other threads:[~2014-09-02 11:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0001-i2c-rk3x-fix-bug-that-cause-transfer-fails-in-master.patch>
2014-08-21 21:38 ` [PATCH v2] i2c: rk3x: fix bug that cause transfer fails in maste receive mode Addy Ke
2014-08-22 1:13 ` [PATCH v3] i2c: rk3x: fix bug that cause transfer fails in master " Addy Ke
2014-08-22 1:15 ` Doug Anderson
2014-08-22 16:16 ` Dmitry Torokhov
2014-08-22 18:00 ` [PATCH v4] " Addy Ke
2014-08-22 18:33 ` Doug Anderson
2014-08-22 18:47 ` addy ke
2014-08-22 20:04 ` Doug Anderson
2014-09-02 11:01 ` Wolfram Sang [this message]
2014-08-22 1:14 ` [PATCH v2] i2c: rk3x: fix bug that cause transfer fails in maste " Doug Anderson
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=20140902110159.GF1266@katana \
--to=wsa@the-dreams.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).