From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux I2C <linux-i2c@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/2] i2c: rcar: Add R-Car Gen4 support
Date: Tue, 8 Feb 2022 13:35:28 +0100 [thread overview]
Message-ID: <YgJjkOqg6YL7499D@ninjato> (raw)
In-Reply-To: <CAMuHMdVVN2Jc0sYpsc=V6gfQRGXk44Uh4r=2JWhM28gF4ePASg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
> > While I2C on R-Car Gen4 does support some extra features (Slave Clock
> > Stretch Select, Fast-mode Plus), for now it is treated the same as I2C
>
> Correction: R-Car S4 does not support Fast-mode Plus, so there will be
> a v2 of this patch, eventually.
But why? Unless we implement slave clock stretching, we can still keep
it at Gen3 level. Which does also not have FM+.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-02-08 13:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 14:33 [PATCH 0/2] i2c: rcar: Add R-Car S4-8 support Geert Uytterhoeven
2022-02-03 14:33 ` [PATCH 1/2] dt-bindings: i2c: renesas,rcar-i2c: Add r8a779f0 support Geert Uytterhoeven
2022-02-10 22:15 ` Wolfram Sang
2022-02-11 14:11 ` Rob Herring
2022-02-11 17:33 ` Wolfram Sang
2022-02-03 14:33 ` [PATCH 2/2] i2c: rcar: Add R-Car Gen4 support Geert Uytterhoeven
2022-02-08 8:08 ` Geert Uytterhoeven
2022-02-08 12:35 ` Wolfram Sang [this message]
2022-02-08 14:30 ` Geert Uytterhoeven
2022-02-08 14:43 ` Wolfram Sang
2022-02-08 14:50 ` Geert Uytterhoeven
2022-02-10 22:16 ` Wolfram Sang
2022-02-11 17: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=YgJjkOqg6YL7499D@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=robh+dt@kernel.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.