From: Sascha Hauer <s.hauer@pengutronix.de>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <florian@openwrt.org>,
Lior Amsalem <alior@marvell.com>,
netdev@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 1/3] of: provide a binding for the 'fixed-link' property
Date: Mon, 12 Aug 2013 08:38:06 +0200 [thread overview]
Message-ID: <20130812063806.GD2324@pengutronix.de> (raw)
In-Reply-To: <1373902450-11857-2-git-send-email-thomas.petazzoni@free-electrons.com>
On Mon, Jul 15, 2013 at 05:34:08PM +0200, Thomas Petazzoni wrote:
> Some Ethernet MACs have a "fixed link", and are not connected to a
> normal MDIO-managed PHY device. For those situations, a Device Tree
> binding allows to describe a "fixed link", as a "fixed-link" property
> of the Ethernet device Device Tree node.
>
> This patch adds:
>
> * A documentation for the Device Tree property "fixed-link".
>
> * A of_phy_register_fixed_link() OF helper, which provided an OF node
> that contains a "fixed-link" property, registers the corresponding
> fixed PHY.
>
> * Removes the warning on the of_phy_connect_fixed_link() that says
> new drivers should not use it, since Grant Likely indicated that
> this "fixed-link" property is indeed the way to go.
>
Any progress with this series?
We have more and more boards here with exactly the same problem as
Thomas has. For reasons stated below I don't like this binding, but
still it would solve my problem.
> +Fixed link Device Tree binding
> +------------------------------
> +
> +Some Ethernet MACs have a "fixed link", and are not connected to a
> +normal MDIO-managed PHY device. For those situations, a Device Tree
> +binding allows to describe a "fixed link".
> +
> +Such a fixed link situation is described within an Ethernet device
> +Device Tree node using a 'fixed-link' property, composed of 5
> +elements:
> +
> + 1. A fake PHY ID, which must be unique accross all fixed-link PHYs in
> + the system.
> + 2. The duplex (1 for full-duplex, 0 for half-duplex)
> + 3. The speed (10, 100, 1000)
> + 4. The pause setting (1 for enabled, 0 for disabled)
> + 5. The asym pause setting (1 for enabled, 0 for disabled)
> +
> +Example:
> +
> +ethernet@0 {
> + ...
> + fixed-link = <1 1 1000 0 0>;
> + ...
> +};
I must say I don't like this binding at all for two reasons.
First the positional arguments make it impossible to add optional
arguments to the link.
Second the other side of the link is most likely a switch. Once this
switch has its own node in the devicetree it seems like having a phandle
to the switch here would be better.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2013-08-12 6:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 15:34 [RFC PATCH 0/3] Add DT support for fixed PHYs Thomas Petazzoni
2013-07-15 15:34 ` [RFC PATCH 1/3] of: provide a binding for the 'fixed-link' property Thomas Petazzoni
2013-07-15 15:50 ` Florian Fainelli
2013-07-23 11:22 ` Mark Rutland
2013-07-23 11:39 ` Florian Fainelli
2013-07-30 9:16 ` Thomas Petazzoni
2013-07-30 10:26 ` Florian Fainelli
2013-07-30 15:28 ` Mark Rutland
2013-07-23 11:39 ` Grant Likely
2013-07-30 9:07 ` Thomas Petazzoni
2013-07-30 10:05 ` Florian Fainelli
2013-07-30 11:23 ` Thomas Petazzoni
2013-07-30 11:43 ` Florian Fainelli
2013-07-30 15:31 ` Mark Rutland
2013-08-12 6:38 ` Sascha Hauer [this message]
2013-08-12 8:16 ` Thomas Petazzoni
2013-08-12 8:37 ` Sascha Hauer
2013-08-21 10:55 ` Christian Gmeiner
2013-08-21 11:25 ` Florian Fainelli
2013-08-21 11:46 ` Florian Fainelli
2013-07-15 15:34 ` [RFC PATCH 2/3] net: phy: call mdiobus_scan() after adding a fixed PHY Thomas Petazzoni
2013-07-15 15:46 ` Florian Fainelli
2013-07-15 15:34 ` [RFC PATCH 3/3] net: mvneta: add support for fixed links Thomas Petazzoni
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=20130812063806.GD2324@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=alior@marvell.com \
--cc=davem@davemloft.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=florian@openwrt.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--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;
as well as URLs for NNTP newsgroup(s).