lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 30 May 2016 17:24:26 +0200 From: Andrew Lunn <andrew@...n.ch> To: Pramod Kumar <pramod.kumar@...adcom.com> Cc: Rob Herring <robh+dt@...nel.org>, Pawel Moll <pawel.moll@....com>, Mark Rutland <mark.rutland@....com>, Ian Campbell <ijc+devicetree@...lion.org.uk>, Kumar Gala <galak@...eaurora.org>, Catalin Marinas <catalin.marinas@....com>, Will Deacon <will.deacon@....com>, Kishon Vijay Abraham I <kishon@...com>, "David S. Miller" <davem@...emloft.net>, devicetree@...r.kernel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, bcm-kernel-feedback-list@...adcom.com, linux-arm-kernel@...ts.infradead.org Subject: Re: [PATCH 3/7] binding: mdio-mux: Add DT binding doc for Broadcom MDIO bus mutiplexer On Mon, May 30, 2016 at 12:40:47PM +0530, Pramod Kumar wrote: > Add DT binding doc for Broadcom MDIO bus mutiplexer driver. > > Signed-off-by: Pramod Kumar <pramod.kumar@...adcom.com> > --- > .../bindings/net/brcm,mdio-mux-iproc.txt | 64 ++++++++++++++++++++++ > 1 file changed, 64 insertions(+) > create mode 100644 Documentation/devicetree/bindings/net/brcm,mdio-mux-iproc.txt > > diff --git a/Documentation/devicetree/bindings/net/brcm,mdio-mux-iproc.txt b/Documentation/devicetree/bindings/net/brcm,mdio-mux-iproc.txt > new file mode 100644 > index 0000000..dd74ee0 > --- /dev/null > +++ b/Documentation/devicetree/bindings/net/brcm,mdio-mux-iproc.txt > @@ -0,0 +1,64 @@ > +Properties for an MDIO bus mutiplexer found in Broadcom iProc based SoCs. > + > +This MDIO bus multiplexer defines buses that could be internal as well as > +external to SoCs and could accept MDIO transaction compatible to C-22 or > +C-45 Clause. When Child bus is selected, one need to select these two > +properties as well to generate desired MDIO trascation on appropriate bus. > + > +Required properties in addition to the generic multiplexer properties: > + > +MDIO multiplexer node: > +- complatible: brcm,mdio-mux-iproc. > + > +Child bus node: > +-brcm,is-c45: Boolean property indicating PHYs attached to this bus supports > + C-45 mdio transaction. This is-c45 seems to be at the wrong level. As far as i know, you can mix C22 and C45 devices on a bus. It is a property of the individual MDIO device if it uses C45 or not. I would expect your MDIO device PHY drivers to logically OR MII_ADDR_C45 into the address when doing an MDIO read/write using C45. Andrew
Powered by blists - more mailing lists