From: Krzysztof Kozlowski <krzk@kernel.org>
To: Abel Vesa <abel.vesa@oss.qualcomm.com>
Cc: Georgi Djakov <djakov@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sibi Sankar <sibi.sankar@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: interconnect: OSM L3: Add Eliza OSM L3 compatible
Date: Tue, 24 Feb 2026 09:14:01 +0100 [thread overview]
Message-ID: <08471da2-8577-4114-ab26-bcbc81536999@kernel.org> (raw)
In-Reply-To: <2dnws4hpakt4oxhbfpcnu5ga45mmx4fjxexou2gaueiqaveeyn@itiyzldq5cxr>
On 24/02/2026 09:10, Abel Vesa wrote:
> On 26-02-24 08:29:09, Krzysztof Kozlowski wrote:
>> On Mon, Feb 23, 2026 at 10:49:04AM +0200, Abel Vesa wrote:
>>> Eliza, similarly to SDM845, uses OSM hardware for L3 scaling.
>>> Document it.
>>>
>>> Signed-off-by: Abel Vesa <abel.vesa@oss.qualcomm.com>
>>> ---
>>> Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml b/Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml
>>> index 4b9b98fbe8f2..6182599eb3c1 100644
>>> --- a/Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml
>>> +++ b/Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml
>>> @@ -28,6 +28,7 @@ properties:
>>> - const: qcom,osm-l3
>>> - items:
>>> - enum:
>>> + - qcom,eliza-epss-l3
>>
>> I see EPSS, not OSM here. This is also list without SDM845, so I don't
>> understand explanation in commit msg at all.
>
> So there are two issues here:
>
> 1. EPSS bindings are handled by the OSM schema. I believe this is by
> design as they basically do the same thing. Interconnect providers for
> L3 scaling. So the compatible is in the right schema.
We do not talk here about schema or bindings at all. Look at your commit
msg:
"uses OSM hardware"
so again: EPSS or OSM.
>
> 2. The commit message should've said SM8650 instead. Will fix and
> respin.
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-24 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 8:49 [PATCH] dt-bindings: interconnect: OSM L3: Add Eliza OSM L3 compatible Abel Vesa
2026-02-24 7:29 ` Krzysztof Kozlowski
2026-02-24 8:10 ` Abel Vesa
2026-02-24 8:14 ` Krzysztof Kozlowski [this message]
2026-02-24 8:32 ` Abel Vesa
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=08471da2-8577-4114-ab26-bcbc81536999@kernel.org \
--to=krzk@kernel.org \
--cc=abel.vesa@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@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=robh@kernel.org \
--cc=sibi.sankar@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