mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luca Weiss" <luca.weiss@fairphone.com>
To: "Konrad Dybcio" <konrad.dybcio@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>
Cc: <~postmarketos/upstreaming@lists.sr.ht>,
	<phone-devel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
	<linux-pm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] interconnect: qcom: Add SM7635 interconnect provider driver
Date: Tue, 08 Jul 2025 12:28:00 +0200	[thread overview]
Message-ID: <DB6LPBOU5TDL.13B4A6U4NQQZQ@fairphone.com> (raw)
In-Reply-To: <3f8bcecb-4c5e-48b1-98be-96f3c0c8329e@oss.qualcomm.com>

Hi Konrad,

On Fri Jun 27, 2025 at 2:48 PM CEST, Konrad Dybcio wrote:
> On 6/25/25 11:13 AM, Luca Weiss wrote:
>> Add driver for the Qualcomm interconnect buses found in SM7635 based
>> platforms. The topology consists of several NoCs that are controlled by
>> a remote processor that collects the aggregated bandwidth for each
>> master-slave pairs.
>> 
>> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
>> ---
>
> [...]
>
>> +static const struct of_device_id qnoc_of_match[] = {
>> +	{ .compatible = "qcom,sm7635-aggre1-noc",
>> +	  .data = &sm7635_aggre1_noc},
>> +	{ .compatible = "qcom,sm7635-aggre2-noc",
>> +	  .data = &sm7635_aggre2_noc},
>> +	{ .compatible = "qcom,sm7635-clk-virt",
>> +	  .data = &sm7635_clk_virt},
>> +	{ .compatible = "qcom,sm7635-cnoc-cfg",
>> +	  .data = &sm7635_cnoc_cfg},
>> +	{ .compatible = "qcom,sm7635-cnoc-main",
>> +	  .data = &sm7635_cnoc_main},
>> +	{ .compatible = "qcom,sm7635-gem-noc",
>> +	  .data = &sm7635_gem_noc},
>> +	{ .compatible = "qcom,sm7635-lpass-ag-noc",
>> +	  .data = &sm7635_lpass_ag_noc},
>> +	{ .compatible = "qcom,sm7635-mc-virt",
>> +	  .data = &sm7635_mc_virt},
>> +	{ .compatible = "qcom,sm7635-mmss-noc",
>> +	  .data = &sm7635_mmss_noc},
>> +	{ .compatible = "qcom,sm7635-nsp-noc",
>> +	  .data = &sm7635_nsp_noc},
>> +	{ .compatible = "qcom,sm7635-pcie-anoc",
>> +	  .data = &sm7635_pcie_anoc},
>> +	{ .compatible = "qcom,sm7635-system-noc",
>> +	  .data = &sm7635_system_noc},
>
> One line per entry, please
>
> In addition to what Dmitry asked for, please also look into porting
> QoS settings - those will require additional clock references in the ICC
> nodes and as such, the bindings will be altered (which we'd prefer to get
> right from the getgo).

I've forgotten to do this for v2, which I've just sent.

But we already have the clock references in the bindings, so the
bindings should be final, also when QoS is added, so just a driver patch
then.

I will put this on my todo list for a future patch to enable this, if
that's fine with you.

> As far as testing goes, there may not be any apparent perf changes, but
> if you get the clocks list wrong, the device will lock up at boot (unless
> you're booting with clk_ignore_unused and friends)

Ack

Regards
Luca

>
> Konrad


  reply	other threads:[~2025-07-08 10:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25  9:13 [PATCH 0/2] Add interconnect driver for SM7635 Luca Weiss
2025-06-25  9:13 ` [PATCH 1/2] dt-bindings: interconnect: document the RPMh Network-On-Chip Interconnect in Qualcomm SM7635 SoC Luca Weiss
2025-06-25 12:24   ` Rob Herring (Arm)
2025-06-25 15:04   ` Rob Herring
2025-06-25  9:13 ` [PATCH 2/2] interconnect: qcom: Add SM7635 interconnect provider driver Luca Weiss
2025-06-27  1:28   ` Dmitry Baryshkov
2025-06-27 12:48   ` Konrad Dybcio
2025-07-08 10:28     ` Luca Weiss [this message]
2025-07-08 11: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=DB6LPBOU5TDL.13B4A6U4NQQZQ@fairphone.com \
    --to=luca.weiss@fairphone.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=djakov@kernel.org \
    --cc=konrad.dybcio@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=phone-devel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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®