[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4840680.vVGZYBJBID@wuerfel>
Date: Wed, 08 Jan 2014 11:40:14 +0100
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Roger Quadros <rogerq@...com>, devicetree@...r.kernel.org,
Samuel Ortiz <sameo@...ux.intel.com>, tony@...mide.com,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
balbi@...com, "Kristo, Tero" <t-kristo@...com>,
bcousson@...libre.com, linux-omap@...r.kernel.org,
Lee Jones <lee.jones@...aro.org>
Subject: Re: [PATCH v4 1/5] mfd: omap-usb-host: Update DT clock binding information
On Wednesday 08 January 2014 15:57:19 Roger Quadros wrote:
> It is a clock gate defined like so in the DT clock data
>
> on OMAP4
> init_60m_fclk: init_60m_fclk {
> #clock-cells = <0>;
> compatible = "ti,divider-clock";
> clocks = <&dpll_usb_m2_ck>;
> reg = <0x0104>;
> ti,dividers = <1>, <8>;
> };
>
> on OMAP5
> l3init_60m_fclk: l3init_60m_fclk {
> #clock-cells = <0>;
> compatible = "ti,divider-clock";
> clocks = <&dpll_usb_m2_ck>;
> reg = <0x0104>;
> ti,dividers = <1>, <8>;
> };
>
> So you can see that it is the same thing with a different name.
Right, but init_60m_fclk is the name of the clock output of the
divider here, which is /not/ what you should put in the "clock-names"
property of the consumer. The clock input name should reflect what
the clock is used for instead.
Arnd
--
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