[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140305091212.GA10380@lee--X1>
Date: Wed, 5 Mar 2014 17:12:12 +0800
From: Lee Jones <lee.jones@...aro.org>
To: Mark Rutland <mark.rutland@....com>
Cc: "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"alexandre.torgue@...com" <alexandre.torgue@...com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@...com>
Subject: Re: [PATCH 1/4] phy: miphy365x: Add Device Tree bindings for the
MiPHY365x
> > > +Specifying phy control of devices
> > > +=================================
> > > +
> > > +Device nodes should specify the configuration required in their "phys"
> > > +property, containing a phandle to the miphy device node, a port number
> > > +and a device type.
> > > +
> > > +Example:
> > > +
> > > +#include <dt-bindings/phy/phy-miphy365x.h>
> > > +
> > > + sata0: sata@...80000 {
> > > + ...
> > > + phys = <&miphy365x_phy MIPHY_PORT_0 MIPHY_TYPE_SATA>;
> > > + ...
> > > + };
> >
> > Is there not a generic phy binding we can point to? It seems a bit
> > redundant to do this in each phy binding.
>
> Sure, but that wouldn't make much of an example.
>
> Documentation/devicetree/bindings/phy/phy-bindings.txt
Ah sorry, I see what you mean now.
No, not yet. That's the next thing to go up into Mainline.
I will replace this second example with a link when the other
documentation document has been accepted.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists