From: Krzysztof Kozlowski <krzk@kernel.org>
To: Raviteja Laggyshetty <raviteja.laggyshetty@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>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Odelu Kukatla <odelu.kukatla@oss.qualcomm.com>
Subject: Re: [PATCH 1/2] dt-bindings: interconnect: qcom,shikra-epss-l3: Add EPSS L3 DT binding
Date: Tue, 2 Jun 2026 13:59:26 +0200 [thread overview]
Message-ID: <709428ff-e732-47b6-a6db-b26cd9149c98@kernel.org> (raw)
In-Reply-To: <afeab8fd-6951-46a3-8b92-9c3b7075949e@oss.qualcomm.com>
On 02/06/2026 11:27, Raviteja Laggyshetty wrote:
>
>
> On 5/30/2026 4:38 PM, Krzysztof Kozlowski wrote:
>> On Sun, May 24, 2026 at 06:03:35PM +0000, Raviteja Laggyshetty wrote:
>>> + '#interconnect-cells':
>>> + const: 1
>>> +
>>
>> I do not see any differences against OSM L3 binding. Why isn't this
>> device there?
>>
>
> The EPSS L3 on Shikra is similar to EPSS/OSM L3 on other Qualcomm SoCs,
> but supports only twelve LUT entries. Due to this hardware difference,
> the generic compatibles are not applicable, so a new SoC specific
> binding is introduced.
>
This I understood, but the binding would be exactly the same, no? Kind
of repeating the question....
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-06-02 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-24 18:03 [PATCH 0/2] Add EPSS L3 provider support on Qualcomm Shikra SoC Raviteja Laggyshetty
2026-05-24 18:03 ` [PATCH 1/2] dt-bindings: interconnect: qcom,shikra-epss-l3: Add EPSS L3 DT binding Raviteja Laggyshetty
2026-05-30 11:08 ` Krzysztof Kozlowski
2026-06-02 9:27 ` Raviteja Laggyshetty
2026-06-02 11:59 ` Krzysztof Kozlowski [this message]
2026-06-02 13:53 ` Raviteja Laggyshetty
2026-05-24 18:03 ` [PATCH 2/2] interconnect: qcom: Add EPSS L3 scaling support for Shikra SoC Raviteja Laggyshetty
2026-05-25 10:12 ` Dmitry Baryshkov
2026-05-25 12:21 ` 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=709428ff-e732-47b6-a6db-b26cd9149c98@kernel.org \
--to=krzk@kernel.org \
--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=odelu.kukatla@oss.qualcomm.com \
--cc=raviteja.laggyshetty@oss.qualcomm.com \
--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®