linux-kernel - changing to threaded_handler in twl6030-irq.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 11 Aug 2011 21:19:37 +0900
From:	anish singh <anish198519851985@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	Rajendra Nayak <rnayak@...com>, Balaji T K <balajitk@...com>,
	Santosh Shilimkar <santosh.shilimkar@...com>,
	Samuel Ortiz <sameo@...ux.intel.com>
Subject: changing to threaded_handler in twl6030-irq.c

/*
 * handle_twl6030_int() is the desc->handle method for the twl6030 interrupt.
 * This is a chained interrupt, so there is no desc->action method for it.
 * Now we need to query the interrupt controller in the twl6030 to determine
 * which module is generating the interrupt request.  However, we can't do i2c
 * transactions in interrupt context, so we must defer that work to a kernel
 * thread.  All we do here is acknowledge and mask the interrupt and wakeup
 * the kernel thread.
 */
static irqreturn_t handle_twl6030_pih(int irq, void *devid)
{
        disable_irq_nosync(irq);
        complete(devid);
        return IRQ_HANDLED;
}

Does this still hold good when we have threaded_handler?Is it possible
to move to threaded handler if no, can anybody explain the reason?
Just to know more about threaded handler short comings if there is any.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/