From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Stas Sergeev <stsp@users.sourceforge.net>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] mvneta: add FIXED_PHY dependency
Date: Mon, 9 Nov 2015 17:31:30 +0000 [thread overview]
Message-ID: <20151109173130.GF8644@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4827390.CWKT8ytt79@wuerfel>
On Mon, Nov 09, 2015 at 06:12:02PM +0100, Arnd Bergmann wrote:
> On Monday 09 November 2015 17:08:34 Russell King - ARM Linux wrote:
> > They are "optional" because when you're using a DSA switch, you don't
> > specify a PHY (because, there isn't one). For example, this is what
> > I'm using with an Armada 388 board with a Marvell DSA switch. The
> > DSA does not appear as a PHY, and no node in the DSA stanza can be
> > referenced for a phy entry in the ethernet device's stanza.
> >
> > eth1: ethernet@30000 {
> > compatible = "marvell,armada-370-neta";
> > reg = <0x30000 0x4000>;
> > interrupts-extended = <&mpic 10>;
> > clocks = <&gateclk 3>;
> > managed = "in-band-status";
> > phy-mode = "sgmii";
> > status = "okay";
> > };
> >
> >
>
> Ok, then it would be nice to change the binding to reflect that,
> and also document the "managed" property there.
"managed" is already documented. See
Documentation/devicetree/bindings/net/ethernet.txt:
- managed: string, specifies the PHY management type. Supported values are:
"auto", "in-band-status". "auto" is the default, it usess MDIO for
management if fixed-link is not specified.
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-11-09 17:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 14:08 Arnd Bergmann
2015-11-09 16:36 ` David Miller
2015-11-09 16:42 ` Andrew Lunn
2015-11-09 16:57 ` Arnd Bergmann
2015-11-09 17:08 ` Russell King - ARM Linux
2015-11-09 17:12 ` Arnd Bergmann
2015-11-09 17:31 ` Russell King - ARM Linux [this message]
2015-11-09 17:08 ` Andrew Lunn
2015-11-09 17:14 ` Arnd Bergmann
2015-11-09 17:33 ` Russell King - ARM Linux
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=20151109173130.GF8644@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stsp@users.sourceforge.net \
--cc=thomas.petazzoni@free-electrons.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®