From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: "Florian Fainelli" <florian@openwrt.org>,
netdev <netdev@vger.kernel.org>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"Gregory Clément" <gregory.clement@free-electrons.com>,
"Ezequiel Garcia" <ezequiel.garcia@free-electrons.com>,
"Lior Amsalem" <alior@marvell.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"Andy Fleming" <afleming@freescale.com>
Subject: Re: Fixed PHY Device Tree usage?
Date: Sat, 13 Jul 2013 19:02:06 +0200 [thread overview]
Message-ID: <20130713190206.2a617983@skate> (raw)
In-Reply-To: <CACxGe6tzMhjH8nxJ1Ezrc43DqCmv-pWRW2NsXa=fP-6Fh_t5PA@mail.gmail.com>
Dear Grant Likely,
On Fri, 12 Jul 2013 23:44:21 +0100, Grant Likely wrote:
> I think this discussion is going in the wrong direction. The concept
> of a dummy phy is really a Linux kernel internal detail. Creating some
> kind of dummy MDIO bus node does not describe the hardware.
This is exactly what I was suggesting in my original e-mail of this
thread, see http://marc.info/?l=linux-netdev&m=137338762627063&w=2 :
"""
One option is to implement a Device Tree binding for the fixed PHY
driver (the exact DT binding would have to be discussed), but I'm
wondering whether describing a fixed PHY in the DT is actually correct,
because describing a fixed PHy is not really describing the hardware,
the hardware is actually a switch.
"""
> There is
> already support in the kernel for Ethernet MACs connected directly to
> a switch or other device. It is far better to describe how the MAC
> needs to be configured than to invent a non-existent phy. Search for
> "fixed-link" in the kernel tree to see how it is used.
As Florian pointed out, the of_phy_connect_fixed_link() comment
indicates:
* This function is a temporary stop-gap and will be removed soon. It is
* only to support the fs_enet, ucc_geth and gianfar Ethernet drivers. Do
* not call this function from new drivers.
Also, it would probably be good to have a few more helpers to make
parsing the "phy" and "fixed-link" property easier for network drivers.
Thanks for your feedback,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-07-13 17:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 16:33 Fixed PHY Device Tree usage? Thomas Petazzoni
2013-07-09 16:44 ` Florian Fainelli
2013-07-09 18:02 ` Florian Fainelli
2013-07-10 16:22 ` Thomas Petazzoni
2013-07-10 16:29 ` Florian Fainelli
2013-07-10 16:39 ` Thomas Petazzoni
2013-07-10 17:23 ` Florian Fainelli
2013-07-12 11:56 ` Thomas Petazzoni
2013-07-12 12:05 ` Florian Fainelli
2013-07-12 13:04 ` Thomas Petazzoni
2013-07-12 22:44 ` Grant Likely
2013-07-12 23:29 ` Florian Fainelli
2013-07-13 17:02 ` Thomas Petazzoni [this message]
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=20130713190206.2a617983@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=afleming@freescale.com \
--cc=alior@marvell.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=florian@openwrt.org \
--cc=grant.likely@secretlab.ca \
--cc=gregory.clement@free-electrons.com \
--cc=netdev@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.