devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Troy Mitchell <troy.mitchell@linux.spacemit.com>
Cc: Yixun Lan <dlan@gentoo.org>,
	linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	"open list:RISC-V ARCHITECTURE" <linux-riscv@lists.infradead.org>,
	"open list:RISC-V SPACEMIT SoC Support"
	<spacemit@lists.linux.dev>
Subject: Re: [PATCH 2/3] riscv: dts: spacemit: add 24c02 eeprom on BPI-F3
Date: Tue, 23 Sep 2025 21:38:02 +0200	[thread overview]
Message-ID: <aNL3GnfqVGyS9AL-@aurel32.net> (raw)
In-Reply-To: <2A310AE601C62BAA+aNH7IfsDeD7-Vrxf@LT-Guozexi>

Hi Troy,

On 2025-09-23 09:42, Troy Mitchell wrote:
> On Mon, Sep 22, 2025 at 06:49:35AM +0200, Aurelien Jarno wrote:
> > On 2025-09-22 11:21, Yixun Lan wrote:
> > It seems to only contains board infos (mac addresses), but if there are 
> > other use cases, that can indeed be dropped.
> Then you can split the EEPROM into different parts.
> Each part can be described as an individual nvmem cell in the device tree.
> Some of them can be marked as read-only, while others remain writable.
> 
> Documentation/devicetree/bindings/eeprom/at24.yaml +15:
> ```
>   - $ref: /schemas/nvmem/nvmem-deprecated-cells.yaml
> ```

As pointed by Vivian the best for that is to use "onie,tlv-layout". I'll 
do that in the V2.

Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net

  reply	other threads:[~2025-09-23 19:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-21 21:01 [PATCH 0/3] riscv: dts: spacemit: add 24c02 eeprom on BPI-F3 Aurelien Jarno
2025-09-21 21:01 ` [PATCH 1/3] riscv: dts: spacemit: enable the i2c2 adapter " Aurelien Jarno
2025-09-23  1:32   ` Troy Mitchell
2025-09-23 19:16     ` Aurelien Jarno
2025-09-24  3:13       ` Troy Mitchell
2025-09-24 19:11         ` Aurelien Jarno
2025-09-21 21:01 ` [PATCH 2/3] riscv: dts: spacemit: add 24c02 eeprom " Aurelien Jarno
2025-09-22  3:21   ` Yixun Lan
2025-09-22  4:49     ` Aurelien Jarno
2025-09-22  8:01       ` Yixun Lan
2025-09-22 21:00         ` Aurelien Jarno
2025-09-23  1:42       ` Troy Mitchell
2025-09-23 19:38         ` Aurelien Jarno [this message]
2025-09-23  2:00   ` Troy Mitchell
2025-09-23 19:21     ` Aurelien Jarno
2025-09-23  6:32   ` Vivian Wang
2025-09-23 19:30     ` Aurelien Jarno
2025-09-21 21:01 ` [PATCH 3/3] riscv: dts: spacemit: add i2c aliases " Aurelien Jarno

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=aNL3GnfqVGyS9AL-@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@gentoo.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh@kernel.org \
    --cc=spacemit@lists.linux.dev \
    --cc=troy.mitchell@linux.spacemit.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).