From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Sivansh Gupta <sivansh.gupta@oss.qualcomm.com>, konradybcio@kernel.org
Cc: abelvesa@kernel.org, andersson@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, dmitry.baryshkov@oss.qualcomm.com,
gopikrishna.garmidi@oss.qualcomm.com, krzk+dt@kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
robh@kernel.org
Subject: Re: [PATCH v1 0/3] Commonize Glymur regulator settings for fixed rails
Date: Fri, 30 Oct 2026 11:46:06 +0100 [thread overview]
Message-ID: <3e798ac9-e0f8-46d2-bc8d-e0fff9c07fd0@oss.qualcomm.com> (raw)
In-Reply-To: <20261029093908.100286-1-sivansh.gupta@oss.qualcomm.com>
On 10/29/26 10:39 AM, Sivansh Gupta wrote:
> Hey Konrad,
>> Certain rails are predefined and will ALWAYS have to be the same for a
>> given PMIC configuration (due to electrical and other requirements).
>> Factor these out to remove a layer of pain when creating DTs and let
>> one have a better way to reason about the settings across the platform.
>>
>> Glymur-SiP will be the next target after/if this is accepted
>
> This series conflicts with mine.
> I attempted to rebase your series on top of mine, but it didnt apply
> cleanly, hence wasnt able to boot test it.
>
> Link: https://lore.kernel.org/all/20261027114955.1266499-1-sivansh.gupta@oss.qualcomm.com/
I'll rebase the v2 on top.
Konrad
prev parent reply other threads:[~2026-10-30 10:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 20:04 [PATCH " Konrad Dybcio
2026-10-28 20:04 ` [PATCH 1/3] arm64: dts: qcom: Unify Glymur/Mahua regulator handles Konrad Dybcio
2026-10-29 8:36 ` Abel Vesa
2026-10-28 20:04 ` [PATCH 2/3] arm64: dts: qcom: Consolidate Glymur CoB power grid Konrad Dybcio
2026-10-29 8:51 ` Abel Vesa
2026-10-28 20:04 ` [PATCH 3/3] arm64: dts: qcom: glymur-crd: Drop L4F0 Konrad Dybcio
2026-10-29 8:37 ` Abel Vesa
2026-10-29 9:39 ` [PATCH v1 0/3] Commonize Glymur regulator settings for fixed rails Sivansh Gupta
2026-10-30 10:46 ` Konrad Dybcio [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=3e798ac9-e0f8-46d2-bc8d-e0fff9c07fd0@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=gopikrishna.garmidi@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sivansh.gupta@oss.qualcomm.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
all inboxes | Powered by JetHome®