On Tuesday 07 January 2014 22:03:11 Hans de Goede wrote: > >> + > >> +Optional properties: > >> + - clocks: array of clocks > >> + - clock-names: clock names "ahb" and/or "ohci" > > > > Where does "ahb" come from, what does it mean, and how is it relevant > > to generic platforms? > > ahb is an ARM specific thing, so your right it does not belong in a > generic driver. I'll use clk1 and clk2 as names in my next version. While AHB is a bus created by ARM Ltd, it's not actually specific to the ARM architecture. My guess is that it is in fact used on 95% of all SoCs, so I would leave it at that. For the other clock, I think that's actually the bus clock for the USB interface, so I would not call it "ohci" but rather just "usb" or "phy". I think it's important to distinguish the names and not just use "clk1" and "clk2", because the driver may actually want to access a particular clock in some scenario. > > What about platforms that use 3 clocks? > > Ah yes I see some platforms have 3 clocks, I'll also add a clk3. I guess we should try to find at least one hardware data sheet for an actual ohci implementation and look at what the clock inputs are really called. A lot of the drivers seem to incorrectly use the name for the clock signal inside of the soc, which tends to be named after who provides it, not what it's used for. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
