Hi, On Friday 23 May 2014 06:51 PM, Andrew Lunn wrote: > On Fri, May 23, 2014 at 02:54:02PM +0530, Kishon Vijay Abraham I wrote: >> Hi, >> >> On Friday 16 May 2014 09:52 PM, Gregory CLEMENT wrote: >>> Armada 375 comes with an USB2 host and device controller and an USB3 >>> controller. The USB cluster control register allows to manage common >>> features of both USB controllers. This commit adds the Device Tree >>> binding documentation for this piece of hardware. >> >> Pls re-order so that the Documentation patch comes before the driver patch.. >>> >>> Signed-off-by: Gregory CLEMENT <gregory.clement@xxxxxxxxxxxxxxxxxx> >>> --- >>> .../bindings/phy/armada-375-usb-phy-cluster.txt | 20 ++++++++++++++++++++ >>> 1 file changed, 20 insertions(+) >>> create mode 100644 Documentation/devicetree/bindings/phy/armada-375-usb-phy-cluster.txt >>> >>> diff --git a/Documentation/devicetree/bindings/phy/armada-375-usb-phy-cluster.txt b/Documentation/devicetree/bindings/phy/armada-375-usb-phy-cluster.txt >> >> simpler file name? armada-phy? > > Armada is a collection of families of SoCs. This driver is very > specific to one SoC, in one family of SoCs. > > Do you want one .txt file per driver, or can we combine binding > documentations into one file? There should already be a mvebu-phy.txt, > which contains the sata phy usable on some of the Armada SoC families. > This binding could be appended to it. So far we've been creating Documentation file per manufacturer (ti-phy.txt, samsung-phy.txt..), so would prefer if you could combine binding documentation in a single file. Thanks Kishon -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
