From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Sergei Shtylyov
<sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
Cc: Addy Ke <addy.ke-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
max.schwarz-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org,
heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org,
olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org,
dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
huangtao-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
hl-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
yzq-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
zyw-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kever.yang-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
xjq-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
caesar.wang-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
cf-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
hj-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] i2c: rk3x: fix bug that cause transfer fails in master receive mode
Date: Thu, 21 Aug 2014 13:17:38 -0500 [thread overview]
Message-ID: <20140821181738.GA1443@katana> (raw)
In-Reply-To: <53F634AF.1010303-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]
On Thu, Aug 21, 2014 at 10:04:31PM +0400, Sergei Shtylyov wrote:
> Hello.
>
> On 08/21/2014 09:50 PM, Addy Ke wrote:
>
> >In rk3x SOC, the I2C controller can receive/transmit up to 32 bytes data
> >in one transaction, so the size of data to be write/read to/from
> >TXDATAx/RXDATAx must be less than or equal 32 bytes at a time.
>
> >Test on pinky board, elan receive 158 bytes data.
>
> >Signed-off-by: Addy Ke <addy.ke-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
> >---
> > drivers/i2c/busses/i2c-rk3x.c | 3 +++
> > 1 file changed, 3 insertions(+)
>
> >diff --git a/drivers/i2c/busses/i2c-rk3x.c b/drivers/i2c/busses/i2c-rk3x.c
> >index 69e1185..dc0aa64 100644
> >--- a/drivers/i2c/busses/i2c-rk3x.c
> >+++ b/drivers/i2c/busses/i2c-rk3x.c
> >@@ -323,6 +323,9 @@ static void rk3x_i2c_handle_read(struct rk3x_i2c *i2c, unsigned int ipd)
> > /* ack interrupt */
> > i2c_writel(i2c, REG_INT_MBRF, REG_IPD);
> >
> >+ /* Can only handle a maximum of 32 bytes at a time */
> >+ len = (len > 32) ? 32 : len;
>
> Why not min(len, 32)? Or even:
>
> if (len > 32)
> len = 32;
No silent trimming, please. The message should be rejected when the transfer is
set up. We could assign -EOVERFLOW to that type of failures, so users
will know. Sadly, I have seen other controllers having such limits :(
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c: rk3x: fix bug that cause transfer fails in master receive mode
Date: Thu, 21 Aug 2014 13:17:38 -0500 [thread overview]
Message-ID: <20140821181738.GA1443@katana> (raw)
In-Reply-To: <53F634AF.1010303@cogentembedded.com>
On Thu, Aug 21, 2014 at 10:04:31PM +0400, Sergei Shtylyov wrote:
> Hello.
>
> On 08/21/2014 09:50 PM, Addy Ke wrote:
>
> >In rk3x SOC, the I2C controller can receive/transmit up to 32 bytes data
> >in one transaction, so the size of data to be write/read to/from
> >TXDATAx/RXDATAx must be less than or equal 32 bytes at a time.
>
> >Test on pinky board, elan receive 158 bytes data.
>
> >Signed-off-by: Addy Ke <addy.ke@rock-chips.com>
> >---
> > drivers/i2c/busses/i2c-rk3x.c | 3 +++
> > 1 file changed, 3 insertions(+)
>
> >diff --git a/drivers/i2c/busses/i2c-rk3x.c b/drivers/i2c/busses/i2c-rk3x.c
> >index 69e1185..dc0aa64 100644
> >--- a/drivers/i2c/busses/i2c-rk3x.c
> >+++ b/drivers/i2c/busses/i2c-rk3x.c
> >@@ -323,6 +323,9 @@ static void rk3x_i2c_handle_read(struct rk3x_i2c *i2c, unsigned int ipd)
> > /* ack interrupt */
> > i2c_writel(i2c, REG_INT_MBRF, REG_IPD);
> >
> >+ /* Can only handle a maximum of 32 bytes at a time */
> >+ len = (len > 32) ? 32 : len;
>
> Why not min(len, 32)? Or even:
>
> if (len > 32)
> len = 32;
No silent trimming, please. The message should be rejected when the transfer is
set up. We could assign -EOVERFLOW to that type of failures, so users
will know. Sadly, I have seen other controllers having such limits :(
-------------- 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/20140821/d4ec6cd6/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Addy Ke <addy.ke@rock-chips.com>,
max.schwarz@online.de, 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 13:17:38 -0500 [thread overview]
Message-ID: <20140821181738.GA1443@katana> (raw)
In-Reply-To: <53F634AF.1010303@cogentembedded.com>
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
On Thu, Aug 21, 2014 at 10:04:31PM +0400, Sergei Shtylyov wrote:
> Hello.
>
> On 08/21/2014 09:50 PM, Addy Ke wrote:
>
> >In rk3x SOC, the I2C controller can receive/transmit up to 32 bytes data
> >in one transaction, so the size of data to be write/read to/from
> >TXDATAx/RXDATAx must be less than or equal 32 bytes at a time.
>
> >Test on pinky board, elan receive 158 bytes data.
>
> >Signed-off-by: Addy Ke <addy.ke@rock-chips.com>
> >---
> > drivers/i2c/busses/i2c-rk3x.c | 3 +++
> > 1 file changed, 3 insertions(+)
>
> >diff --git a/drivers/i2c/busses/i2c-rk3x.c b/drivers/i2c/busses/i2c-rk3x.c
> >index 69e1185..dc0aa64 100644
> >--- a/drivers/i2c/busses/i2c-rk3x.c
> >+++ b/drivers/i2c/busses/i2c-rk3x.c
> >@@ -323,6 +323,9 @@ static void rk3x_i2c_handle_read(struct rk3x_i2c *i2c, unsigned int ipd)
> > /* ack interrupt */
> > i2c_writel(i2c, REG_INT_MBRF, REG_IPD);
> >
> >+ /* Can only handle a maximum of 32 bytes at a time */
> >+ len = (len > 32) ? 32 : len;
>
> Why not min(len, 32)? Or even:
>
> if (len > 32)
> len = 32;
No silent trimming, please. The message should be rejected when the transfer is
set up. We could assign -EOVERFLOW to that type of failures, so users
will know. Sadly, I have seen other controllers having such limits :(
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-21 18:17 UTC|newest]
Thread overview: 13+ 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 17:50 ` Addy Ke
2014-08-21 18:04 ` Sergei Shtylyov
2014-08-21 18:04 ` Sergei Shtylyov
[not found] ` <53F634AF.1010303-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2014-08-21 18:17 ` Wolfram Sang [this message]
2014-08-21 18:17 ` Wolfram Sang
2014-08-21 18:17 ` Wolfram Sang
2014-08-21 18:54 ` Max Schwarz
2014-08-21 18:54 ` Max Schwarz
2014-08-21 18:54 ` Max Schwarz
2014-08-21 20:12 ` Wolfram Sang
2014-08-21 20:12 ` Wolfram Sang
2014-08-21 20:12 ` Wolfram Sang
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=20140821181738.GA1443@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=addy.ke-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=caesar.wang-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=cf-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
--cc=hj-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=hl-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=huangtao-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=kever.yang-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=max.schwarz-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org \
--cc=xjq-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=yzq-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=zyw-TNX95d0MmH7DzftRWevZcw@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 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.