Devicetree
 help / color / mirror / Atom feed
From: Hung-Chun Tseng <alan.tseng.cs@gmail.com>
To: Yixun Lan <dlan@kernel.org>
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>, E Shattow <e@freeshell.de>,
	devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
	spacemit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] riscv: dts: spacemit: mark K1 board boot devices bootph-pre-ram
Date: Thu, 15 Oct 2026 20:15:49 +0800	[thread overview]
Message-ID: <20261015121549.3809199-1-alan.tseng.cs@gmail.com> (raw)
In-Reply-To: <20261015074621-GKN26088@kernel.org>

Hi Yixun,

Thanks for the review.

On Thu, Oct 15, 2026 at 07:46:21AM +0000, Yixun Lan wrote:
> > &i2c8 {
> > +	bootph-pre-ram;
> We could move this to dtsi file, since all board share
> same design which use i2c8 for connecting to pmic, the
> reward would be that we no longer need to carry this
> property all over board dts file.. similar we could do
> for "i2c2", but I noticed k1-orangepi-rv2/r2s have no
> eeprom enabled..

Agreed, v2 will tag i2c8 in k1.dtsi. I'll keep i2c2 in the board
files, as the OrangePi RV2 and R2S have no EEPROM.

> > 			buck1 {
> > +				bootph-pre-ram;
> U-Boot also carry "regulator-name" for this node, we
> probably could also merge it here, but could do it in
> another patch if want to limit this patch to "pre-ram"
> change only

I'd prefer a separate patch for that, to keep this one about the
bootph tags. The U-Boot K1 SPL looks the rails up by name ("vdd_core",
"vdd_1v8", "vdd_1v8_mmc"), so once the names are upstream, U-Boot can
drop the overrides in its -u-boot.dtsi files.

Thanks,
Hung-Chun

      reply	other threads:[~2026-10-15 12:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12 23:56 [PATCH 0/2] riscv: dts: spacemit: mark K1 boot nodes bootph-pre-ram Hung-Chun Tseng
2026-10-12 23:56 ` [PATCH 1/2] riscv: dts: spacemit: k1: mark boot-critical SoC " Hung-Chun Tseng
2026-10-13  0:04   ` sashiko-bot
2026-10-12 23:56 ` [PATCH 2/2] riscv: dts: spacemit: mark K1 board boot devices bootph-pre-ram Hung-Chun Tseng
2026-10-13  0:08   ` sashiko-bot
2026-10-15  7:46   ` Yixun Lan
2026-10-15 12:15     ` Hung-Chun Tseng [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=20261015121549.3809199-1-alan.tseng.cs@gmail.com \
    --to=alan.tseng.cs@gmail.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlan@kernel.org \
    --cc=e@freeshell.de \
    --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