From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: George Moussalem <george.moussalem@outlook.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
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>,
Florian Fainelli <f.fainelli@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH 1/5] dt-bindings: net: qca,ar803x: Add IPQ5018 Internal GE PHY support
Date: Tue, 27 May 2025 15:00:07 +0200 [thread overview]
Message-ID: <7d8c3a31-cba3-40b9-8cba-52d782e5cf00@oss.qualcomm.com> (raw)
In-Reply-To: <DS7PR19MB88838F05ADDD3BDF9B08076C9D64A@DS7PR19MB8883.namprd19.prod.outlook.com>
On 5/27/25 2:13 PM, George Moussalem wrote:
>
>
> On 5/27/25 15:31, Konrad Dybcio wrote:
>> On 5/27/25 1:28 PM, George Moussalem wrote:
>>> Hi Konrad,
>>>
>>> On 5/27/25 14:59, Konrad Dybcio wrote:
>>>> On 5/26/25 2:55 PM, Krzysztof Kozlowski wrote:
>>>>> On 26/05/2025 08:43, George Moussalem wrote:
>>>>>>>> + qca,dac:
>>>>>>>> + description:
>>>>>>>> + Values for MDAC and EDAC to adjust amplitude, bias current settings,
>>>>>>>> + and error detection and correction algorithm. Only set in a PHY to PHY
>>>>>>>> + link architecture to accommodate for short cable length.
>>>>>>>> + $ref: /schemas/types.yaml#/definitions/uint32-array
>>>>>>>> + items:
>>>>>>>> + - items:
>>>>>>>> + - description: value for MDAC. Expected 0x10, if set
>>>>>>>> + - description: value for EDAC. Expected 0x10, if set
>>>>>>>
>>>>>>> If this is fixed to 0x10, then this is fully deducible from compatible.
>>>>>>> Drop entire property.
>>>>>>
>>>>>> as mentioned to Andrew, I can move the required values to the driver
>>>>>> itself, but a property would still be required to indicate that this PHY
>>>>>> is connected to an external PHY (ex. qca8337 switch). In that case, the
>>>>>> values need to be set. Otherwise, not..
>>>>>>
>>>>>> Would qcom,phy-to-phy-dac (boolean) do?
>>>>>
>>>>> Seems fine to me.
>>>>
>>>> Can the driver instead check for a phy reference?
>>>
>>> Do you mean using the existing phy-handle DT property or create a new DT property called 'qcom,phy-reference'? Either way, can add it for v2.
>>
>> I'm not sure how this is all wired up. Do you have an example of a DT
>> with both configurations you described in your reply to Andrew?
>
> Sure, for IPQ5018 GE PHY connected to a QCA8337 switch (phy to phy):
> Link: https://github.com/openwrt/openwrt/blob/main/target/linux/qualcommax/files/arch/arm64/boot/dts/qcom/ipq5018-spnmx56.dts
> In this scenario, the IPQ5018 single UNIPHY is freed up and can be used with an external PHY such as QCA8081 to offer up to 2.5 gbps connectivity, see diagram below:
>
> * =================================================================
> * _______________________ _______________________
> * | IPQ5018 | | QCA8337 |
> * | +------+ +--------+ | | +--------+ +------+ |
> * | | MAC0 |---| GE Phy |-+--- MDI ---+ | Phy4 |---| MAC5 | |
> * | +------+ +--------+ | | +--------+ +------+ |
> * | | |_______________________|
> * | | _______________________
> * | | | QCA8081 |
> * | +------+ +--------+ | | +--------+ +------+ |
> * | | MAC1 |---| Uniphy |-+-- SGMII+--+ | Phy |---| RJ45 | |
> * | +------+ +--------+ | | +--------+ +------+ |
> * |_______________________| |_______________________|
> *
> * =================================================================
>
> The other use case is when an external switch or PHY, if any, is connected to the IPQ5018 UNIPHY over SGMII(+), freeing up the GE PHY which can optionally be connected to an RJ45 connector. I haven't worked on such board yet where the GE PHY is directly connected to RJ45, but I believe the Linksys MX6200 has this architecture (which I'll look into soon).
>
> * =================================================================
> * _______________________ ____________
> * | IPQ5018 | | |
> * | +------+ +--------+ | | +--------+ |
> * | | MAC0 |---| GE Phy |-+--- MDI ---+ | RJ45 | +
> * | +------+ +--------+ | | +--------+ |
> * | | |____________|
> * | | _______________________
> * | | | QCA8081 Phy |
> * | +------+ +--------+ | | +--------+ +------+ |
> * | | MAC1 |---| Uniphy |-+-- SGMII+--+ | Phy |---| RJ45 | |
> * | +------+ +--------+ | | +--------+ +------+ |
> * |_______________________| |_______________________|
> *
> * =================================================================
So - with keeping in mind that I'm not a big networking guy - can we test
for whether there's an ethernet-switch present under the MDIO host and
decide based on that?
Konrad
next prev parent reply other threads:[~2025-05-27 13:00 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-25 17:56 [PATCH 0/5] Add support for the IPQ5018 Internal GE PHY George Moussalem via B4 Relay
2025-05-25 17:56 ` [PATCH 1/5] dt-bindings: net: qca,ar803x: Add IPQ5018 Internal GE PHY support George Moussalem via B4 Relay
2025-05-25 19:35 ` Andrew Lunn
2025-05-26 4:27 ` George Moussalem
2025-05-26 13:34 ` Andrew Lunn
2025-05-26 13:43 ` George Moussalem
2025-05-26 4:17 ` Krzysztof Kozlowski
2025-05-26 6:43 ` George Moussalem
2025-05-26 12:55 ` Krzysztof Kozlowski
2025-05-27 10:59 ` Konrad Dybcio
2025-05-27 11:28 ` George Moussalem
2025-05-27 11:31 ` Konrad Dybcio
2025-05-27 12:13 ` George Moussalem
2025-05-27 13:00 ` Konrad Dybcio [this message]
2025-05-27 13:03 ` George Moussalem
2025-05-27 13:08 ` Andrew Lunn
2025-05-27 13:15 ` Konrad Dybcio
2025-05-27 15:12 ` Andrew Lunn
2025-05-25 17:56 ` [PATCH 2/5] clk: qcom: gcc-ipq5018: fix GE PHY reset George Moussalem via B4 Relay
2025-05-27 11:00 ` Konrad Dybcio
2025-05-27 11:14 ` George Moussalem
2025-05-27 11:19 ` Konrad Dybcio
2025-05-25 17:56 ` [PATCH 3/5] net: phy: qcom: at803x: Add Qualcomm IPQ5018 Internal PHY support George Moussalem via B4 Relay
2025-05-25 19:42 ` Andrew Lunn
2025-05-26 4:28 ` George Moussalem
2025-05-25 17:56 ` [PATCH 4/5] arm64: dts: qcom: ipq5018: add MDIO buses George Moussalem via B4 Relay
2025-05-27 11:07 ` Konrad Dybcio
2025-05-27 11:23 ` George Moussalem
2025-05-25 17:56 ` [PATCH 5/5] arm64: dts: qcom: ipq5018: Add GE PHY to internal mdio bus George Moussalem via B4 Relay
2025-05-27 13:34 ` Konrad Dybcio
2025-05-27 13:36 ` George Moussalem
2025-05-27 17:56 ` [PATCH 0/5] Add support for the IPQ5018 Internal GE PHY Rob Herring (Arm)
2025-05-28 4:57 ` George Moussalem
2025-05-28 12:00 ` 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=7d8c3a31-cba3-40b9-8cba-52d782e5cf00@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=george.moussalem@outlook.com \
--cc=hkallweit1@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mturquette@baylibre.com \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.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