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>,
"Jeff Johnson" <jeff.johnson@oss.qualcomm.com>,
Mike Tipton <mdtipton@quicinc.com>,
Jagadeesh Kona <quic_jkona@quicinc.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 V9 4/7] interconnect: qcom: icc-rpmh: Add dynamic icc node id support
Date: Mon, 10 Mar 2025 07:54:15 +0530 [thread overview]
Message-ID: <5278cb2e-6111-4e57-86b3-987f6f9eabf6@quicinc.com> (raw)
In-Reply-To: <gxqjfabcqafqjzzwc3seadfuldqfxlfappsotjbhkbirvorcyd@mahdpv6klwn5>
On 2/27/2025 9:46 PM, Dmitry Baryshkov wrote:
> On Thu, Feb 27, 2025 at 03:52:10PM +0000, Raviteja Laggyshetty wrote:
>> To facilitate dynamic node ID support, the driver now uses
>> node pointers for links instead of static node IDs.
>> Additionally, the default node ID is set to -1 to prompt
>> the ICC framework for dynamic node ID allocation.
>>
>> Signed-off-by: Raviteja Laggyshetty <quic_rlaggysh@quicinc.com>
>> ---
>> drivers/interconnect/qcom/icc-rpmh.c | 16 ++++++++++++++--
>> drivers/interconnect/qcom/icc-rpmh.h | 3 ++-
>> 2 files changed, 16 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/interconnect/qcom/icc-rpmh.c b/drivers/interconnect/qcom/icc-rpmh.c
>> index f2d63745be54..2e654917f535 100644
>> --- a/drivers/interconnect/qcom/icc-rpmh.c
>> +++ b/drivers/interconnect/qcom/icc-rpmh.c
>> @@ -285,13 +285,25 @@ int qcom_icc_rpmh_probe(struct platform_device *pdev)
>> ret = PTR_ERR(node);
>> goto err_remove_nodes;
>> }
>> + qn->id = node->id;
>>
>> node->name = qn->name;
>> node->data = qn;
>> icc_node_add(node, provider);
>>
>> - for (j = 0; j < qn->num_links; j++)
>> - icc_link_create(node, qn->links[j]);
>> + for (j = 0; j < qn->num_links; j++) {
>> + struct qcom_icc_node *qn_link_node = qn->link_nodes[j];
>> + struct icc_node *link_node;
>> +
>> + if (qn_link_node) {
>> + link_node = icc_node_create(qn_link_node->id);
>> + qn_link_node->id = link_node->id;
>> + icc_link_create(node, qn_link_node->id);
>
> I really don't like the idea of reading the ->id back. I think in the
> last cycle I have already asked to add an API to link two nodes instead
> of linking a node and an ID. Is there an issue with such an API?
Yes, the link pointer may or may not be initialized during the link
creation as the link can belong to other provider which is yet to probe.
So, it is not possible to pass two node pointers as arguments for linking.
RPMh driver has multiple providers and during the creation of links,
nodes associated with other providers are created in the icc_link_create
API. When the actual provider to which the link belongs is probed, its
initialization/node creation is skipped by checking the ID. To ensure
proper tracking of node initialization and prevent re-initialization, it
is essential to read back and store the node’s ID in qnode.
>
>> + } else {
>> + /* backward compatibility for target using static IDs */
>> + icc_link_create(node, qn->links[j]);
>> + }
>> + }
>>
>> data->nodes[i] = node;
>> }
>> diff --git a/drivers/interconnect/qcom/icc-rpmh.h b/drivers/interconnect/qcom/icc-rpmh.h
>> index 82344c734091..cf4aa69c707c 100644
>> --- a/drivers/interconnect/qcom/icc-rpmh.h
>> +++ b/drivers/interconnect/qcom/icc-rpmh.h
>> @@ -95,7 +95,8 @@ struct qcom_icc_qosbox {
>> struct qcom_icc_node {
>> const char *name;
>> u16 links[MAX_LINKS];
>> - u16 id;
>> + struct qcom_icc_node *link_nodes[MAX_LINKS];
>> + int id;
>> u16 num_links;
>> u16 channels;
>> u16 buswidth;
>> --
>> 2.43.0
>>
>
next prev parent reply other threads:[~2025-03-10 2:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 15:52 [PATCH V9 0/7] Add EPSS L3 provider support on SA8775P SoC Raviteja Laggyshetty
2025-02-27 15:52 ` [PATCH V9 1/7] dt-bindings: interconnect: Add EPSS L3 compatible for SA8775P Raviteja Laggyshetty
2025-02-27 15:52 ` [PATCH V9 2/7] interconnect: core: Add dynamic id allocation support Raviteja Laggyshetty
2025-02-27 16:08 ` Dmitry Baryshkov
2025-03-04 5:53 ` Raviteja Laggyshetty
2025-02-27 15:52 ` [PATCH V9 3/7] interconnect: qcom: Add multidev EPSS L3 support Raviteja Laggyshetty
2025-02-27 16:09 ` Dmitry Baryshkov
2025-02-28 0:39 ` Bjorn Andersson
2025-02-27 15:52 ` [PATCH V9 4/7] interconnect: qcom: icc-rpmh: Add dynamic icc node id support Raviteja Laggyshetty
2025-02-27 16:16 ` Dmitry Baryshkov
2025-03-10 2:24 ` Raviteja Laggyshetty [this message]
2025-03-11 19:08 ` Dmitry Baryshkov
2025-03-07 3:53 ` Mike Tipton
2025-03-10 1:58 ` Raviteja Laggyshetty
2025-02-27 15:52 ` [PATCH V9 5/7] interconnect: qcom: sa8775p: " Raviteja Laggyshetty
2025-02-27 16:23 ` Dmitry Baryshkov
2025-03-04 6:20 ` Raviteja Laggyshetty
2025-02-28 0:32 ` Bjorn Andersson
2025-02-27 15:52 ` [PATCH V9 6/7] arm64: dts: qcom: sa8775p: add EPSS l3 interconnect provider Raviteja Laggyshetty
2025-02-27 15:52 ` [PATCH V9 7/7] arm64: dts: qcom: sa8775p: Add CPU OPP tables to scale DDR/L3 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=5278cb2e-6111-4e57-86b3-987f6f9eabf6@quicinc.com \
--to=quic_rlaggysh@quicinc.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=jeff.johnson@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=mdtipton@quicinc.com \
--cc=quic_jkona@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®