linux-kernel - Re: [PATCH 2/5 v11] arm: omap: usb: ehci and ohci hwmod structures for omap3

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 27 Sep 2011 16:24:56 +0300
From:	Felipe Balbi <balbi@...com>
To:	"Munegowda, Keshava" <keshava_mgowda@...com>
Cc:	t-kristo@...com, Paul Walmsley <paul@...an.com>,
	"Cousson, Benoit" <b-cousson@...com>,
	"Basak, Partha" <p-basak2@...com>, "Balbi, Felipe" <balbi@...com>,
	parthab@...ia.ti.com, linux-usb@...r.kernel.org,
	linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
	"Gadiyar, Anand" <gadiyar@...com>, sameo@...ux.intel.com,
	tony@...mide.com, "Hilman, Kevin" <khilman@...com>,
	johnstul@...ibm.com, "Sripathy, Vishwanath" <vishwanath.bs@...com>
Subject: Re: [PATCH 2/5 v11] arm: omap: usb: ehci and ohci hwmod structures
 for omap3

Hi,

On Tue, Sep 27, 2011 at 06:48:35PM +0530, Munegowda, Keshava wrote:
> > So, you would need a mechanism to do something like this:
> >
> > pad a or b wakeup detected -> irq0
> > pad c or d wakeup detected -> irq1?
> 
> yes, if get something like this , its perfect.

can't you have different IRQs for each pad ? I mean, allocate one
irq_desc for each pad and let drivers request a pad/pin as an IRQ
source. Then, when you detect a pad wakeup, you can:

unsigned	pad_irq = pad_number - pad->irq_base;

handle_nested_thread(pad_irq);

this will make use of threaded IRQ handlers even. Could it be something
like that ?

-- 
balbi

Download attachment "signature.asc" of type "application/pgp-signature" (491 bytes)