From: Aurelien Jarno <aurelien@aurel32.net>
To: linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Yixun Lan <dlan@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>
Cc: Aurelien Jarno <aurelien@aurel32.net>,
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-riscv@lists.infradead.org (open list:RISC-V ARCHITECTURE),
spacemit@lists.linux.dev (open list:RISC-V SPACEMIT SoC Support)
Subject: [PATCH 2/6] riscv: dts: spacemit: add 24c04 eeprom on Milk-V Jupiter
Date: Sun, 22 Mar 2026 21:28:33 +0100 [thread overview]
Message-ID: <20260322203356.2206927-3-aurelien@aurel32.net> (raw)
In-Reply-To: <20260322203356.2206927-1-aurelien@aurel32.net>
The Milk-V Jupiter board includes a 24c04 eeprom on the i2c2 bus. The
eeprom contains an ONIE TLV table, which on the board I tested only
provides a product-name entry. Expose it via an onie,tlv-layout nvmem
layout.
The eeprom is marked as read-only since its contents are not supposed to
be modified.
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
---
.../boot/dts/spacemit/k1-milkv-jupiter.dts | 22 +++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/arch/riscv/boot/dts/spacemit/k1-milkv-jupiter.dts b/arch/riscv/boot/dts/spacemit/k1-milkv-jupiter.dts
index 3cd83c5924e4f..bd48208a370cf 100644
--- a/arch/riscv/boot/dts/spacemit/k1-milkv-jupiter.dts
+++ b/arch/riscv/boot/dts/spacemit/k1-milkv-jupiter.dts
@@ -108,6 +108,28 @@ &pdma {
status = "okay";
};
+&i2c2 {
+ pinctrl-0 = <&i2c2_0_cfg>;
+ pinctrl-names = "default";
+ status = "okay";
+
+ eeprom@50 {
+ compatible = "atmel,24c04";
+ reg = <0x50>;
+ vcc-supply = <&buck3_1v8>; /* EEPROM_VCC18 */
+ pagesize = <16>;
+ read-only;
+ size = <512>;
+
+ nvmem-layout {
+ compatible = "onie,tlv-layout";
+
+ product-name {
+ };
+ };
+ };
+};
+
&i2c8 {
pinctrl-0 = <&i2c8_cfg>;
pinctrl-names = "default";
--
2.51.0
next prev parent reply other threads:[~2026-03-22 20:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260322203356.2206927-1-aurelien@aurel32.net>
2026-03-22 20:28 ` [PATCH 1/6] riscv: dts: spacemit: add LEDs for Milk-V Jupiter board Aurelien Jarno
2026-03-24 7:54 ` Javier Martinez Canillas
2026-03-22 20:28 ` Aurelien Jarno [this message]
2026-03-24 7:55 ` [PATCH 2/6] riscv: dts: spacemit: add 24c04 eeprom on Milk-V Jupiter Javier Martinez Canillas
2026-03-22 20:28 ` [PATCH 3/6] riscv: dts: spacemit: add i2c aliases " Aurelien Jarno
2026-03-24 7:56 ` Javier Martinez Canillas
2026-03-22 20:28 ` [PATCH 4/6] riscv: dts: spacemit: enable QSPI and add SPI NOR " Aurelien Jarno
2026-03-24 9:02 ` Yixun Lan
2026-03-24 17:07 ` Yao Zi
2026-03-24 21:59 ` Yixun Lan
2026-03-24 21:19 ` Aurelien Jarno
2026-03-24 22:09 ` Yixun Lan
2026-03-22 20:28 ` [PATCH 5/6] riscv: dts: spacemit: enable USB 3 ports " Aurelien Jarno
2026-03-24 8:01 ` Javier Martinez Canillas
2026-03-22 20:28 ` [PATCH 6/6] riscv: dts: spacemit: enable PCIe " Aurelien Jarno
2026-03-24 8:02 ` Javier Martinez Canillas
2026-03-26 7:34 ` Yixun Lan
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=20260322203356.2206927-3-aurelien@aurel32.net \
--to=aurelien@aurel32.net \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
/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