[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <DBHKBSK14XHM.E3ZUQMEJKEOJ@fairphone.com>
Date: Mon, 21 Jul 2025 09:42:38 +0200
From: "Luca Weiss" <luca.weiss@...rphone.com>
To: "Georgi Djakov" <djakov@...nel.org>, "Rob Herring" <robh@...nel.org>,
"Krzysztof Kozlowski" <krzk+dt@...nel.org>, "Conor Dooley"
<conor+dt@...nel.org>
Cc: <~postmarketos/upstreaming@...ts.sr.ht>, <phone-devel@...r.kernel.org>,
<linux-arm-msm@...r.kernel.org>, <linux-pm@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 2/2] interconnect: qcom: Add Milos interconnect
provider driver
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@...rphone.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
Powered by blists - more mailing lists