linux-kernel - Re: [PATCH net-next v4 01/14] dt-bindings: net: Add PPE for Qualcomm IPQ9574 SoC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e9dac160-f90a-48e2-9269-245b36c3aefe@kernel.org>
Date: Sat, 24 May 2025 08:25:51 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Luo Jie <quic_luoj@...cinc.com>
Cc: Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller"
 <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
 Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Lei Wei <quic_leiwei@...cinc.com>,
 Suruchi Agarwal <quic_suruchia@...cinc.com>,
 Pavithra R <quic_pavir@...cinc.com>, Simon Horman <horms@...nel.org>,
 Jonathan Corbet <corbet@....net>, Kees Cook <kees@...nel.org>,
 "Gustavo A. R. Silva" <gustavoars@...nel.org>,
 Philipp Zabel <p.zabel@...gutronix.de>, linux-arm-msm@...r.kernel.org,
 netdev@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
 linux-hardening@...r.kernel.org, quic_kkumarcs@...cinc.com,
 quic_linchen@...cinc.com, srinivas.kandagatla@...aro.org,
 bartosz.golaszewski@...aro.org, john@...ozen.org
Subject: Re: [PATCH net-next v4 01/14] dt-bindings: net: Add PPE for Qualcomm
 IPQ9574 SoC

On 23/05/2025 12:28, Luo Jie wrote:
>>> +  interconnect-names:
>>> +    items:
>>> +      - const: ppe
>>> +      - const: ppe_cfg
>>> +      - const: qos_gen
>>> +      - const: timeout_ref
>>> +      - const: nssnoc_memnoc
>>> +      - const: memnoc_nssnoc
>>> +      - const: memnoc_nssnoc_1
>>> +
>>> +  ethernet-dma:
>>
>> I don't get why this is a separate node.
>>
> 
> We used a separate node because the EDMA (Ethernet DMA)
> is a separate block within the PPE block, with specific
> functions like ports-to-host-CPU packet transfer and
> hardware packet steering. We felt that a separate node
> would depict the hierarchy more clearly. Could you please
> suggest if a single node is recommended instead?
Since it is a separate block and it has its own resources, it is fine.

Best regards,
Krzysztof