Hi,
On Thu, Feb 10, 2011 at 12:21:17PM +0200, Felipe Balbi wrote:
> here are 4 very quick patches to grab IRQ
> via struct resource. Now all these changes
> need to be ported to Tahvo. I'm not sure
> I'll have any time to look at that for a
> while, though.
I have put together a few more patches which are now available at [1],
here's the diffstat against tony/master:
arch/arm/mach-omap1/board-nokia770.c | 1 +
arch/arm/mach-omap2/board-n8x0.c | 1 +
arch/arm/plat-omap/include/plat/cbus.h | 4 +
drivers/cbus/retu-headset.c | 46 +++++---
drivers/cbus/retu-pwrbutton.c | 6 +-
drivers/cbus/retu-rtc.c | 57 +++++-----
drivers/cbus/retu-wdt.c | 15 +--
drivers/cbus/retu.c | 202 ++++++++++++++++++++-----------
drivers/cbus/retu.h | 10 +-
9 files changed, 206 insertions(+), 136 deletions(-)
and here's the new shortlog:
Felipe Balbi (19):
cbus: retu: pass IRQ via struct resource
cbus: retu: headset: grab IRQ via struct resource
cbus: retu: pwrbutton: grab IRQ via struct resource
cbus: retu: rtc: grab IRQ via struct resource
cbus: retu: drop retu_get_status
cbus: retu: replace BUG_ON with WARN
cbus: retu: drop the unnecessary spinlock_t
cbus: retu: drop unused PFX macro
arm: omap: cbus: add IDs for Retu and Tahvo
arm: omap: pass Retu ID via platform_data
cbus: retu: use the devid from platform_data
cbus: retu: introduce internal read/write functions
cbus: retu: search and replace
cbus: retu: pwrbutton: save device pointer on our structure
cbus: retu: pass the child device pointer to all retu functions
cbus: retu: headset: don't save pdev pointer
cbus: retu: replace EXPORT_SYMBOL with EXPORT_SYMBOL_GPL
cbus: retu: tabify retu initialization
cbus: retu: set pm_power_off to NULL when removing retu
Want me to re-send all patches or you can pull from my cbus branch to
test ?
Any taker for fixing tahvo ? All you have to do is port the changes done
in retu to tahvo. Tahvo is a lot simpler than retu though.
--
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
