From: Krzysztof Kozlowski <krzk@kernel.org>
To: Casey Connolly <casey.connolly@linaro.org>
Cc: Luca Weiss <luca.weiss@fairphone.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 2/2] pmdomain: qcom: rpmhpd: Add Milos power domains
Date: Tue, 8 Jul 2025 10:05:51 +0200 [thread overview]
Message-ID: <20250708-vengeful-bright-rhino-d8d5ea@krzk-bin> (raw)
In-Reply-To: <fe454257-aa21-4304-868f-aefbea9963c4@linaro.org>
On Mon, Jul 07, 2025 at 04:42:13PM +0200, Casey Connolly wrote:
> > > > diff --git a/drivers/pmdomain/qcom/rpmhpd.c b/drivers/pmdomain/qcom/rpmhpd.c
> > > > index 078323b85b5648e33dd89e08cf31bdc5ab76d553..e09552a469264f28952fc46c3ab8c125e87310da 100644
> > > > --- a/drivers/pmdomain/qcom/rpmhpd.c
> > > > +++ b/drivers/pmdomain/qcom/rpmhpd.c
> > > > @@ -217,6 +217,24 @@ static struct rpmhpd gmxc = {
> > > > .res_name = "gmxc.lvl",
> > > > };
> > > > +/* Milos RPMH powerdomains */
> > >
> > > I can't find any public docs telling us which SoC is Milos (the only
> > > relevant result is Bjorn's email asking you to use that name instead of
> > > SM7635). So for the sake of future generations could you reference both
> > > names in a comment somewhere? Or even the commit message would be enough
> > > tbh.
> >
> > I don't know the full list of model numbers for Milos. I assume it's
> > SM7635, SM6650, SM6650P, QCM6690 and QCS6690 based on the info I could
> > fine, but such info is hard to get. So this is not a definite list that
> > all those are actually Milos, or that this is the full list of Milos
> > chipsets.
>
> oof, I see... that complicates things. It sure would be good if this list
> was documented in the kernel though imo.
Kernel is not the place to store mappings or descriptions of some random
company products and their names, so no.
Also it's not a task of contributor of a new SoC to decipher Qualcomm
model numbering and document it anywhere.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-08 8:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 10:18 [PATCH v2 0/2] Add Milos RPMHPD power domains Luca Weiss
2025-07-07 10:18 ` [PATCH v2 1/2] dt-bindings: power: qcom,rpmpd: document the Milos RPMh Power Domains Luca Weiss
2025-07-08 8:07 ` Krzysztof Kozlowski
2025-07-07 10:18 ` [PATCH v2 2/2] pmdomain: qcom: rpmhpd: Add Milos power domains Luca Weiss
2025-07-07 11:31 ` Konrad Dybcio
2025-07-07 13:23 ` Casey Connolly
2025-07-07 13:49 ` Luca Weiss
2025-07-07 14:42 ` Casey Connolly
2025-07-08 8:05 ` Krzysztof Kozlowski [this message]
2025-07-09 11:30 ` [PATCH v2 0/2] Add Milos RPMHPD " Ulf Hansson
2025-07-09 11:33 ` Luca Weiss
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=20250708-vengeful-bright-rhino-d8d5ea@krzk-bin \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=casey.connolly@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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