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>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Odelu Kukatla <odelu.kukatla@oss.qualcomm.com>
Subject: Re: [PATCH 2/2] interconnect: qcom: glymur: Add Mahua SoC support
Date: Mon, 26 Jan 2026 18:40:13 +0530 [thread overview]
Message-ID: <d160aa9b-d22d-4c12-ab4f-42b5dff375b5@oss.qualcomm.com> (raw)
In-Reply-To: <vpaz7jhnuagfl24dow3ktyhjtzktmhiiwh2rnflub3jbc3pgu2@2ydlmugmqgbt>
On 1/23/2026 11:28 PM, Dmitry Baryshkov wrote:
> On Fri, Jan 23, 2026 at 05:12:36PM +0000, Raviteja Laggyshetty wrote:
>> Mahua is a derivative of the Glymur SoC. This patch extends the
>
> Documentation/process/submitting-patches.rst, look for 'This patch'.
Will update the commit text, in next patch revision.
>
>> Glymur driver to support Mahua by:
>>
>> 1. Adding new node definitions for interconnects that differ from Glymur
>> (Config NoC, High-Speed Coherent NoC, PCIe West ANOC/Slave NoC).
>> 2. Reusing existing Glymur definitions for identical NoCs.
>> 3. Overriding the channel and buswidth, with Mahua specific values for
>> the differing NoCs
>>
>> Co-developed-by: Odelu Kukatla <odelu.kukatla@oss.qualcomm.com>
>> Signed-off-by: Odelu Kukatla <odelu.kukatla@oss.qualcomm.com>
>> Signed-off-by: Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>
>> ---
>> drivers/interconnect/qcom/glymur.c | 153 ++++++++++++++++++++++++++++++++++++-
>> 1 file changed, 152 insertions(+), 1 deletion(-)
>>
>> +static struct qcom_icc_node * const mahua_cnoc_cfg_nodes[] = {
>
> As you are patching other instances, why can't we just patch out the
> PCI_3A out of these structures?
>
>>
>> +static int glymur_qnoc_probe(struct platform_device *pdev)
>> +{
>> + if (device_is_compatible(&pdev->dev, "qcom,mahua-mc-virt")) {
>> + llcc_mc.channels = 8;
>> + ebi.channels = 8;
>> + } else if (device_is_compatible(&pdev->dev, "qcom,mahua-hscnoc")) {
>> + qns_llcc.channels = 8;
>> + chm_apps.channels = 4;
>> + qnm_pcie_west.buswidth = 32;
>> + } else if (device_is_compatible(&pdev->dev, "qcom,mahua-pcie-west-anoc")) {
>> + qns_pcie_west_mem_noc.buswidth = 32;
>> + }
>
> Right here, set the node entries to NULL.
cnoc_cfg_nodes is declared as an array of const pointers, so the pointer
values cannot be reassigned after initialization. To change the addresses,
the const qualifier would need to be dropped. To preserve const, the
entire array has been duplicated instead by dropping the PCIE_3A related
nodes.
>
>> +
>> + return qcom_icc_rpmh_probe(pdev);
>> +}
>> +
>> static const struct of_device_id qnoc_of_match[] = {
>> { .compatible = "qcom,glymur-aggre1-noc", .data = &glymur_aggre1_noc},
>> { .compatible = "qcom,glymur-aggre2-noc", .data = &glymur_aggre2_noc},
>> @@ -2477,12 +2623,15 @@ static const struct of_device_id qnoc_of_match[] = {
>> { .compatible = "qcom,glymur-aggre4-noc", .data = &glymur_aggre4_noc},
>> { .compatible = "qcom,glymur-clk-virt", .data = &glymur_clk_virt},
>> { .compatible = "qcom,glymur-cnoc-cfg", .data = &glymur_cnoc_cfg},
>> + { .compatible = "qcom,mahua-cnoc-cfg", .data = &mahua_cnoc_cfg},
>> { .compatible = "qcom,glymur-cnoc-main", .data = &glymur_cnoc_main},
>> { .compatible = "qcom,glymur-hscnoc", .data = &glymur_hscnoc},
>> + { .compatible = "qcom,mahua-hscnoc", .data = &mahua_hscnoc},
>> { .compatible = "qcom,glymur-lpass-ag-noc", .data = &glymur_lpass_ag_noc},
>> { .compatible = "qcom,glymur-lpass-lpiaon-noc", .data = &glymur_lpass_lpiaon_noc},
>> { .compatible = "qcom,glymur-lpass-lpicx-noc", .data = &glymur_lpass_lpicx_noc},
>> { .compatible = "qcom,glymur-mc-virt", .data = &glymur_mc_virt},
>> + { .compatible = "qcom,mahua-mc-virt", .data = &glymur_mc_virt},
>> { .compatible = "qcom,glymur-mmss-noc", .data = &glymur_mmss_noc},
>> { .compatible = "qcom,glymur-nsinoc", .data = &glymur_nsinoc},
>> { .compatible = "qcom,glymur-nsp-noc", .data = &glymur_nsp_noc},
>> @@ -2490,14 +2639,16 @@ static const struct of_device_id qnoc_of_match[] = {
>> { .compatible = "qcom,glymur-pcie-east-anoc", .data = &glymur_pcie_east_anoc},
>> { .compatible = "qcom,glymur-pcie-east-slv-noc", .data = &glymur_pcie_east_slv_noc},
>> { .compatible = "qcom,glymur-pcie-west-anoc", .data = &glymur_pcie_west_anoc},
>> + { .compatible = "qcom,mahua-pcie-west-anoc", .data = &mahua_pcie_west_anoc},
>> { .compatible = "qcom,glymur-pcie-west-slv-noc", .data = &glymur_pcie_west_slv_noc},
>> + { .compatible = "qcom,mahua-pcie-west-slv-noc", .data = &mahua_pcie_west_slv_noc},
>> { .compatible = "qcom,glymur-system-noc", .data = &glymur_system_noc},
>> { }
>> };
>> MODULE_DEVICE_TABLE(of, qnoc_of_match);
>>
>> static struct platform_driver qnoc_driver = {
>> - .probe = qcom_icc_rpmh_probe,
>> + .probe = glymur_qnoc_probe,
>> .remove = qcom_icc_rpmh_remove,
>> .driver = {
>> .name = "qnoc-glymur",
>>
>> --
>> 2.43.0
>>
>
next prev parent reply other threads:[~2026-01-26 13:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 17:12 [PATCH 0/2] Add interconnect support for Qualcomm Mahua SoC Raviteja Laggyshetty
2026-01-23 17:12 ` [PATCH 1/2] dt-bindings: interconnect: document the RPMh Network-On-Chip interconnect in " Raviteja Laggyshetty
2026-01-23 17:12 ` [PATCH 2/2] interconnect: qcom: glymur: Add Mahua SoC support Raviteja Laggyshetty
2026-01-23 17:58 ` Dmitry Baryshkov
2026-01-26 10:31 ` Konrad Dybcio
2026-01-26 13:10 ` Raviteja Laggyshetty [this message]
2026-01-26 13:34 ` Dmitry Baryshkov
2026-01-26 13:40 ` 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=d160aa9b-d22d-4c12-ab4f-42b5dff375b5@oss.qualcomm.com \
--to=raviteja.laggyshetty@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=dmitry.baryshkov@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=odelu.kukatla@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
all inboxes | Powered by JetHome®