mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sivansh Gupta <sivansh.gupta@oss.qualcomm.com>
To: 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,
	konrad.dybcio@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: Thu, 29 Oct 2026 15:09:08 +0530	[thread overview]
Message-ID: <20261029093908.100286-1-sivansh.gupta@oss.qualcomm.com> (raw)
In-Reply-To: <20261028-topic-sip_cob-v1-0-80ab6704aca3@oss.qualcomm.com>

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/

  parent reply	other threads:[~2026-10-29  9:39 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 ` Sivansh Gupta [this message]
2026-10-30 10:46   ` [PATCH v1 0/3] Commonize Glymur regulator settings for fixed rails Konrad Dybcio

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=20261029093908.100286-1-sivansh.gupta@oss.qualcomm.com \
    --to=sivansh.gupta@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=konrad.dybcio@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 \
    /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®