From: Wolfram Sang <wsa@the-dreams.de>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Linux I2C <linux-i2c@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Hiromitsu Yamasaki <hiromitsu.yamasaki.ym@renesas.com>
Subject: Re: [RFC PATCH 1/1] i2c: rcar: handle RXDMA HW bug on Gen3
Date: Thu, 28 Jun 2018 07:13:25 +0200 [thread overview]
Message-ID: <20180628051325.pehoyggnxrqymfos@ninjato> (raw)
In-Reply-To: <OSBPR01MB229371E806C2D772B426C469D8480@OSBPR01MB2293.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 309 bytes --]
Shimoda-san,
> Please refer to "57.5.4 Usage note for the transmission and reception
> procedure" in the datasheet Rev. 1.00.
Thank you. I'll send a new version with the workaround in the i2c
driver.
> The BSP waits for maximum 1024us, not 1024ms.
You are right. Sorry, my mistake.
Regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-28 5:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 10:58 [RFC PATCH 0/1] i2c: rcar: handle RXDMA HW bug on Gen3 Wolfram Sang
2018-05-29 10:58 ` [RFC PATCH 1/1] " Wolfram Sang
2018-05-30 8:35 ` Yoshihiro Shimoda
2018-05-31 8:31 ` Wolfram Sang
2018-05-31 9:22 ` Yoshihiro Shimoda
2018-05-31 8:45 ` Geert Uytterhoeven
2018-05-31 9:12 ` Yoshihiro Shimoda
2018-06-07 5:36 ` Yoshihiro Shimoda
2018-06-07 10:08 ` Geert Uytterhoeven
2018-06-26 3:05 ` Wolfram Sang
2018-06-26 8:38 ` Yoshihiro Shimoda
2018-06-26 8:58 ` Geert Uytterhoeven
2018-06-26 9:26 ` Yoshihiro Shimoda
2018-06-27 8:44 ` Wolfram Sang
2018-06-27 8:51 ` Geert Uytterhoeven
2018-06-27 9:10 ` Wolfram Sang
2018-06-27 9:48 ` Yoshihiro Shimoda
2018-06-28 5:13 ` Wolfram Sang [this message]
2018-06-28 7:33 ` 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=20180628051325.pehoyggnxrqymfos@ninjato \
--to=wsa@the-dreams.de \
--cc=geert@linux-m68k.org \
--cc=hiromitsu.yamasaki.ym@renesas.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.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 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.