From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Wolfram Sang <wsa@the-dreams.de>,
Magnus Damm <magnus.damm@gmail.com>,
Linux I2C <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH 4/6] arm64: renesas: draak: enable I2C controller 0 and EEPROM
Date: Thu, 16 Nov 2017 10:27:56 +0100 [thread overview]
Message-ID: <CAMuHMdWmZEoNGRjsumOc+yPe3JTCBobVZd8arzUfcymjF0imDA@mail.gmail.com> (raw)
In-Reply-To: <1510759526-30346-5-git-send-email-ulrich.hecht+renesas@gmail.com>
Hi Ulrich,
On Wed, Nov 15, 2017 at 4:25 PM, Ulrich Hecht
<ulrich.hecht+renesas@gmail.com> wrote:
> Enables EEPROM on I2C0 on the Draak board.
>
> Signed-off-by: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
Thanks for your patch!
> --- a/arch/arm64/boot/dts/renesas/r8a77995-draak.dts
> +++ b/arch/arm64/boot/dts/renesas/r8a77995-draak.dts
> @@ -67,6 +72,18 @@
> };
> };
>
> +&i2c0 {
> + pinctrl-0 = <&i2c0_pins>;
> + pinctrl-names = "default";
> + status = "okay";
> +
> + eeprom@50 {
> + compatible = "atmel,24c01";
This is actually a ROHM Semiconductor BR24T01FVM-W, so it should be
compatible = "rohm,br24t01", "atmel,24c01";
Please also submit a patch to add that compatible value to
Documentation/devicetree/bindings/eeprom/eeprom.txt.
With the above fixed:
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
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:[~2017-11-16 9:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 15:25 [PATCH 0/6] R-Car D3 (r8a77995) I2C integration Ulrich Hecht
2017-11-15 15:25 ` [PATCH 1/6] pinctrl: sh-pfc: r8a77995: add missing pins SCL0 and SDA0 to pinmux data Ulrich Hecht
2017-11-16 8:53 ` Geert Uytterhoeven
2017-11-15 15:25 ` [PATCH 2/6] i2c: rcar: enable for R-Car D3 (r8a77995) Ulrich Hecht
2017-11-16 8:54 ` Geert Uytterhoeven
2017-11-15 15:25 ` [PATCH 3/6] arm64: renesas: r8a77995: add I2C support Ulrich Hecht
2017-11-16 9:10 ` Geert Uytterhoeven
2017-11-17 14:28 ` Simon Horman
2018-01-19 10:32 ` Kieran Bingham
2018-01-17 17:21 ` Kieran Bingham
2017-11-15 15:25 ` [PATCH 4/6] arm64: renesas: draak: enable I2C controller 0 and EEPROM Ulrich Hecht
2017-11-16 9:27 ` Geert Uytterhoeven [this message]
2017-11-17 14:31 ` Simon Horman
2017-11-17 16:39 ` Simon Horman
2018-01-19 10:34 ` Kieran Bingham
2017-11-15 15:25 ` [PATCH 5/6] arm64: renesas: draak: enable I2C controller 1 Ulrich Hecht
2017-11-16 9:31 ` Geert Uytterhoeven
2017-11-17 14:32 ` Simon Horman
2017-11-17 16:40 ` Simon Horman
2018-01-29 15:46 ` Ulrich Hecht
2017-11-15 15:25 ` [PATCH 6/6] i2c: rcar: document R8A77970 bindings Ulrich Hecht
2017-11-16 8:55 ` Geert Uytterhoeven
2017-12-04 21:33 ` [PATCH 0/6] R-Car D3 (r8a77995) I2C integration 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=CAMuHMdWmZEoNGRjsumOc+yPe3JTCBobVZd8arzUfcymjF0imDA@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=ulrich.hecht+renesas@gmail.com \
--cc=wsa@the-dreams.de \
/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).