Thread (5 messages) flat view 5 messages, 2 authors, 2012-05-24

Re: Reg. kernel crash while using pixcir touchscreen driver

From: Sachin Kamat <hidden>
Date: 2012-05-24 10:05:53

On 24/05/2012, Dmitry Torokhov [off-list ref] wrote:
On Thu, May 24, 2012 at 01:41:27PM +0530, Sachin Kamat wrote:
quoted
Hi Dmitry,

Thank you for your reply.


On 24/05/2012, Dmitry Torokhov [off-list ref] wrote:
quoted
Hi Sachin,

On Thu, May 24, 2012 at 11:20:01AM +0530, Sachin Kamat wrote:
quoted
Hi,

I encountered a kernel crash while integrating Pixcir touchscreen
driver with one of our hardware. The log is attached at the end of the
mail (inline).

The following ISR code:

while (!tsdata->exiting) {
        pixcir_ts_poscheck(tsdata);

        if (tsdata->chip->attb_read_val())
              break;

        msleep(20);
}

seems to run until the if condition is false. However, when it exits
the loop (when the condition becomes true), it crashes saying "exiting
task "irq/438-pixcir_" (1011) is an active IRQ thread".
It actually crashes earlier, in pixcir_ts_isr() itself. The message is
coming from do_exit() when ISR thread dies. Did you porvide
attb_read_val implementation?
Yes, i did provide the implementation for it.
In fact even a simplest implementation where I return a positive
integer (for testing) results in the above crash.
Hmm, this is wierd... are you sure you do not discard platform data
after binding to the touchscreen?
Yes, you are right. The platform data was getting freed after the binding.
It now works fine. Thanks for your help.
--
Dmitry

-- 
With warm regards,
Sachin
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help