From: Conor Dooley <conor@kernel.org>
To: Ryan.Wanner@microchip.com
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
nicolas.ferre@microchip.com, claudiu.beznea@tuxon.dev,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: net: cdns,macb: Add external REFCLK property
Date: Fri, 20 Jun 2025 15:22:41 +0100 [thread overview]
Message-ID: <20250620-giveaway-crazily-e8afbe8a7b5a@spud> (raw)
In-Reply-To: <7f9c7308e404a6bcebdc8cc65ccf188dde435924.1750346271.git.Ryan.Wanner@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 1631 bytes --]
On Thu, Jun 19, 2025 at 10:04:13AM -0700, Ryan.Wanner@microchip.com wrote:
> From: Ryan Wanner <Ryan.Wanner@microchip.com>
>
> REFCLK can be provided by an external source so this should be exposed
> by a DT property. The REFCLK is used for RMII and in some SoCs that use
> this driver the RGMII 125MHz clk can also be provided by an external
> source.
>
> Signed-off-by: Ryan Wanner <Ryan.Wanner@microchip.com>
> ---
> Documentation/devicetree/bindings/net/cdns,macb.yaml | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/cdns,macb.yaml b/Documentation/devicetree/bindings/net/cdns,macb.yaml
> index 8d69846b2e09..e69f60c37793 100644
> --- a/Documentation/devicetree/bindings/net/cdns,macb.yaml
> +++ b/Documentation/devicetree/bindings/net/cdns,macb.yaml
> @@ -114,6 +114,13 @@ properties:
> power-domains:
> maxItems: 1
>
> + cdns,refclk-ext:
> + type: boolean
> + description:
> + This selects if the REFCLK for RMII is provided by an external source.
> + For RGMII mode this selects if the 125MHz REF clock is provided by an external
> + source.
If this gets a v2, is the distinction between RMII and RGMII worth
mentioning? Or is that mentioned because the property has no effect for
!{RGMII,RMII} usecases?
I'm okay with the property existing, though so
Acked-by: Conor Dooley <conor.dooley@microchip.com>
if it's the latter or with an improved description for the former.
> +
> cdns,rx-watermark:
> $ref: /schemas/types.yaml#/definitions/uint32
> description:
> --
> 2.43.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-06-20 14:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 17:04 [PATCH 0/3] Expose REFCLK for RMII and enable RMII Ryan.Wanner
2025-06-19 17:04 ` [PATCH 1/3] dt-bindings: net: cdns,macb: Add external REFCLK property Ryan.Wanner
2025-06-20 14:22 ` Conor Dooley [this message]
2025-06-19 17:04 ` [PATCH 2/3] net: cadence: macb: Expose REFCLK as a device tree property Ryan.Wanner
2025-06-20 10:25 ` Simon Horman
2025-06-19 17:04 ` [PATCH 3/3] net: cadence: macb: Enable RMII for SAMA7 gem Ryan.Wanner
2025-06-21 7:24 ` [PATCH 0/3] Expose REFCLK for RMII and enable RMII Andrew Lunn
2025-06-23 16:16 ` Ryan Wanner
2025-06-23 17:47 ` 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=20250620-giveaway-crazily-e8afbe8a7b5a@spud \
--to=conor@kernel.org \
--cc=Ryan.Wanner@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.com \
--cc=robh@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