From: Timur Tabi <b04825@freescale.com>
To: David Daney <ddaney.cavm@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v6 0/3] netdev/of/phy: MDIO bus multiplexer support.
Date: Fri, 18 May 2012 17:09:10 -0500 [thread overview]
Message-ID: <4FB6C886.3050105@freescale.com> (raw)
In-Reply-To: <4FB6C728.3090507@gmail.com>
David Daney wrote:
>> > I'm not sure what the "parent" MDIO bus node is supposed to represent.
>> > Is that that device that actually controls the muxing hardware
> No. It is the device that implements the master 802.3 clause {22,45}
> MDIO Station Management (STA) protocol.
Ah, I think I get it. It is *the* MDIO node that would normally exist if
muxing we're necessary on the board. From the looks of it, that node
would look exactly the same if you didn't need muxing?
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <b04825@freescale.com>
To: David Daney <ddaney.cavm@gmail.com>
Cc: "devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v6 0/3] netdev/of/phy: MDIO bus multiplexer support.
Date: Fri, 18 May 2012 17:09:10 -0500 [thread overview]
Message-ID: <4FB6C886.3050105@freescale.com> (raw)
In-Reply-To: <4FB6C728.3090507@gmail.com>
David Daney wrote:
>> > I'm not sure what the "parent" MDIO bus node is supposed to represent.
>> > Is that that device that actually controls the muxing hardware
> No. It is the device that implements the master 802.3 clause {22,45}
> MDIO Station Management (STA) protocol.
Ah, I think I get it. It is *the* MDIO node that would normally exist if
muxing we're necessary on the board. From the looks of it, that node
would look exactly the same if you didn't need muxing?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-05-18 22:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 1:16 [PATCH v6 0/3] netdev/of/phy: MDIO bus multiplexer support David Daney
2012-05-03 1:16 ` David Daney
2012-05-03 1:16 ` [PATCH v6 1/3] netdev/of/phy: New function: of_mdio_find_bus() David Daney
2012-05-03 1:16 ` David Daney
2012-05-03 1:16 ` David Daney
2012-05-08 2:58 ` David Miller
2012-05-03 1:16 ` [PATCH v6 2/3] netdev/of/phy: Add MDIO bus multiplexer support David Daney
2012-05-08 2:58 ` David Miller
2012-05-03 1:16 ` [PATCH v6 3/3] netdev/of/phy: Add MDIO bus multiplexer driven by GPIO lines David Daney
2012-05-03 1:16 ` David Daney
2012-05-08 2:59 ` David Miller
2012-05-18 21:42 ` [PATCH v6 0/3] netdev/of/phy: MDIO bus multiplexer support Tabi Timur-B04825
2012-05-18 21:42 ` Tabi Timur-B04825
2012-05-18 22:03 ` David Daney
2012-05-18 22:03 ` David Daney
2012-05-18 22:09 ` Timur Tabi [this message]
2012-05-18 22:09 ` Timur Tabi
2012-05-18 22:23 ` David Daney
2012-05-18 22:23 ` David Daney
2012-05-24 18:28 ` Timur Tabi
2012-05-24 18:28 ` Timur Tabi
2012-05-24 18:50 ` David Daney
2012-05-24 18:50 ` David Daney
2012-05-24 19:03 ` Timur Tabi
2012-05-24 19:03 ` Timur Tabi
2012-05-24 19:19 ` David Daney
2012-05-24 19:19 ` David Daney
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=4FB6C886.3050105@freescale.com \
--to=b04825@freescale.com \
--cc=ddaney.cavm@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
/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.