From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-renesas-soc@vger.kernel.org,
Andi Shyti <andi.shyti@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] i2c: rcar: introduce Gen4 devices
Date: Wed, 6 Sep 2023 22:21:35 +0200 [thread overview]
Message-ID: <ZPjfT3H42+5id0i+@shikoro> (raw)
In-Reply-To: <ZPhKxsj6VTmIlKUY@shikoro>
[-- Attachment #1: Type: text/plain, Size: 470 bytes --]
> I was reluctant to add the reset too often because my measurements back
> then showed that it costs around 5us every time. Annoying. Maybe I
> should take it easy and follow the documentation. But then I am still
> not sure if a large transfer with way more than two messages are OK
> without reset? I will ask the HW team.
Stupid me, we are following the documentation. Except that we treat the
reset property as optional while it should be mandatory for >= Gen3.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-09-06 20:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 13:58 [PATCH 0/3] i2c: rcar: add FastMode+ support Wolfram Sang
2023-09-04 13:58 ` [PATCH 1/3] i2c: rcar: avoid non-standard use of goto Wolfram Sang
2023-09-05 11:30 ` Andi Shyti
2023-09-06 6:57 ` Geert Uytterhoeven
2023-09-04 13:58 ` [PATCH 2/3] i2c: rcar: introduce Gen4 devices Wolfram Sang
2023-09-05 11:36 ` Andi Shyti
2023-09-05 14:18 ` Wolfram Sang
2023-09-05 21:21 ` Andi Shyti
2023-09-06 7:56 ` Geert Uytterhoeven
2023-09-06 9:47 ` Wolfram Sang
2023-09-06 20:21 ` Wolfram Sang [this message]
2023-09-04 13:58 ` [PATCH 3/3] i2c: rcar: add FastMode+ support Wolfram Sang
2023-09-05 21:37 ` Andi Shyti
2023-09-06 7:10 ` Wolfram Sang
2023-09-06 7:34 ` Andi Shyti
2023-09-07 7:09 ` Geert Uytterhoeven
2023-09-07 12:11 ` Wolfram Sang
2023-09-06 10:31 ` Geert Uytterhoeven
2023-09-06 12:11 ` Wolfram Sang
2023-09-06 12:23 ` Geert Uytterhoeven
2023-09-06 13:07 ` 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=ZPjfT3H42+5id0i+@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=andi.shyti@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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.