From: David Daney <ddaney@caviumnetworks.com>
To: Timur Tabi <timur@freescale.com>
Cc: David Daney <ddaney.cavm@gmail.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
Andy Fleming <afleming@freescale.com>,
David Miller <davem@davemloft.net>, <netdev@vger.kernel.org>,
<david.daney@cavium.com>
Subject: Re: [PATCH] netdev/phy: add MDIO bus multiplexer driven by a memory-mapped FPGA
Date: Wed, 22 Aug 2012 15:52:32 -0700 [thread overview]
Message-ID: <503562B0.3010005@caviumnetworks.com> (raw)
In-Reply-To: <50355F6D.4070002@freescale.com>
On 08/22/2012 03:38 PM, Timur Tabi wrote:
> David Daney wrote:
>
>> I wonder if *fpga is really a good name for this. It is a general
>> purpose multiplexer with a memory mapped control register. I would call
>> it something like mdio-mux-mmioreg.
>
> At one point, I thought of using mdio-mux-bitbang, but -mmioreg is better.
> Thanks.
>
>>> +- mdio-mux-device : phandle, points to the FPGA (or similar) node. This
>>> + must be a memory-mapped device with 8-bit registers.
>>
>> You shouldn't need this. Just make the multiplexer a child of FPGA node
>> to indicate where it lives.
>
> The problem is that we don't normally consider the FPGA node to be a bus,
> so its child nodes won't get probed. That's why I have this:
>
That would seem to be a mistake/error.
You should be able to arrive at any directly addressable register by
walking down the tree to the children and applying any "ranges"
properties at each node. The OF infrastructure will take care of
resolving all the addresses and you get rid of much of the code you
added to duplicate its function.
next prev parent reply other threads:[~2012-08-22 22:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 21:45 [PATCH] netdev/phy: add MDIO bus multiplexer driven by a memory-mapped FPGA Timur Tabi
2012-08-22 22:24 ` David Daney
2012-08-22 22:38 ` Timur Tabi
2012-08-22 22:52 ` David Daney [this message]
2012-08-23 0:06 ` Tabi Timur-B04825
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=503562B0.3010005@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=afleming@freescale.com \
--cc=davem@davemloft.net \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=timur@freescale.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).