From: Krzysztof Kozlowski <krzk@kernel.org>
To: "André Draszik" <andre.draszik@linaro.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>
Cc: Juan Yescas <jyescas@google.com>,
kernel-team@android.com, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Peter Griffin <peter.griffin@linaro.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>
Subject: Re: [PATCH v2] arm64: dts: exynos: gs101-pixel: add all S2MPG1x regulators
Date: Tue, 10 Feb 2026 12:52:57 +0100 [thread overview]
Message-ID: <0497b058-b943-46e5-89f4-a0d3dcf367ad@kernel.org> (raw)
In-Reply-To: <81ef51394b2612368bceb81466dbb090260578e0.camel@linaro.org>
On 10/02/2026 12:47, André Draszik wrote:
> On Tue, 2026-02-10 at 11:38 +0000, André Draszik wrote:
>> On Tue, 2026-02-10 at 11:30 +0000, André Draszik wrote:
>>> Most rails are the same between Pixel 6 and Pro, with the following
>>> differences:
>>> * only Pro has UWB
>>> * Pro uses l2m, not l14m, for TCXO
>>> * Pro uses bucka, not l31m, for NFC
>>>
>>> Signed-off-by: André Draszik <andre.draszik@linaro.org>
>>> ---
>>> Changes in v2:
>>> - add comments for board-specific and unused rails (Krzysztof)
>>> - link simple-framebuffer to display regulators
>>> - Link to v1: https://lore.kernel.org/r/20251113-s2mpg1x-regulators-dts-v1-1-80a70ef42be1@linaro.org
>>> ---
>>> Please note that this patch depends on the bindings updates for S2MPG1x
>>> from
>>> https://lore.kernel.org/all/20260122-s2mpg1x-regulators-v7-0-3b1f9831fffd@linaro.org/
>>> for validation to succeed. Almost all of them are in linux-next, but
>>> patch 1 from that series is still to be applied.
>>
>> ^^^^^^^
>> patch 7
>
> Krzysztof, could you take patch 7 of that series? I expected them all to go
> via mfd and/or regulator trees, but seems final decision was otherwise.
Yes, sure, just resend it please (remember to note if there are any
dependencies).
>
> Or what's the best thing to do?
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-10 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 11:30 André Draszik
2026-02-10 11:38 ` André Draszik
2026-02-10 11:47 ` André Draszik
2026-02-10 11:52 ` Krzysztof Kozlowski [this message]
2026-02-28 14:44 ` Krzysztof Kozlowski
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=0497b058-b943-46e5-89f4-a0d3dcf367ad@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jyescas@google.com \
--cc=kernel-team@android.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=tudor.ambarus@linaro.org \
/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
all inboxes | Powered by JetHome®