ti-st: use worker instead of calling st_int_write in wake up
authorMuhammad Hamza Farooq <mfarooq@visteon.com>
Fri, 11 Sep 2015 14:42:38 +0000 (16:42 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 21 Sep 2015 05:52:13 +0000 (22:52 -0700)
commitb05b7c7cc0324524dcda7fa7c2be1255290ee416
treeecaff7f9aebc82187b5613789b43c9c76d530420
parentf97ef759999485df485fe19a440d6af02d561140
ti-st: use worker instead of calling st_int_write in wake up

The wake up method is called with the port lock held. The st_int_write
method calls port->ops->write with tries to acquire the lock again,
causing CPU to wait infinitely. Right way to do is to write data to port
in worker thread.

Signed-off-by: Muhammad Hamza Farooq <mfarooq@visteon.com>
Signed-off-by: Jacob Siverskog <jacob@teenage.engineering>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/misc/ti-st/st_core.c
include/linux/ti_wilink_st.h