From: Krzysztof Kozlowski <krzk@kernel.org>
To: Til Kaiser <mail@tk154.de>
Cc: netdev@vger.kernel.org, Luo Jie <jie.luo@oss.qualcomm.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Simon Horman <horms@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Lei Wei <quic_leiwei@quicinc.com>,
Suruchi Agarwal <quic_suruchia@quicinc.com>,
Pavithra R <quic_pavir@quicinc.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next 3/4] dt-bindings: net: qcom,ipq9574-ppe: Add IPQ5332 support
Date: Fri, 9 Oct 2026 10:38:55 +0200 [thread overview]
Message-ID: <20261009-practical-wildebeest-of-conversion-7c0e59@quoll> (raw)
In-Reply-To: <20261005152915.101780-4-mail@tk154.de>
On Mon, Oct 05, 2026 at 05:29:14PM +0200, Til Kaiser wrote:
> IPQ5332 uses the same PPE architecture as IPQ9574, but has two front
> panel ports instead of six and four interconnect paths instead of seven.
>
> Add the qcom,ipq5332-ppe compatible and constrain the interconnects
> and port nodes per SoC: IPQ5332 takes four interconnects and only
> ethernet-port@1 and ethernet-port@2, while IPQ9574 keeps seven
> interconnects.
>
> The PPE core, EDMA and MAC clock functions are shared, but IPQ5332 also
> needs the GCC IM sleep clock. The PPE core uses one reset and each MAC
> uses three resets on both SoCs. IPQ5332 EDMA needs separate system and
> configuration resets; IPQ9574 uses one combined reset. Constrain the
> clock and reset counts accordingly. Keep EDMA resets positional, with
> the system reset first and the configuration reset second on IPQ5332,
> consistent with the existing unnamed IPQ9574 reset.
>
> IPQ5332 EDMA has 24 TX/completion rings, 16 RX descriptor rings and eight
> RX fill rings, so the full EDMA interrupt set comprises 49 interrupts.
> Constrain the interrupt counts and ring names per SoC as well.
>
> The IPQ5332 clock and reset functions are described by Qualcomm's NSSCC
How is clock relevant to this device? This is PPE, no?
> driver submission. Its sleep clock is also listed in Qualcomm's
> PPE DTS submission. The ring limits come from QSDK 14.0.1595.1665,
> qca-nss-dp hal/soc_ops/ipq53xx/nss_ipq53xx.h.
>
> Link: https://lore.kernel.org/r/20240829082830.56959-7-quic_varada@quicinc.com
> Link: https://lore.kernel.org/r/20240110112059.2498-3-quic_luoj@quicinc.com
I do not understand how these clock patches are relevant here.
Drop links and paragraph not relevant to this code.
With this:
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-09 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 15:29 [PATCH net-next 0/4] net: ethernet: qualcomm: ppe: Add IPQ5332 support Til Kaiser
2026-10-05 15:29 ` [PATCH net-next 1/4] net: ethernet: qualcomm: ppe: Select hardware configuration by SoC Til Kaiser
2026-10-05 15:29 ` [PATCH net-next 2/4] dt-bindings: net: qcom,ipq9574-ppe: Tighten ethernet port node constraints Til Kaiser
2026-10-08 3:31 ` netdev-bot+sashiko
2026-10-09 8:36 ` Krzysztof Kozlowski
2026-10-05 15:29 ` [PATCH net-next 3/4] dt-bindings: net: qcom,ipq9574-ppe: Add IPQ5332 support Til Kaiser
2026-10-08 3:31 ` netdev-bot+sashiko
2026-10-09 8:38 ` Krzysztof Kozlowski [this message]
2026-10-05 15:29 ` [PATCH net-next 4/4] net: ethernet: qualcomm: ppe: " Til Kaiser
2026-10-08 3:31 ` netdev-bot+sashiko
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=20261009-practical-wildebeest-of-conversion-7c0e59@quoll \
--to=krzk@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=jie.luo@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@tk154.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_leiwei@quicinc.com \
--cc=quic_pavir@quicinc.com \
--cc=quic_suruchia@quicinc.com \
--cc=rdunlap@infradead.org \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.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