[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201001252306.55625.david-b@pacbell.net>
Date: Mon, 25 Jan 2010 23:06:55 -0800
From: David Brownell <david-b@...bell.net>
To: Felipe Balbi <felipe.balbi@...ia.com>
Cc: linux-kernel@...r.kernel.org,
Linux OMAP Mailing List <linux-omap@...r.kernel.org>,
Tony Lindgren <tony@...mide.com>,
Aaro Koskinen <aaro.koskinen@...ia.com>,
Linux USB Mailing List <linux-usb@...r.kernel.org>,
Anton Vorontsov <avorontsov@...mvista.com>,
Grazvydas Ignotas <notasas@...il.com>,
Madhusudhan Chikkature <madhu.cr@...com>,
"Greg Kroah-Hartman" <gregkh@...e.de>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Samuel Ortiz <sameo@...nedhand.com>
Subject: Re: [RFC/PATCH 0/4] twl4030 threaded_irq support
On Monday 14 December 2009, Felipe Balbi wrote:
> move twl4030 children to threaded irq.
>
> Felipe Balbi (4):
> input: keyboard: twl4030: move to request_threaded_irq
> input: misc: twl4030: move to request_threaded_irq
> rtc: twl4030: move to request_threaded_irq
> usb: otg: twl4030: move to request_threaded_irq
But nothing in drivers/mfd ... the entry to the whole stack?
Did the threaded IRQ stuff ever get set up so that the top
level IRQ thread didn't have to hand off to another thread
each time? (That's how the current stuff works. One thread
calling out to each handler.)
If so, I'd like to see that be used here, rather than needlessly
spend all those pages on mostly-unused stacks.
>
> drivers/input/keyboard/twl4030_keypad.c | 11 ++---------
> drivers/input/misc/twl4030-pwrbutton.c | 12 +-----------
> drivers/rtc/rtc-twl4030.c | 10 +---------
> drivers/usb/otg/twl4030-usb.c | 10 +---------
> 4 files changed, 5 insertions(+), 38 deletions(-)
>
>
--
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/
Powered by blists - more mailing lists