From: Andrew Lunn <andrew@lunn.ch>
To: Jie Luo <quic_luoj@quicinc.com>
Cc: Sergey Ryazanov <ryazanov.s.a@gmail.com>,
Christian Marangi <ansuelsmth@gmail.com>,
Robert Marko <robert.marko@sartura.hr>,
Vladimir Oltean <olteanv@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [net-next PATCH RFC v3 1/8] dt-bindings: net: document ethernet PHY package nodes
Date: Tue, 9 Jan 2024 14:48:16 +0100 [thread overview]
Message-ID: <2f2328ee-205b-4b4f-a683-2df4fbb22dde@lunn.ch> (raw)
In-Reply-To: <07c01c11-0cc2-4837-b371-1404f2ce3359@quicinc.com>
>
> __| |_______________| |__
> | PCS0 | |PCS1 |
> |______| |_____|
> |_______ |<---- REF clock 50MHZ
> | |------------ |
> |NSSCC | |clks |rsts|<---- GPIO reset
> |______| | | |
> | V V |
> |_______________________|
> | | | | |
> |PHY1 |PHY2 |PHY3 |PHY4 |
> |_____|_____|_____|_____|
Not the best of improvements. So the ref clock goes to the package,
and then magically somehow gets to the NSSCC? Are there any more
blocks it goes through before reaching the NSSCC? How does the GPIO
reset get converted into multiple reset inside the package? Details,
details, details.
> There are difference clock trees generated from NSSCC for the different
> PHYs, all clocks and resets for qca8084 CHIP working are internally
> provided by the NSSCC.
So show this in the block diagram.
> Yes, Andrew, the NSSCC provider driver is probed based on the MDIO
> device, the PHY CHIP occupies the MDIO addresses, so the NSSCC is
> registered as the MDIO device.
>
> DT of the NSSCC device node:
> mdio {
> #address-cells = <1>;
> #size-cells = <0>;
>
> clock-controller@18 {
> compatible = "qcom,qca8084-nsscc";
> reg = <0x18>;
> clocks = <&qca8k_xo>,
> <&qca8k_uniphy0_rx>,
> <&qca8k_uniphy0_tx>,
> <&qca8k_uniphy1_rx>,
> <&qca8k_uniphy1_tx>,
> <&qca8k_uniphy1_rx312p5m>,
> <&qca8k_uniphy1_tx312p5m>;
> #clock-cells = <1>;
> #reset-cells = <1>;
> #power-domain-cells = <1>;
> };
> };
This does not make any sense. You have one clock input, 50MHz. So why
are you listing 6 consumer clocks, not one? And where are the clocks
this clock controller provides, clock-output-names=<...>;
I give up. Please consider this PHY driver NACKed.
Get Linaro, or some other organisation with a lot of experience with
mainline to take over the work.
Andrew
next prev parent reply other threads:[~2024-01-09 13:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 1:53 [net-next PATCH RFC v3 0/8] net: phy: Support DT PHY package Christian Marangi
2023-11-26 1:53 ` [net-next PATCH RFC v3 1/8] dt-bindings: net: document ethernet PHY package nodes Christian Marangi
2023-11-27 22:16 ` Rob Herring
2023-11-28 0:09 ` Andrew Lunn
2024-01-07 18:00 ` Sergey Ryazanov
2024-01-07 18:30 ` Christian Marangi
2024-01-07 18:44 ` Andrew Lunn
2024-01-07 21:57 ` Sergey Ryazanov
2024-01-07 21:49 ` Sergey Ryazanov
2024-01-07 21:45 ` Christian Marangi
2024-01-17 0:36 ` Christian Marangi
2024-01-17 19:39 ` Sergey Ryazanov
2024-01-17 20:03 ` Christian Marangi
2024-01-17 20:05 ` Andrew Lunn
2024-01-07 18:31 ` Andrew Lunn
2024-01-08 11:13 ` Jie Luo
2024-01-08 13:19 ` Andrew Lunn
2024-01-09 11:44 ` Jie Luo
2024-01-09 13:48 ` Andrew Lunn [this message]
2024-01-10 3:13 ` Jie Luo
2023-11-26 1:53 ` [net-next PATCH RFC v3 2/8] net: phy: add initial support for PHY package in DT Christian Marangi
2023-11-28 0:39 ` Andrew Lunn
2023-11-28 12:09 ` Christian Marangi
2023-11-26 1:53 ` [net-next PATCH RFC v3 3/8] net: phy: add support for shared priv data size " Christian Marangi
2023-11-26 1:53 ` [net-next PATCH RFC v3 4/8] net: phy: add support for driver specific PHY package probe/config Christian Marangi
2023-11-26 1:53 ` [net-next PATCH RFC v3 5/8] dt-bindings: net: add QCA807x PHY defines Christian Marangi
2023-11-27 22:36 ` Rob Herring
2023-11-26 1:53 ` [net-next PATCH RFC v3 6/8] dt-bindings: net: Document Qcom QCA807x PHY package Christian Marangi
2023-11-27 22:35 ` Rob Herring
2023-11-28 0:30 ` Andrew Lunn
2023-11-26 1:53 ` [net-next PATCH RFC v3 7/8] net: phy: add Qualcom QCA807x driver Christian Marangi
2023-11-26 1:53 ` [net-next PATCH RFC v3 8/8] net: phy: qca807x: Add support for configurable LED Christian Marangi
2023-11-28 0:20 ` [net-next PATCH RFC v3 0/8] net: phy: Support DT PHY package Andrew Lunn
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=2f2328ee-205b-4b4f-a683-2df4fbb22dde@lunn.ch \
--to=andrew@lunn.ch \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ansuelsmth@gmail.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=quic_luoj@quicinc.com \
--cc=robert.marko@sartura.hr \
--cc=robh+dt@kernel.org \
--cc=ryazanov.s.a@gmail.com \
/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®