From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Eugen Hristev <eugen.hristev@linaro.org>,
Jingyi Wang <jingyi.wang@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>,
Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
aiqun.yu@oss.qualcomm.com, tingwei.zhang@oss.qualcomm.com,
trilok.soni@oss.qualcomm.com, yijie.yang@oss.qualcomm.com
Subject: Re: [PATCH 1/2] dt-bindings: interconnect: document the RPMh Network-On-Chip interconnect in Kaanapali SoC
Date: Thu, 25 Sep 2025 14:40:53 +0200 [thread overview]
Message-ID: <f4e7a388-54fd-42a7-8960-be6a3de7ec6a@oss.qualcomm.com> (raw)
In-Reply-To: <ea291acc-bfdc-4a04-ba60-fc59a55ada28@linaro.org>
On 9/25/25 10:57 AM, Eugen Hristev wrote:
>
>
> On 9/25/25 02:02, Jingyi Wang wrote:
>> From: Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>
>>
>> Document the RPMh Network-On-Chip Interconnect of the Kaanapali platform.
>>
>> Signed-off-by: Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>
>> Signed-off-by: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
>> ---
[...]
>> +properties:
>> + compatible:
>> + enum:
>> + - qcom,kaanapali-aggre-noc
>
> Hi,
>
> Does Kaanapali have a single aggre node, or there are several ?
> On previous SoC, I see there are two (aggre1 and aggre2).
> Also in your driver (second patch), I notice aggre1_noc and aggre2_noc .
> It would make sense to accurately describe here the hardware.
They're physically separate
Konrad
next prev parent reply other threads:[~2025-09-25 12:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 23:02 [PATCH 0/2] Add interconnect support for Kaanapali SoC Jingyi Wang
2025-09-24 23:02 ` [PATCH 1/2] dt-bindings: interconnect: document the RPMh Network-On-Chip interconnect in " Jingyi Wang
2025-09-25 4:39 ` Rob Herring (Arm)
2025-09-25 8:57 ` Eugen Hristev
2025-09-25 12:40 ` Konrad Dybcio [this message]
2025-09-30 3:06 ` Raviteja Laggyshetty
2025-09-30 9:57 ` Eugen Hristev
2025-10-21 1:58 ` Raviteja Laggyshetty
2025-09-24 23:02 ` [PATCH 2/2] interconnect: qcom: add Kaanapali interconnect provider driver Jingyi Wang
2025-09-25 2:47 ` Dmitry Baryshkov
2025-09-30 2:52 ` Raviteja Laggyshetty
-- strict thread matches above, loose matches on Subject: below --
2025-10-23 4:39 [PATCH 0/2] Add interconnect support for Kaanapali SoC Raviteja Laggyshetty
2025-10-23 4:39 ` [PATCH 1/2] dt-bindings: interconnect: document the RPMh Network-On-Chip interconnect in " Raviteja Laggyshetty
2025-10-23 6:23 ` Krzysztof Kozlowski
2025-10-28 3:02 ` Aiqun(Maria) Yu
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=f4e7a388-54fd-42a7-8960-be6a3de7ec6a@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=aiqun.yu@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=eugen.hristev@linaro.org \
--cc=jingyi.wang@oss.qualcomm.com \
--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=raviteja.laggyshetty@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=tingwei.zhang@oss.qualcomm.com \
--cc=trilok.soni@oss.qualcomm.com \
--cc=yijie.yang@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