From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Raviteja Laggyshetty <raviteja.laggyshetty@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 11:31:09 +0100 [thread overview]
Message-ID: <c488e092-2319-463a-b73d-68e487cf3770@oss.qualcomm.com> (raw)
In-Reply-To: <vpaz7jhnuagfl24dow3ktyhjtzktmhiiwh2rnflub3jbc3pgu2@2ydlmugmqgbt>
On 1/23/26 6:58 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'.
>
>> 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.
+1
Konrad
next prev parent reply other threads:[~2026-01-26 10:31 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 [this message]
2026-01-26 13:10 ` Raviteja Laggyshetty
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=c488e092-2319-463a-b73d-68e487cf3770@oss.qualcomm.com \
--to=konrad.dybcio@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=raviteja.laggyshetty@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®