From: David Daney <ddaney.cavm@gmail.com>
To: Tabi Timur-B04825 <B04825@freescale.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 15:03:20 -0700 [thread overview]
Message-ID: <4FB6C728.3090507@gmail.com> (raw)
In-Reply-To: <CAOZdJXWVCu+aNxcQRkcSSDsWWxnn8B9X5Y6=8oVgFwJ9SZTTGQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
On 05/18/2012 02:42 PM, Tabi Timur-B04825 wrote:
> On Wed, May 2, 2012 at 8:16 PM, David Daney<ddaney.cavm@gmail.com> wrote:
>> From: David Daney<david.daney@cavium.com>
>>
>> This code has been working well for about six months on a couple of
>> different configurations (boards), so I thought it would be a good
>> time to send it out again, and I hope get it on the path towards
>> merging.
>
> David,
>
> I'm trying to implement this feature on our boards, which don't use
> GPIOs but rather a memory-mapped FPGA. I control the mux by setting
> some bits in one of the FPGA registers.
You can either:
1) write a standard GPIO driver for the thing that controls the mux, and
then use mdio-mux-gpio.c, or...
2) Write a new driver modeled on mdio-mux-gpio.c for your switch control.
>
> Do you have a real device tree I can use as an example?
>
Attached.
> 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.
>, which in our case would be the FPGA?
I have no idea what your FPGA implements, so it is hard to say.
A sane person would implement a separate MDIO STA controller for each
bus, in which case you wouldn't use the multiplexer driver.
Only people dealing with insane hardware need the multiplexer. The
patch in net-next has a nice ASCII art picture of such an insane design.
David Daney
[-- Attachment #2: ebb6600.dts --]
[-- Type: audio/vnd.dts, Size: 16812 bytes --]
next prev parent reply other threads:[~2012-05-18 22:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1336007799-31016-1-git-send-email-ddaney.cavm@gmail.com>
2012-05-18 21:42 ` [PATCH v6 0/3] netdev/of/phy: MDIO bus multiplexer support Tabi Timur-B04825
2012-05-18 22:03 ` David Daney [this message]
2012-05-18 22:09 ` Timur Tabi
2012-05-18 22:23 ` David Daney
2012-05-24 18:28 ` Timur Tabi
2012-05-24 18:50 ` David Daney
2012-05-24 19:03 ` Timur Tabi
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=4FB6C728.3090507@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=B04825@freescale.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 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).