Hi, Daniel
> On 02/07/2019 11:03, Anson Huang wrote:
> > Hi, Daniel
> >
> >> Hi Anson,
> >>
> >> why did you resend the series?
> >
> > Previous patch series has build warning and I did NOT notice, sorry
> > for that,
> >
> > drivers/clocksource/timer-of.c: In function ‘timer_of_init’:
> >
On 02/07/2019 11:03, Anson Huang wrote:
> Hi, Daniel
>
>> Hi Anson,
>>
>> why did you resend the series?
>
> Previous patch series has build warning and I did NOT notice, sorry for that,
>
> drivers/clocksource/timer-of.c: In function ‘timer_of_init’:
> drivers/clocksource/timer-of.c:185:30:
Hi, Daniel
> Hi Anson,
>
> why did you resend the series?
Previous patch series has build warning and I did NOT notice, sorry for that,
drivers/clocksource/timer-of.c: In function ‘timer_of_init’:
drivers/clocksource/timer-of.c:185:30: warning: suggest parentheses around
comparison in operand
From: Anson Huang
More and more platforms use platform driver model for clock driver,
so the clock driver is NOT ready during timer initialization phase,
it will cause timer initialization failed.
To support those platforms with upper scenario, introducing a new
flag TIMER_OF_CLOCK_FREQUENCY
Hi Anson,
why did you resend the series?
On 02/07/2019 09:55, anson.hu...@nxp.com wrote:
> From: Anson Huang
>
> More and more platforms use platform driver model for clock driver,
> so the clock driver is NOT ready during timer initialization phase,
> it will cause timer initialization
5 matches
Mail list logo