On 04/06/2015 at 23:08:03 +0200, Philippe Reynes wrote :
> >You are getting the rate but don't you need to clk_prepare_enable()?
>
> This IP needs the clock reference rate for his configuration,
> so I think that I only need the rate.
>
I think we need to check whether we are guaranteed to get a
Hi Alexandre,
On 28/05/15 13:57, Alexandre Belloni wrote:
Hi,
On 16/05/2015 at 00:35:29 +0200, Philippe Reynes wrote :
The mxc RTC needs two clocks, one for the input
reference, and one for the IP. But this driver
was only using one clock (for the reference).
This patch add the second clock (f
Hi,
On 16/05/2015 at 00:35:29 +0200, Philippe Reynes wrote :
> The mxc RTC needs two clocks, one for the input
> reference, and one for the IP. But this driver
> was only using one clock (for the reference).
> This patch add the second clock (for the IP).
>
> Signed-off-by: Philippe Reynes
> ---
On Sat, May 16, 2015 at 12:35:29AM +0200, Philippe Reynes wrote:
> The mxc RTC needs two clocks, one for the input
> reference, and one for the IP. But this driver
> was only using one clock (for the reference).
> This patch add the second clock (for the IP).
>
> Signed-off-by: Philippe Reynes
>
Hi Enrico,
On 18/05/15 13:27, Enrico Weigelt, metux IT consult wrote:
Am 16.05.2015 um 00:35 schrieb Philippe Reynes:
The mxc RTC needs two clocks, one for the input
reference, and one for the IP. But this driver
was only using one clock (for the reference).
This patch add the second clock (for
Am 16.05.2015 um 00:35 schrieb Philippe Reynes:
The mxc RTC needs two clocks, one for the input
reference, and one for the IP. But this driver
was only using one clock (for the reference).
This patch add the second clock (for the IP).
Does this also apply to MX53, or just MX21 ?
greetings,
-
6 matches
Mail list logo
