public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yixun Lan <dlan@kernel.org>
To: Lee Jones <lee@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Alex Elder <elder@riscstar.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Troy Mitchell <troy.mitchell@linux.spacemit.com>,
	Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	Guodong Xu <guodong@riscstar.com>,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	spacemit@lists.linux.dev, devicetree@vger.kernel.org
Subject: Re: (subset) [PATCH v4 1/3] dt-bindings: mfd: spacemit,p1: Add individual regulator supply properties
Date: Sat, 7 Mar 2026 06:39:58 +0800	[thread overview]
Message-ID: <20260306223958-GKB302167@kernel.org> (raw)
In-Reply-To: <177280476778.1042627.3296790673262334325.b4-ty@kernel.org>

Hi Jones,

On 13:46 Fri 06 Mar     , Lee Jones wrote:
> On Fri, 06 Feb 2026 10:32:02 +0800, Guodong Xu wrote:
> > Add supply properties that match the P1 PMIC's actual hardware topology
> > where each buck converter has its own VIN pin and LDO groups share
> > common input pins. Supply names are defined according to the pinout
> > names in the P1 datasheet.
> > 
> > The existing "vin-supply" is dropped from the binding document as the
> > updated spacemit P1 driver no longer parses it. Only the per-rail names
> > ("vin1-supply", "vin2-supply", ...) are supported.
> > 
> > [...]
> 
> Applied, thanks!
> 
> [1/3] dt-bindings: mfd: spacemit,p1: Add individual regulator supply properties
>       commit: e13ebb4cfcff4399a34c3a89c493020899a431f7
> 
Not fure if this will cause a conflict, the patch has already been merged
by Mark, see

https://lore.kernel.org/r/177204643911.168523.3724548692200647978.b4-ty@kernel.org/

> --
> Lee Jones [李琼斯]
> 

-- 
Yixun Lan (dlan)

  reply	other threads:[~2026-03-06 22:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06  2:32 [PATCH v4 0/3] regulator: spacemit-p1: Support board power tree via DT properties Guodong Xu
2026-02-06  2:32 ` [PATCH v4 1/3] dt-bindings: mfd: spacemit,p1: Add individual regulator supply properties Guodong Xu
2026-02-09 19:00   ` Conor Dooley
2026-03-06 13:46   ` (subset) " Lee Jones
2026-03-06 22:39     ` Yixun Lan [this message]
2026-03-09  9:50       ` Lee Jones
2026-02-06  2:32 ` [PATCH v4 2/3] regulator: spacemit-p1: Update supply names Guodong Xu
2026-02-06  2:32 ` [PATCH v4 3/3] riscv: dts: spacemit: Update PMIC supply properties for BPI-F3 and Jupiter Guodong Xu
2026-02-25 19:07 ` (subset) [PATCH v4 0/3] regulator: spacemit-p1: Support board power tree via DT properties Mark Brown
2026-03-02  3:11 ` 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=20260306223958-GKB302167@kernel.org \
    --to=dlan@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=elder@riscstar.com \
    --cc=guodong@riscstar.com \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=lgirdwood@gmail.com \
    --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 \
    --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