From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Linux I2C <linux-i2c@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/5] dt-bindings: i2c: renesas,i2c: add r8a779a0 (V3U) support
Date: Sun, 17 Jan 2021 12:44:00 +0100 [thread overview]
Message-ID: <20210117114400.GF1983@ninjato> (raw)
In-Reply-To: <CAMuHMdVKmb8tCGQUQtCOfkjB3VxbVtwuA3u9kh2XuxQumKhekg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
> New features:
> - Slave Clock Stretch Select,
> - Fast Mode+ Enable,
> - Enhanced First Bit Setup Cycle configuration.
>
> Looks like the R-Car V3U variant can be treated as a generic R-Car Gen3
> variant (lacking the new features, of course).
FM+ doesn't need an update. It will just handle higher values for the
bus frequency. This is also the most likely one to be supported in
Linux. First Bit setup is not even supported yet in the basic version.
Configuration via Linux is unclear same as SlaveClockStretch. Use cases
are unclear, too, which we would need for implementating any of this.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-17 11:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 17:24 [PATCH 0/5] v3u: enable I2C0-6 Wolfram Sang
2020-12-23 17:25 ` [PATCH 1/5] dt-bindings: i2c: renesas,i2c: add r8a779a0 (V3U) support Wolfram Sang
2021-01-05 12:30 ` Geert Uytterhoeven
2021-01-17 11:44 ` Wolfram Sang [this message]
2021-01-08 2:38 ` Rob Herring
2021-01-17 11:34 ` Wolfram Sang
2020-12-23 17:25 ` [PATCH 3/5] arm64: dts: renesas: Add I2C to R8A779A0 Wolfram Sang
2021-01-05 10:49 ` Geert Uytterhoeven
2020-12-23 17:25 ` [PATCH 4/5] arm64: dts: renesas: Add I2C support for falcon board Wolfram Sang
2021-01-05 11:00 ` Geert Uytterhoeven
2021-01-12 11:46 ` Geert Uytterhoeven
2020-12-23 17:25 ` [PATCH 5/5] v3u: enable other I2C busses for testing Wolfram Sang
2021-01-05 11:02 ` Geert Uytterhoeven
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=20210117114400.GF1983@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-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).