From: "Luca Weiss" <luca.weiss@fairphone.com>
To: "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 v3 2/2] interconnect: qcom: Add Milos interconnect provider driver
Date: Mon, 21 Jul 2025 09:42:38 +0200 [thread overview]
Message-ID: <DBHKBSK14XHM.E3ZUQMEJKEOJ@fairphone.com> (raw)
In-Reply-To: <d8955532-9a3b-451f-b5c7-549cee7d749e@kernel.org>
Hi Georgi,
On Mon Jul 21, 2025 at 9:36 AM CEST, Georgi Djakov wrote:
> Hi Luca,
>
> On 7/9/25 4:14 PM, Luca Weiss wrote:
>> Add driver for the Qualcomm interconnect buses found in Milos 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>
>> ---
>> drivers/interconnect/qcom/Kconfig | 9 +
>> drivers/interconnect/qcom/Makefile | 2 +
>> drivers/interconnect/qcom/milos.c | 1837 ++++++++++++++++++++++++++++++++++++
>> 3 files changed, 1848 insertions(+)
>>
> [..]
>> +
>> +static struct qcom_icc_qosbox qhm_qup1_qos = {
>> + .num_ports = 1,
>> + .port_offsets = { 0xc000 },
>> + .prio = 2,
>> + .urg_fwd = 0,
>> + .prio_fwd_disable = 1,
>> +};
>
> Thanks for adding QoS!
>
>> +
>> +static struct qcom_icc_node qhm_qup1 = {
>> + .name = "qhm_qup1",
>> + .channels = 1,
>> + .buswidth = 4,
>> + .qosbox = &qhm_qup1_qos,
>> + .link_nodes = { &qns_a1noc_snoc, NULL },
>> +};
>
> It's very nice that you switched to the dynamic IDs, but please use the
> current style of links (like in v1), as the the NULL terminated lists
> are not merged yet. All the rest looks good!
Is what's in todays linux-next a good base? Or what branch should I base
this on? But correct, I currently have v2 of dynamic ID patches in the
base for this.
Also If I send the next revision by e.g. Wednesday can it still go into
6.17? Just wondering how quick I need to work on this.
Regards
Luca
>
> Thanks,
> Georgi
next prev parent reply other threads:[~2025-07-21 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 13:14 [PATCH v3 0/2] Add interconnect driver for Milos Luca Weiss
2025-07-09 13:14 ` [PATCH v3 1/2] dt-bindings: interconnect: document the RPMh Network-On-Chip Interconnect in Qualcomm Milos SoC Luca Weiss
2025-07-09 13:14 ` [PATCH v3 2/2] interconnect: qcom: Add Milos interconnect provider driver Luca Weiss
2025-07-21 7:36 ` Georgi Djakov
2025-07-21 7:42 ` Luca Weiss [this message]
2025-07-23 7:50 ` Luca Weiss
2025-07-23 15:24 ` Georgi Djakov
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=DBHKBSK14XHM.E3ZUQMEJKEOJ@fairphone.com \
--to=luca.weiss@fairphone.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@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=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®