From: Krzysztof Kozlowski <krzk@kernel.org>
To: Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>,
Georgi Djakov <djakov@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sibi Sankar <quic_sibis@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Mike Tipton <mike.tipton@oss.qualcomm.com>,
Odelu Kukatla <odelu.kukatla@oss.qualcomm.com>,
Imran Shaik <imran.shaik@oss.qualcomm.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: interconnect: Add OSM L3 compatible for QCS615 SoC
Date: Tue, 19 Aug 2025 13:29:45 +0200 [thread overview]
Message-ID: <620427ef-ade4-43c8-b041-34b0365fb4c1@kernel.org> (raw)
In-Reply-To: <20250819-talos-l3-icc-v3-1-04529e85dac7@oss.qualcomm.com>
On 19/08/2025 13:24, Raviteja Laggyshetty wrote:
> Add Operation State Manager (OSM) L3 interconnect provider binding for
> QCS615 SoC. As the OSM hardware in QCS615 and SM8150 are same,
> added a family-level compatible for SM8150 SoC.
>
> Signed-off-by: Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>
> ---
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-19 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 11:24 [PATCH v3 0/2] Add OSM L3 provider support on QCS615 SoC Raviteja Laggyshetty
2025-08-19 11:24 ` [PATCH v3 1/2] dt-bindings: interconnect: Add OSM L3 compatible for " Raviteja Laggyshetty
2025-08-19 11:29 ` Krzysztof Kozlowski [this message]
2025-08-19 11:24 ` [PATCH v3 2/2] arm64: dts: qcom: qcs615: Add OSM l3 interconnect provider node and CPU OPP tables to scale DDR/L3 Raviteja Laggyshetty
2025-08-19 11:40 ` Dmitry Baryshkov
2025-10-27 22:37 ` (subset) [PATCH v3 0/2] Add OSM L3 provider support on QCS615 SoC Bjorn Andersson
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=620427ef-ade4-43c8-b041-34b0365fb4c1@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=imran.shaik@oss.qualcomm.com \
--cc=konradybcio@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=mike.tipton@oss.qualcomm.com \
--cc=odelu.kukatla@oss.qualcomm.com \
--cc=quic_sibis@quicinc.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