omap_hdq: fix usecount handling

hdq_usecount was set to zero after a successful read, so
omap_hdq_put could not properly free resources which leads
e.g. to increasing usecounts in lsmod output

Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
Acked-by: Evgeniy Polyakov <zbr@ioremap.net>
Reviewed-by: Vignesh R <vigneshr@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

diff --git a/drivers/w1/masters/omap_hdq.c b/drivers/w1/masters/omap_hdq.c
index 0e2f43bccf1ffba52d1a7fe60a089ea4da8e3b60..a2eec97d506496e71885130269ba0af6df05319d 100644 (file)
--- a/drivers/w1/masters/omap_hdq.c
+++ b/drivers/w1/masters/omap_hdq.c
@@ -618,7 +618,6 @@ static u8 omap_w1_read_byte(void *_hdq)
 
        hdq_disable_interrupt(hdq_data, OMAP_HDQ_CTRL_STATUS,
                              ~OMAP_HDQ_CTRL_STATUS_INTERRUPTMASK);
-       hdq_data->hdq_usecount = 0;
 
        /* Write followed by a read, release the module */
        if (hdq_data->init_trans) {