From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Chris Brandt <chris.brandt@renesas.com>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: dts: rskrza1: Add I2C support
Date: Fri, 22 Mar 2019 11:23:25 +0100 [thread overview]
Message-ID: <20190322102324.yxnrwnkyhxrzqdg4@verge.net.au> (raw)
In-Reply-To: <20190320194410.14870-2-geert+renesas@glider.be>
On Wed, Mar 20, 2019 at 08:44:09PM +0100, Geert Uytterhoeven wrote:
> Enable the I2C bus, and add the following devices:
> - Two CAT9554 port expanders (8 GPIOs, interrupt not wired by
> default),
> - R1EX24016ASAS0A EEPROM.
>
> The bus also contains a MAX9856 Audio Codec, which is not yet supported.
>
> All devices (incl. the audio codec) are documented to support an I2C bus
> running at 400 kHz.
>
> Pinctrl is based on the RZ/A BSP.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> Pending acceptance of the DT binding patches documenting the
> "onnn,cat9554" and "renesas,r1ex24016" compatible values.
Thanks.
I'm marking this series as deferred pending acceptance of the bindings.
Please repost or ping me once that has happened.
> ---
> arch/arm/boot/dts/r7s72100-rskrza1.dts | 33 ++++++++++++++++++++++++++
> 1 file changed, 33 insertions(+)
>
> diff --git a/arch/arm/boot/dts/r7s72100-rskrza1.dts b/arch/arm/boot/dts/r7s72100-rskrza1.dts
> index 8ee44a100e9a44c4..60e80ecbbf6826bc 100644
> --- a/arch/arm/boot/dts/r7s72100-rskrza1.dts
> +++ b/arch/arm/boot/dts/r7s72100-rskrza1.dts
> @@ -47,6 +47,34 @@
> clock-frequency = <13330000>;
> };
>
> +&i2c3 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&i2c3_pins>;
> + status = "okay";
> +
> + clock-frequency = <400000>;
> +
> + io_expander1: gpio@20 {
> + compatible = "onnn,cat9554";
> + reg = <0x20>;
> + gpio-controller;
> + #gpio-cells = <2>;
> + };
> +
> + io_expander2: gpio@21 {
> + compatible = "onnn,cat9554";
> + reg = <0x21>;
> + gpio-controller;
> + #gpio-cells = <2>;
> + };
> +
> + eeprom@50 {
> + compatible = "renesas,r1ex24016", "atmel,24c16";
> + reg = <0x50>;
> + pagesize = <16>;
> + };
> +};
> +
> &usb_x1_clk {
> clock-frequency = <48000000>;
> };
> @@ -56,6 +84,11 @@
> };
>
> &pinctrl {
> + /* RIIC ch3 (Port Expander, EEPROM (MAC Addr), Audio Codec) */
> + i2c3_pins: i2c3 {
> + pinmux = <RZA1_PINMUX(1, 6, 1)>, /* RIIC3SCL */
> + <RZA1_PINMUX(1, 7, 1)>; /* RIIC3SDA */
> + };
>
> /* Serial Console */
> scif2_pins: serial2 {
> --
> 2.17.1
>
next prev parent reply other threads:[~2019-03-22 10:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 19:44 [PATCH 0/2] ARM: dts: rskrza1: Add I2C and remaining LEDs Geert Uytterhoeven
2019-03-20 19:44 ` [PATCH 1/2] ARM: dts: rskrza1: Add I2C support Geert Uytterhoeven
2019-03-22 10:23 ` Simon Horman [this message]
2019-03-25 10:55 ` Geert Uytterhoeven
2019-03-27 12:08 ` Simon Horman
2019-03-20 19:44 ` [PATCH 2/2] ARM: dts: rskrza1: Add remaining LEDs Geert Uytterhoeven
2019-03-27 12:09 ` Simon Horman
2019-03-20 20:41 ` [PATCH 0/2] ARM: dts: rskrza1: Add I2C and " Chris Brandt
2019-03-21 10:02 ` Geert Uytterhoeven
2019-03-21 12:16 ` Chris Brandt
2019-03-21 12:28 ` Geert Uytterhoeven
2019-03-22 8:23 ` Geert Uytterhoeven
2019-03-22 11:04 ` Chris Brandt
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=20190322102324.yxnrwnkyhxrzqdg4@verge.net.au \
--to=horms@verge.net.au \
--cc=chris.brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--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 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).