From: Andrew Lunn <andrew@lunn.ch>
To: Roelof Berg <rberg@berg-solutions.de>
Cc: Bryan Whitehead <bryan.whitehead@microchip.com>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lan743x: Added fixed link and RGMII support
Date: Fri, 29 May 2020 23:30:00 +0200 [thread overview]
Message-ID: <20200529213000.GO869823@lunn.ch> (raw)
In-Reply-To: <20200529193003.3717-1-rberg@berg-solutions.de>
On Fri, May 29, 2020 at 09:30:02PM +0200, Roelof Berg wrote:
> Microchip lan7431 is frequently connected to a phy. However, it
> can also be directly connected to a MII remote peer without
> any phy in between. For supporting such a phyless hardware setup
> in Linux we utilized phylib, which supports a fixed-link
> configuration via the device tree. And we added support for
> defining the connection type R/GMII in the device tree.
>
> New behavior:
> -------------
> . The automatic speed and duplex detection of the lan743x silicon
> between mac and phy is disabled. Instead phylib is used like in
> other typical Linux drivers. The usage of phylib allows to
> specify fixed-link parameters in the device tree.
>
> . The device tree entry phy-connection-type is supported now with
> the modes RGMII or (G)MII (default).
>
> Development state:
> ------------------
> . Tested with fixed-phy configurations. Not yet tested in normal
> configurations with phy. Microchip kindly offered testing
> as soon as the Corona measures allow this.
>
> . All review findings of Andrew Lunn are included
>
> Example:
> --------
> &pcie {
> status = "okay";
>
> host@0 {
> reg = <0 0 0 0 0>;
>
> #address-cells = <3>;
> #size-cells = <2>;
>
> ethernet@0 {
> compatible = "weyland-yutani,noscom1", "microchip,lan743x";
> status = "okay";
> reg = <0 0 0 0 0>;
> phy-connection-type = "rgmii";
>
> fixed-link {
> speed = <100>;
> full-duplex;
> };
> };
> };
> };
>
> Signed-off-by: Roelof Berg <rberg@berg-solutions.de>
Hi Roelof
It looks like you took my suggestion as a basis. So i should give you:
Signed-off-by: Andrew Lunn <andrew@lunn.ch>
since i did not include one in my posting. I'm happy to see it helped,
and fixed some other issues you were seeing.
Andrew
next prev parent reply other threads:[~2020-05-29 21:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 19:30 [PATCH] lan743x: Added fixed link and RGMII support Roelof Berg
2020-05-29 21:30 ` Andrew Lunn [this message]
2020-06-01 18:51 ` David Miller
2020-06-03 14:52 ` [PATCH] lan743x: Added fixed link and RGMII support / BROKEN PATCH Roelof Berg
2020-06-03 15:59 ` Andrew Lunn
2020-06-03 16:33 ` [PATCH] lan743x: Added fixed link and RGMII support / debugging Roelof Berg
2020-06-03 18:06 ` Andrew Lunn
2020-06-03 18:31 ` Roelof Berg
2020-06-03 22:02 ` Roelof Berg
2020-06-03 16:36 ` Roelof Berg
2020-06-03 18:02 ` Andrew Lunn
[not found] ` <08FC216E-BBCA-40E6-8251-FA1EB3EF9F99@berg-solutions.de>
2020-06-03 15:10 ` [PATCH] lan743x: Added fixed link and RGMII support / Options for proceeding ? Roelof Berg
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=20200529213000.GO869823@lunn.ch \
--to=andrew@lunn.ch \
--cc=UNGLinuxDriver@microchip.com \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rberg@berg-solutions.de \
/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).