Re: [PATCH] clockevents/drivers/cs5535: Un-break driver with 'set-state' interface

2017-01-04 Thread David Gstir
Hi Daniel, > On 04.01.2017, at 15:19, Daniel Lezcano wrote: > > On 02/01/2017 10:34, Viresh Kumar wrote: > > [ ... ] > >>> --- a/drivers/clocksource/cs5535-clockevt.c >>> +++ b/drivers/clocksource/cs5535-clockevt.c >>> @@ -117,7 +117,8 @@ static irqreturn_t

Re: [PATCH] clockevents/drivers/cs5535: Un-break driver with 'set-state' interface

2017-01-04 Thread David Gstir
Hi Daniel, > On 04.01.2017, at 15:19, Daniel Lezcano wrote: > > On 02/01/2017 10:34, Viresh Kumar wrote: > > [ ... ] > >>> --- a/drivers/clocksource/cs5535-clockevt.c >>> +++ b/drivers/clocksource/cs5535-clockevt.c >>> @@ -117,7 +117,8 @@ static irqreturn_t mfgpt_tick(int irq, void *dev_id)

Re: [PATCH] clockevents/drivers/cs5535: Un-break driver with 'set-state' interface

2017-01-02 Thread Viresh Kumar
On 28-12-16, 22:56, David Gstir wrote: > Since migrating to the 'set-state' interface the cs5535 driver causes a > crash after loading: Right after initialization, the IRQ handler > (mfgpt_tick) is triggered with clock event device in detached state. This > state not properly handled and causes a

Re: [PATCH] clockevents/drivers/cs5535: Un-break driver with 'set-state' interface

2017-01-02 Thread Viresh Kumar
On 28-12-16, 22:56, David Gstir wrote: > Since migrating to the 'set-state' interface the cs5535 driver causes a > crash after loading: Right after initialization, the IRQ handler > (mfgpt_tick) is triggered with clock event device in detached state. This > state not properly handled and causes a

[PATCH] clockevents/drivers/cs5535: Un-break driver with 'set-state' interface

2016-12-28 Thread David Gstir
Since migrating to the 'set-state' interface the cs5535 driver causes a crash after loading: Right after initialization, the IRQ handler (mfgpt_tick) is triggered with clock event device in detached state. This state not properly handled and causes a crash through NULL pointer dereference upon

[PATCH] clockevents/drivers/cs5535: Un-break driver with 'set-state' interface

2016-12-28 Thread David Gstir
Since migrating to the 'set-state' interface the cs5535 driver causes a crash after loading: Right after initialization, the IRQ handler (mfgpt_tick) is triggered with clock event device in detached state. This state not properly handled and causes a crash through NULL pointer dereference upon