From: Yao Zi <ziyao@disroot.org>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: andi.shyti@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, heiko@sntech.de, jonas@kwiboo.se,
krzk+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 3/3] arm64: dts: rockchip: Add onboard EEPROM for Radxa E20C
Date: Mon, 10 Mar 2025 07:15:58 +0000 [thread overview]
Message-ID: <Z86RrlBTvt9d40Dk@pie> (raw)
In-Reply-To: <20250310070023.52290-1-amadeus@jmu.edu.cn>
On Mon, Mar 10, 2025 at 03:00:23PM +0800, Chukun Pan wrote:
> Hi,
>
> > +&i2c1 {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&i2c1m0_xfer>;
> > + status = "okay";
> > +
> > + eeprom@50 {
> > + compatible = "belling,bl24c16a", "atmel,24c16";
> > + reg = <0x50>;
> > + pagesize = <16>;
> > + vcc-supply = <&vcc_3v3>;
> > + };
> > +};
>
> This eeprom stores the device information written by the manufacturer,
> such as mac address and sn. So it should be marked as read-only.
Thanks, this makes sense.
> Thanks,
> Chukun
>
> --
> 2.25.1
>
Best regards,
Yao Zi
prev parent reply other threads:[~2025-03-10 7:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 7:06 [PATCH 0/3] Support I2C controllers in RK3528 Yao Zi
2025-03-09 7:06 ` [PATCH 1/3] dt-bindings: i2c: i2c-rk3x: Add compatible string for RK3528 Yao Zi
2025-03-09 19:47 ` Heiko Stübner
2025-03-10 16:38 ` Conor Dooley
2025-03-11 22:08 ` Andi Shyti
2025-03-09 7:06 ` [PATCH 2/3] arm64: dts: rockchip: Add I2C controllers " Yao Zi
2025-03-09 8:00 ` Chukun Pan
2025-03-10 7:22 ` Yao Zi
2025-03-09 18:23 ` Jonas Karlman
2025-03-09 7:06 ` [PATCH 3/3] arm64: dts: rockchip: Add onboard EEPROM for Radxa E20C Yao Zi
2025-03-10 7:00 ` Chukun Pan
2025-03-10 7:15 ` Yao Zi [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=Z86RrlBTvt9d40Dk@pie \
--to=ziyao@disroot.org \
--cc=amadeus@jmu.edu.cn \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).