From: Yixun Lan <dlan@kernel.org>
To: Jennifer Berringer <jberring@redhat.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] riscv: dts: spacemit: add eeprom for K3 CoM260
Date: Sat, 25 Jul 2026 13:28:05 +0000 [thread overview]
Message-ID: <20260725132805-GKG77545@kernel.org> (raw)
In-Reply-To: <20260722202848.1817988-1-jberring@redhat.com>
Hi Jennifer,
On 16:28 Wed 22 Jul , Jennifer Berringer wrote:
> SpacemiT K3 CoM260 Dev Kit has two eeproms: one on the compute
> module and one on the carrier board. Both use a Giantec
> GT24C02B-2TFLI-TR.
>
Patch looks good, so
Reviewed-by: Yixun Lan <dlan@kernel.org>
> Jennifer Berringer (2):
> riscv: dts: spacemit: k3-com260: add eeprom on i2c2
> riscv: dts: spacemit: k3-com260-ifx: add eeprom on i2c1
>
> .../riscv/boot/dts/spacemit/k3-com260-ifx.dts | 15 +++++++++
> arch/riscv/boot/dts/spacemit/k3-com260.dtsi | 32 +++++++++++++++++++
> arch/riscv/boot/dts/spacemit/k3-pinctrl.dtsi | 12 +++++++
> 3 files changed, 59 insertions(+)
>
>
> base-commit: 199380e4d8cd22e539a08d4949e9582b09390bd5
> --
> 2.55.0
>
--
Yixun Lan (dlan)
prev parent reply other threads:[~2026-07-25 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 20:28 [PATCH 0/2] riscv: dts: spacemit: add eeprom for K3 CoM260 Jennifer Berringer
2026-07-22 20:28 ` [PATCH 1/2] riscv: dts: spacemit: k3-com260: add eeprom on i2c2 Jennifer Berringer
2026-07-22 20:28 ` [PATCH 2/2] riscv: dts: spacemit: k3-com260-ifx: add eeprom on i2c1 Jennifer Berringer
2026-07-22 20:37 ` sashiko-bot
2026-07-25 13:28 ` Yixun Lan [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=20260725132805-GKG77545@kernel.org \
--to=dlan@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jberring@redhat.com \
--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