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>,
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,
Odelu Kukatla <odelu.kukatla@oss.qualcomm.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: interconnect: qcom,osm-l3: Add EPSS L3 DT binding for Qualcomm Shikra SoC
Date: Fri, 5 Jun 2026 14:32:20 +0200 [thread overview]
Message-ID: <20260605-imaginary-essential-kestrel-0bf265@quoll> (raw)
In-Reply-To: <20260603-shikra_epss_l3-v3-1-3c2e0b796e78@oss.qualcomm.com>
On Wed, Jun 03, 2026 at 11:26:12AM +0000, Raviteja Laggyshetty wrote:
> Document the EPSS L3 interconnect provider binding for Qualcomm
> Shikra SoC.
>
> The Shikra EPSS L3 block is similar to existing Qualcomm EPSS/OSM L3
> providers, but supports only up to 12 frequency lookup table entries.
>
> Co-developed-by: Odelu Kukatla <odelu.kukatla@oss.qualcomm.com>
> Signed-off-by: Odelu Kukatla <odelu.kukatla@oss.qualcomm.com>
> Signed-off-by: Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>
> ---
> Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml | 2 ++
> 1 file changed, 2 insertions(+)
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-06-05 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 11:26 [PATCH v3 0/2] Add EPSS L3 provider support on Qualcomm Shikra SoC Raviteja Laggyshetty
2026-06-03 11:26 ` [PATCH v3 1/2] dt-bindings: interconnect: qcom,osm-l3: Add EPSS L3 DT binding for " Raviteja Laggyshetty
2026-06-05 12:32 ` Krzysztof Kozlowski [this message]
2026-06-03 11:26 ` [PATCH v3 2/2] interconnect: qcom: Add EPSS L3 scaling support for " Raviteja Laggyshetty
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=20260605-imaginary-essential-kestrel-0bf265@quoll \
--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 \
--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