From: "Jérémie Dautheribes" <jeremie.dautheribes@bootlin.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Russell King" <linux@armlinux.org.uk>,
"Andrew Davis" <afd@ti.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Miquèl Raynal" <miquel.raynal@bootlin.com>,
"Yen-Mei Goh" <yen-mei.goh@keysight.com>,
"Maxime Chevallier" <maxime.chevallier@bootlin.com>
Subject: Re: [PATCH net-next 1/3] dt-bindings: net: dp83822: support configuring RMII master/slave mode
Date: Mon, 4 Mar 2024 17:31:59 +0100 [thread overview]
Message-ID: <70a00ad4-ee8e-4325-af09-b013247a003a@bootlin.com> (raw)
In-Reply-To: <d994001c-dff2-402d-bd19-7ddb0c148805@lunn.ch>
>>> We are normally interested in this 50Mhz reference clock. So i would
>>> drop all references to 25Mhz. It is not relevant to the binding, since
>>> it is nothing to do with connecting the PHY to the MAC, and it has a
>>> fixed value.
>>>
>>> So you can simplify this down to:
>>>
>>> RMII Master: Outputs a 50Mhz Reference clock which can be connected to the MAC.
>>>
>>> RMII Slave: Expects a 50MHz Reference clock input, shared with the
>>> MAC.
>>>
>>>> That said, would you like me to include this description (or some parts) in
>>>> the binding in addition to what I've already written? Or would you prefer me
>>>> to use a more meaningful property name?
>>>
>>> We don't really have any vendor agnostic consistent naming. dp83867
>>> and dp83869 seems to call this ti,clk-output-sel. Since this is
>>> another dp83xxx device, it would be nice if there was consistency
>>> between all these TI devices. So could you check if the concept is the
>>> same, and if so, change dp83826 to follow what other TI devices do.
>>
>>
>> So I had a look at this ti,clk-output-sel property on the TI DP8386x
>> bindings, but unfortunately it does not correspond to our use case. In their
>> case, it is used to select one of the various internal clocks to output on
>> the CLK_OUT pin.
>> In our case, we would prefer to describe the direction of the clock (OUT in
>> master mode, IN in slave mode).
>
> I would suggest we keep with the current property name, but simplify
> the description. Focus on the reference clock, and ignore the crystal.
Ok noted, thanks for your feedback! I will send a v2 containing a
simplified description + implement your suggested changes on patch 2.
Jérémie
next prev parent reply other threads:[~2024-03-04 16:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 10:31 [PATCH net-next 0/3] Add support for TI DP83826 configuration Jérémie Dautheribes
2024-02-22 10:31 ` [PATCH net-next 1/3] dt-bindings: net: dp83822: support configuring RMII master/slave mode Jérémie Dautheribes
2024-02-22 15:09 ` Krzysztof Kozlowski
2024-02-26 15:28 ` Andrew Lunn
2024-02-29 20:46 ` Jérémie Dautheribes
2024-02-29 21:23 ` Andrew Lunn
2024-03-04 15:12 ` Jérémie Dautheribes
2024-03-04 16:06 ` Andrew Lunn
2024-03-04 16:31 ` Jérémie Dautheribes [this message]
2024-02-22 10:31 ` [PATCH net-next 2/3] net: phy: dp83826: Add support for phy-mode configuration Jérémie Dautheribes
2024-02-23 11:16 ` Maxime Chevallier
2024-02-26 15:34 ` Andrew Lunn
2024-02-22 10:31 ` [PATCH net-next 3/3] net: phy: dp83826: support configuring RMII master/slave operation mode Jérémie Dautheribes
2024-02-26 11:40 ` [PATCH net-next 0/3] Add support for TI DP83826 configuration patchwork-bot+netdevbpf
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=70a00ad4-ee8e-4325-af09-b013247a003a@bootlin.com \
--to=jeremie.dautheribes@bootlin.com \
--cc=afd@ti.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yen-mei.goh@keysight.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;
as well as URLs for NNTP newsgroup(s).