From: Raviteja Laggyshetty <quic_rlaggysh@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
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>,
Odelu Kukatla <quic_okukatla@quicinc.com>,
"Mike Tipton" <quic_mdtipton@quicinc.com>,
Jeff Johnson <quic_jjohnson@quicinc.com>,
Andrew Halaney <ahalaney@redhat.com>,
Sibi Sankar <quic_sibis@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 V8 5/7] interconnect: qcom: sa8775p: Add dynamic icc node id support
Date: Mon, 10 Feb 2025 11:42:17 +0530 [thread overview]
Message-ID: <747868ee-9f6b-4bff-a88b-a91ff52e3f06@quicinc.com> (raw)
In-Reply-To: <ujsy5e4u7inz5mzdh5m672zkfcrd6igoypgkak2assfpvlcrve@mmjlabr6rh5a>
On 2/6/2025 6:30 AM, Dmitry Baryshkov wrote:
> On Wed, Feb 05, 2025 at 06:27:41PM +0000, Raviteja Laggyshetty wrote:
>> Discard the static IDs from node data and set the default node ID
>> to -1 to indicate the for dynamic ID allocation.
>> Update the topology to use node pointers for links instead of static
>> IDs, and rearrange the node definitions to avoid undefined references.
>
> I think it might be better to forward-declare all node entries at the
> top and then keep currently defined nodes in place. Otherwise the diff
> is pretty unreadable.
>
Sure, will upload a new patch with forward declarations.
These forward declarations will be present only for SA8775P and for
upcoming SoCs, topology will be adjusted to avoid the forward declarations.
Please review the other patches in this series, so that I can include
the suggestions in the next patch revision.
Thanks,
Raviteja.
>>
>> Signed-off-by: Raviteja Laggyshetty <quic_rlaggysh@quicinc.com>
>> ---
>> drivers/interconnect/qcom/sa8775p.c | 2194 ++++++++++++---------------
>> 1 file changed, 962 insertions(+), 1232 deletions(-)
>>
>
next prev parent reply other threads:[~2025-02-10 6:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 18:27 [PATCH V8 0/7] Add EPSS L3 provider support on SA8775P SoC Raviteja Laggyshetty
2025-02-05 18:27 ` [PATCH V8 1/7] dt-bindings: interconnect: Add EPSS L3 compatible for SA8775P Raviteja Laggyshetty
2025-02-10 10:11 ` Krzysztof Kozlowski
2025-02-05 18:27 ` [PATCH V8 2/7] interconnect: core: Add dynamic id allocation support Raviteja Laggyshetty
2025-02-10 10:50 ` Dmitry Baryshkov
2025-02-16 16:38 ` Raviteja Laggyshetty
2025-02-17 1:02 ` Dmitry Baryshkov
2025-02-21 6:18 ` Raviteja Laggyshetty
2025-02-05 18:27 ` [PATCH V8 3/7] interconnect: qcom: Add multidev EPSS L3 support Raviteja Laggyshetty
2025-02-10 10:57 ` Dmitry Baryshkov
2025-02-16 16:28 ` Raviteja Laggyshetty
2025-02-17 1:08 ` Dmitry Baryshkov
2025-02-21 11:09 ` Raviteja Laggyshetty
2025-02-05 18:27 ` [PATCH V8 4/7] interconnect: qcom: icc-rpmh: Add dynamic icc node id support Raviteja Laggyshetty
2025-02-05 18:27 ` [PATCH V8 5/7] interconnect: qcom: sa8775p: " Raviteja Laggyshetty
2025-02-06 1:00 ` Dmitry Baryshkov
2025-02-10 6:12 ` Raviteja Laggyshetty [this message]
2025-02-05 18:27 ` [PATCH V8 6/7] arm64: dts: qcom: sa8775p: add EPSS l3 interconnect provider Raviteja Laggyshetty
2025-02-11 14:36 ` Konrad Dybcio
2025-02-05 18:27 ` [PATCH V8 7/7] arm64: dts: qcom: sa8775p: Add CPU OPP tables to scale DDR/L3 Raviteja Laggyshetty
2025-02-11 15:31 ` 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=747868ee-9f6b-4bff-a88b-a91ff52e3f06@quicinc.com \
--to=quic_rlaggysh@quicinc.com \
--cc=ahalaney@redhat.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--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=quic_jjohnson@quicinc.com \
--cc=quic_mdtipton@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®