Re: [PATCH] clocksource/drivers/timer-ti-dm: Do one override clock parent in prepare()

2020-05-20 Thread Daniel Lezcano
On 05/05/2020 20:07, Tony Lindgren wrote: > * Tony Lindgren [200428 18:23]: >> * Lokesh Vutla [200427 17:29]: >>> omap_dm_timer_prepare() is setting up the parent 32KHz clock. This >>> prepare() gets called by request_timer in the client's driver. Because of >>> this, the timer clock parent that

Re: [PATCH] clocksource/drivers/timer-ti-dm: Do one override clock parent in prepare()

2020-05-05 Thread Tony Lindgren
* Tony Lindgren [200428 18:23]: > * Lokesh Vutla [200427 17:29]: > > omap_dm_timer_prepare() is setting up the parent 32KHz clock. This > > prepare() gets called by request_timer in the client's driver. Because of > > this, the timer clock parent that is set with assigned-clock-parent is being >

Re: [PATCH] clocksource/drivers/timer-ti-dm: Do one override clock parent in prepare()

2020-05-05 Thread Suman Anna
On 4/28/20 1:22 PM, Tony Lindgren wrote: * Lokesh Vutla [200427 17:29]: omap_dm_timer_prepare() is setting up the parent 32KHz clock. This prepare() gets called by request_timer in the client's driver. Because of this, the timer clock parent that is set with assigned-clock-parent is being

Re: [PATCH] clocksource/drivers/timer-ti-dm: Do one override clock parent in prepare()

2020-04-28 Thread Tony Lindgren
* Lokesh Vutla [200427 17:29]: > omap_dm_timer_prepare() is setting up the parent 32KHz clock. This > prepare() gets called by request_timer in the client's driver. Because of > this, the timer clock parent that is set with assigned-clock-parent is being > overwritten. So drop this default