From: David Daney <ddaney.cavm@gmail.com>
To: Timur Tabi <timur@freescale.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>
Cc: 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:24:05 -0700 [thread overview]
Message-ID: <50355C05.6000407@gmail.com> (raw)
In-Reply-To: <1345671954-6398-1-git-send-email-timur@freescale.com>
On 08/22/2012 02:45 PM, Timur Tabi wrote:
> An FPGA controls which sub-bus is connected to the master MDIO bus. The
> FPGA must be memory-mapped and contain only 8-bit registers (which keeps
> things simple).
>
> Tested on a Freescale P5020DS board which uses the "PIXIS" FPGA attached
> to the localbus.
>
> Signed-off-by: Timur Tabi <timur@freescale.com>
> ---
> .../devicetree/bindings/net/mdio-mux-fpga.txt | 74 ++++++++
> drivers/net/phy/Kconfig | 13 ++
> drivers/net/phy/Makefile | 1 +
> drivers/net/phy/mdio-mux-fpga.c | 186 ++++++++++++++++++++
I am fine with the general concept of the patch, so I am going to start
a Bike Shedding session with it over the names of some of the things here.
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.
> 4 files changed, 274 insertions(+), 0 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/net/mdio-mux-fpga.txt
> create mode 100644 drivers/net/phy/mdio-mux-fpga.c
>
> diff --git a/Documentation/devicetree/bindings/net/mdio-mux-fpga.txt b/Documentation/devicetree/bindings/net/mdio-mux-fpga.txt
> new file mode 100644
> index 0000000..ef567c6
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/mdio-mux-fpga.txt
> @@ -0,0 +1,74 @@
> +Properties for an MDIO bus multiplexer/switch controlled by an FPGA register.
> +
> +This is a special case of a MDIO bus multiplexer. An FPGA register is used
> +to control which child bus is connected.
> +
> +Required properties in addition to the generic multiplexer properties:
> +
> +- compatible : string, must contain "mdio-mux-fpga"
> +
> +- 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.
> +
> +- mdio-mux-register : integer, contains the offset of the register that
> + controls the bus multiplexer.
This should just be the normal "reg" properly
> +
> +- mdio-mux-mask : integer, contains an 8-bit mask that specifies which
> + bits in the register control the actual bus multiplexer. The
> + 'reg' property of each child mdio-mux node must be constrained by
> + this mask.
> +
"reg-mask" ??
Do you need a shift too?
David Daney
next parent reply other threads:[~2012-08-22 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1345671954-6398-1-git-send-email-timur@freescale.com>
2012-08-22 22:24 ` David Daney [this message]
2012-08-22 22:38 ` [PATCH] netdev/phy: add MDIO bus multiplexer driven by a memory-mapped FPGA Timur Tabi
2012-08-22 22:52 ` David Daney
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=50355C05.6000407@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=afleming@freescale.com \
--cc=davem@davemloft.net \
--cc=david.daney@cavium.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).