From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
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: Tue, 5 Jan 2021 13:30:40 +0100 [thread overview]
Message-ID: <CAMuHMdVKmb8tCGQUQtCOfkjB3VxbVtwuA3u9kh2XuxQumKhekg@mail.gmail.com> (raw)
In-Reply-To: <20201223172505.34736-2-wsa+renesas@sang-engineering.com>
On Wed, Dec 23, 2020 at 6:27 PM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> --- a/Documentation/devicetree/bindings/i2c/renesas,i2c.txt
> +++ b/Documentation/devicetree/bindings/i2c/renesas,i2c.txt
> @@ -26,6 +26,7 @@ Required properties:
> "renesas,i2c-r8a77980" if the device is a part of a R8A77980 SoC.
> "renesas,i2c-r8a77990" if the device is a part of a R8A77990 SoC.
> "renesas,i2c-r8a77995" if the device is a part of a R8A77995 SoC.
> + "renesas,i2c-r8a779a0" if the device is a part of a R8A779A0 SoC.
> "renesas,rcar-gen1-i2c" for a generic R-Car Gen1 compatible device.
> "renesas,rcar-gen2-i2c" for a generic R-Car Gen2 or RZ/G1 compatible
> device.
Note that this doesn't say anything about (in)compatibility with generic
R-Car Gen3 compatible devices (hint: yaml conversion?).
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).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2021-01-05 12:32 UTC|newest]
Thread overview: 15+ 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 [this message]
2021-01-17 11:44 ` Wolfram Sang
2021-01-08 2:38 ` Rob Herring
2021-01-17 11:34 ` Wolfram Sang
2020-12-23 17:25 ` [PATCH 2/5] clk: renesas: r8a779a0: add clocks for I2C Wolfram Sang
2021-01-05 10:40 ` Geert Uytterhoeven
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=CAMuHMdVKmb8tCGQUQtCOfkjB3VxbVtwuA3u9kh2XuxQumKhekg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=devicetree@vger.kernel.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 \
--cc=wsa+renesas@sang-engineering.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 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).