From: Casey Connolly <casey.connolly@linaro.org>
To: 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>
Cc: ~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: Mon, 7 Jul 2025 16:42:13 +0200 [thread overview]
Message-ID: <fe454257-aa21-4304-868f-aefbea9963c4@linaro.org> (raw)
In-Reply-To: <DB5VDDKCAQQG.LDCMHXAZN17S@fairphone.com>
On 7/7/25 15:49, Luca Weiss wrote:
> Hi Casey,
>
> On Mon Jul 7, 2025 at 3:23 PM CEST, Casey Connolly wrote:
>>
>>
>> On 7/7/25 12:18, Luca Weiss wrote:
>>> Add the power domains exposed by RPMH in the Qualcomm Milos platform.
>>
>> \o/ codenames!
>>
>>>
>>> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
>>> ---
>>> drivers/pmdomain/qcom/rpmhpd.c | 19 +++++++++++++++++++
>>> 1 file changed, 19 insertions(+)
>>>
>>> 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.
>
>> Off-topic here, but maybe it would be a good idea to add some Qualcomm
>> platform docs to the kernel with a table of all the publicly known names
>> for each SoC? This would also be really helpful even ignoring codenames
>> just to know that SM8550 is Snapdragon 8 Gen 2 for example.
>
> So far my source for this has been the postmarketOS wiki, and this
> Google Doc, but the latter hasn't been updated for new chips since a
> year or so, and is also probably not very complete:
> https://docs.google.com/spreadsheets/d/1WrKHLj_oSoiykhSc6xqXAkT3nlD2hq-fzUPSGiq3Kbc/edit?gid=1270863184#gid=1270863184
>
> And I've got some notes locally for a couple that I regularly need.
>
> But I'd love a more central place that isn't specific to postmarketOS
> for example. Not sure where though?
kernel docs seem sensible to me? Maybe a wiki on gh/linux-msm?
>
> Regards
> Luca
>
>>
>> Kind regards,
>> Casey (she/they)
>>
>>> +static struct rpmhpd *milos_rpmhpds[] = {
>>> + [RPMHPD_CX] = &cx,
>>> + [RPMHPD_CX_AO] = &cx_ao,
>>> + [RPMHPD_EBI] = &ebi,
>>> + [RPMHPD_GFX] = &gfx,
>>> + [RPMHPD_LCX] = &lcx,
>>> + [RPMHPD_LMX] = &lmx,
>>> + [RPMHPD_MSS] = &mss,
>>> + [RPMHPD_MX] = &mx,
>>> + [RPMHPD_MX_AO] = &mx_ao,
>>> +};
>>> +
>>> +static const struct rpmhpd_desc milos_desc = {
>>> + .rpmhpds = milos_rpmhpds,
>>> + .num_pds = ARRAY_SIZE(milos_rpmhpds),
>>> +};
>>> +
>>> /* SA8540P RPMH powerdomains */
>>> static struct rpmhpd *sa8540p_rpmhpds[] = {
>>> [SC8280XP_CX] = &cx,
>>> @@ -723,6 +741,7 @@ static const struct rpmhpd_desc qcs615_desc = {
>>> };
>>>
>>> static const struct of_device_id rpmhpd_match_table[] = {
>>> + { .compatible = "qcom,milos-rpmhpd", .data = &milos_desc },
>>> { .compatible = "qcom,qcs615-rpmhpd", .data = &qcs615_desc },
>>> { .compatible = "qcom,qcs8300-rpmhpd", .data = &qcs8300_desc },
>>> { .compatible = "qcom,qdu1000-rpmhpd", .data = &qdu1000_desc },
>>>
>
next prev parent reply other threads:[~2025-07-07 14:42 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 [this message]
2025-07-08 8:05 ` Krzysztof Kozlowski
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=fe454257-aa21-4304-868f-aefbea9963c4@linaro.org \
--to=casey.connolly@linaro.org \
--cc=andersson@kernel.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;
as well as URLs for NNTP newsgroup(s).