From: Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@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>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Sibi Sankar <quic_sibis@quicinc.com>,
Odelu Kukatla <quic_okukatla@quicinc.com>,
Mike Tipton <mike.tipton@oss.qualcomm.com>,
Imran Shaik <quic_imrashai@quicinc.com>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 2/2] arm64: dts: qcom: qcs615: Add OSM l3 interconnect provider node and CPU OPP tables to scale DDR/L3
Date: Mon, 18 Aug 2025 12:22:29 +0530 [thread overview]
Message-ID: <c8dc3383-be77-4075-9e04-f5ea693e37a2@oss.qualcomm.com> (raw)
In-Reply-To: <bsrhqkrzdapg72o6h6yx3pw6fjeseolt7zmq5fpvfhhdg7ktyv@zz3ueam6lcqh>
On 8/4/2025 11:58 AM, Dmitry Baryshkov wrote:
> On Mon, Aug 04, 2025 at 06:15:36AM +0000, Raviteja Laggyshetty wrote:
>> Add Operation State Manager (OSM) L3 interconnect provide node and OPP
>> tables required to scale DDR and L3 per freq-domain on QCS615 SoC.
>> As QCS615 and SM8150 SoCs have same OSM hardware, added SM8150
>> compatible as fallback for QCS615 OSM device node.
>>
>> Depends-on: <20250702-qcs615-mm-cpu-dt-v4-v5-3-df24896cbb26@quicinc.com>
>
> Yuck. It's not a way to define dependencies.
Will add the dependency using b4 --edit-deps instead of Depends-on
>
>> Signed-off-by: Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>
>> Signed-off-by: Imran Shaik <quic_imrashai@quicinc.com>
>
> And the comment regarding SoB chain wasn't addressed.
>
>> ---
>> arch/arm64/boot/dts/qcom/sm6150.dtsi | 148 +++++++++++++++++++++++++++
>> 1 file changed, 148 insertions(+)
>>
>> };
>> };
>>
>> + osm_l3: interconnect@18321000 {
>> + compatible = "qcom,qcs615-osm-l3", "qcom,sm8150-osm-l3", "qcom,osm-l3";
>> + reg = <0 0x18321000 0 0x1400>;
>
> reg = <0x0 0x18321000 0x0 0x1400>;
I will fix this in next revision.
Thanks,
Raviteja
>
>> +
>> + clocks = <&rpmhcc RPMH_CXO_CLK>, <&gcc GPLL0>;
>> + clock-names = "xo", "alternate";
>> +
>> + #interconnect-cells = <1>;
>> + };
>> +
>> usb_1_hsphy: phy@88e2000 {
>> compatible = "qcom,qcs615-qusb2-phy";
>> reg = <0x0 0x88e2000 0x0 0x180>;
>> --
>> 2.43.0
>>
>
prev parent reply other threads:[~2025-08-18 6:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 6:15 [PATCH V2 0/2] Add OSM L3 provider support on QCS615 SoC Raviteja Laggyshetty
2025-08-04 6:15 ` [PATCH V2 1/2] dt-bindings: interconnect: Add OSM L3 compatible for " Raviteja Laggyshetty
2025-08-04 6:26 ` Krzysztof Kozlowski
2025-08-18 9:12 ` Raviteja Laggyshetty
2025-08-18 9:55 ` Krzysztof Kozlowski
2025-08-04 6:15 ` [PATCH V2 2/2] arm64: dts: qcom: qcs615: Add OSM l3 interconnect provider node and CPU OPP tables to scale DDR/L3 Raviteja Laggyshetty
2025-08-04 6:28 ` Dmitry Baryshkov
2025-08-18 6:52 ` Raviteja Laggyshetty [this message]
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=c8dc3383-be77-4075-9e04-f5ea693e37a2@oss.qualcomm.com \
--to=raviteja.laggyshetty@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=dmitry.baryshkov@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=quic_imrashai@quicinc.com \
--cc=quic_okukatla@quicinc.com \
--cc=quic_sibis@quicinc.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®