From: Wolfram Sang <wsa@the-dreams.de>
To: Max Schwarz <max.schwarz@online.de>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Addy Ke <addy.ke@rock-chips.com>,
heiko@sntech.de, olof@lixom.net, dianders@chromium.org,
huangtao@rock-chips.com, hl@rock-chips.com, yzq@rock-chips.com,
zyw@rock-chips.com, linux-kernel@vger.kernel.org,
kever.yang@rock-chips.com, linux-rockchip@lists.infradead.org,
xjq@rock-chips.com, linux-i2c@vger.kernel.org,
caesar.wang@rock-chips.com, cf@rock-chips.com, hj@rock-chips.com,
zhengsq@rock-chips.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] i2c: rk3x: fix bug that cause transfer fails in master receive mode
Date: Thu, 21 Aug 2014 15:12:46 -0500 [thread overview]
Message-ID: <20140821201246.GB1443@katana> (raw)
In-Reply-To: <5150326.5TB64kCfF4@typ>
[-- Attachment #1: Type: text/plain, Size: 256 bytes --]
> Actually, reads with >32 bytes of data are possible with the controller. The
> hw returns the data in 32 byte chunks. Our chunk handling code is just buggy.
Understood. Then, I'd prefer 'chunk' in the commit message instead of
'transaction'.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-08-21 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 17:50 [PATCH] i2c: rk3x: fix bug that cause transfer fails in master receive mode Addy Ke
2014-08-21 18:04 ` Sergei Shtylyov
2014-08-21 18:17 ` Wolfram Sang
2014-08-21 18:54 ` Max Schwarz
2014-08-21 20:12 ` 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=20140821201246.GB1443@katana \
--to=wsa@the-dreams.de \
--cc=addy.ke@rock-chips.com \
--cc=caesar.wang@rock-chips.com \
--cc=cf@rock-chips.com \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=hj@rock-chips.com \
--cc=hl@rock-chips.com \
--cc=huangtao@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=max.schwarz@online.de \
--cc=olof@lixom.net \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=xjq@rock-chips.com \
--cc=yzq@rock-chips.com \
--cc=zhengsq@rock-chips.com \
--cc=zyw@rock-chips.com \
/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