From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@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 5/5] v3u: enable other I2C busses for testing
Date: Tue, 5 Jan 2021 12:02:12 +0100 [thread overview]
Message-ID: <CAMuHMdUeKSMFGgQOVXSPfhhg6PimVdFbQ=A=dEY4Y6UuhrsCbA@mail.gmail.com> (raw)
In-Reply-To: <20201223172505.34736-6-wsa+renesas@sang-engineering.com>
Hi Wolfram,
On Wed, Dec 23, 2020 at 6:25 PM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> Not for upstream!
>
> Not-Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Thanks for your patch!
> --- a/arch/arm64/boot/dts/renesas/r8a779a0-falcon.dts
> +++ b/arch/arm64/boot/dts/renesas/r8a779a0-falcon.dts
> @@ -37,6 +37,46 @@ &i2c1 {
> clock-frequency = <400000>;
> };
>
> +&i2c2 {
> + pinctrl-0 = <&i2c2_pins>;
> + pinctrl-names = "default";
> +
> + status = "okay";
> + clock-frequency = <100000>;
> +};
> +
> +&i2c3 {
> + pinctrl-0 = <&i2c3_pins>;
> + pinctrl-names = "default";
> +
> + status = "okay";
> + clock-frequency = <100000>;
> +};
> +
> +&i2c4 {
> + pinctrl-0 = <&i2c4_pins>;
> + pinctrl-names = "default";
> +
> + status = "okay";
> + clock-frequency = <100000>;
> +};
> +
> +&i2c5 {
> + pinctrl-0 = <&i2c5_pins>;
> + pinctrl-names = "default";
> +
> + status = "okay";
> + clock-frequency = <100000>;
> +};
> +
> +&i2c6 {
> + pinctrl-0 = <&i2c6_pins>;
> + pinctrl-names = "default";
> +
> + status = "okay";
> + clock-frequency = <100000>;
> +};
I think the i2c6 part belongs to "[PATCH 4/5] arm64: dts: renesas: Add
I2C support for falcon board",
possibly with clock-frequency = <400000>.
> +
> &pfc {
> i2c0_pins: i2c0 {
> groups = "i2c0";
> @@ -47,6 +87,31 @@ i2c1_pins: i2c1 {
> groups = "i2c1";
> function = "i2c1";
> };
> +
> + i2c2_pins: i2c2 {
> + groups = "i2c2";
> + function = "i2c2";
> + };
> +
> + i2c3_pins: i2c3 {
> + groups = "i2c3";
> + function = "i2c3";
> + };
> +
> + i2c4_pins: i2c4 {
> + groups = "i2c4";
> + function = "i2c4";
> + };
> +
> + i2c5_pins: i2c5 {
> + groups = "i2c5";
> + function = "i2c5";
> + };
> +
> + i2c6_pins: i2c6 {
> + groups = "i2c6";
> + function = "i2c6";
> + };
Likewise.
> };
>
> &rwdt {
> --
> 2.28.0
>
--
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
prev parent reply other threads:[~2021-01-05 11:03 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
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 [this message]
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='CAMuHMdUeKSMFGgQOVXSPfhhg6PimVdFbQ=A=dEY4Y6UuhrsCbA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--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).