linux-kernel - Re: [patch 2/2] genirq: Provide irq_wake

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 for Android: free password hash cracker in your pocket

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

Date:	Sat, 15 Feb 2014 10:50:28 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Russell King <linux@....linux.org.uk>,
	Chris Ball <chris@...ntf.net>, linux-mmc@...r.kernel.org,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [patch 2/2] genirq: Provide irq_wake_thread()

On Sat, Feb 15, 2014 at 12:55:19AM -0000, Thomas Gleixner wrote:
> In course of the sdhci/sdio discussion with Russell about killing the
> sdio kthread hackery we discovered the need to be able to wake an
> interrupt thread from software.
> 
> The rationale for this is, that sdio hardware can lack proper
> interrupt support for certain features. So the driver needs to poll
> the status registers, but at the same time it needs to be woken up by
> an hardware interrupt.
> 
> To be able to get rid of the home brewn kthread construct of sdio we
> need a way to wake an irq thread independent of an actual hardware
> interrupt.
> 
> Provide an irq_wake_thread() function which wakes up the thread which
> is associated to a given dev_id. This allows sdio to invoke the irq
> thread from the hardware irq handler via the IRQ_WAKE_THREAD return
> value and provides a possibility to wake it via a timer for the
> polling scenarios. That allows to simplify the sdio logic
> significantly.
> 
> Signed-off-by: Thomas Gleixner <tglx@...utronix.de>

Acked-by: Peter Zijlstra <peterz@...radead.org>
--
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/