From: Johan Jonker <jbx6244@gmail.com>
To: Tianling Shen <cnsztl@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Marty Jones <mj8263788@gmail.com>, Pavel Machek <pavel@ucw.cz>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: add EEPROM node for NanoPi R4S
Date: Mon, 7 Jun 2021 11:14:23 +0200 [thread overview]
Message-ID: <9258ab23-ef65-2c3d-f0d2-ca5f77d7c12a@gmail.com> (raw)
In-Reply-To: <20210607081727.4723-1-cnsztl@gmail.com>
Hi Tianling,
On 6/7/21 10:17 AM, Tianling Shen wrote:
> NanoPi R4S has a EEPROM attached to the 2nd I2C bus (U92), which
> stores the MAC address.
>
> Signed-off-by: Tianling Shen <cnsztl@gmail.com>
> ---
> arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts b/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts
> index cef4d18b599d..4a82f50a07c5 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts
> @@ -68,6 +68,15 @@
> status = "disabled";
> };
>
> +&i2c2 {
> + eeprom@51 {
> + compatible = "microchip,24c02", "atmel,24c02";
> + reg = <0x51>;
> + pagesize = <16>;
> + read-only; /* This holds our MAC */
The mainline dts files should be generic I think.
Any comment about "use", partitions or write ability should be avoided.
It's up the user.
Johan
> + };
> +};
> +
> &i2c4 {
> status = "disabled";
> };
>
next prev parent reply other threads:[~2021-06-07 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 8:17 [PATCH] arm64: dts: rockchip: add EEPROM node for NanoPi R4S Tianling Shen
2021-06-07 8:35 ` Chen-Yu Tsai
2021-06-07 12:48 ` Tianling Shen
2021-06-07 9:14 ` Johan Jonker [this message]
2021-06-07 9:40 ` Chen-Yu Tsai
2021-06-07 10:26 ` Johan Jonker
2021-06-07 11:20 ` Chen-Yu Tsai
2021-06-07 16:01 ` Tianling Shen
2021-06-07 17:04 ` Johan Jonker
2021-06-07 17:08 ` Chen-Yu Tsai
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=9258ab23-ef65-2c3d-f0d2-ca5f77d7c12a@gmail.com \
--to=jbx6244@gmail.com \
--cc=cnsztl@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mj8263788@gmail.com \
--cc=pavel@ucw.cz \
--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