* Felipe Balbi <balbi@xxxxxx> [140728 14:19]: > OMAP INTC irqchip driver will be moved under > drivers/irqchip/ soon but we still have a dependency > with mach-omap2 when it comes to idle functions. > > In order to make it easy to share those function > prototypes with OMAP PM code, we introduce this new > header. > > Signed-off-by: Felipe Balbi <balbi@xxxxxx> > --- > arch/arm/mach-omap2/board-3430sdp.c | 1 + > arch/arm/mach-omap2/board-am3517crane.c | 1 + > arch/arm/mach-omap2/board-am3517evm.c | 1 + > arch/arm/mach-omap2/board-cm-t35.c | 1 + > arch/arm/mach-omap2/board-cm-t3517.c | 1 + > arch/arm/mach-omap2/board-devkit8000.c | 1 + > arch/arm/mach-omap2/board-ldp.c | 1 + > arch/arm/mach-omap2/board-omap3beagle.c | 1 + > arch/arm/mach-omap2/board-omap3logic.c | 1 + > arch/arm/mach-omap2/board-omap3pandora.c | 1 + > arch/arm/mach-omap2/board-omap3stalker.c | 1 + > arch/arm/mach-omap2/board-omap3touchbook.c | 1 + > arch/arm/mach-omap2/board-overo.c | 1 + > arch/arm/mach-omap2/board-rx51.c | 1 + > arch/arm/mach-omap2/board-ti8168evm.c | 1 + > arch/arm/mach-omap2/common.h | 9 --------- > arch/arm/mach-omap2/cpuidle34xx.c | 1 + > arch/arm/mach-omap2/irq.c | 1 + > arch/arm/mach-omap2/pm24xx.c | 1 + > arch/arm/mach-omap2/pm34xx.c | 1 + > include/linux/irqchip/irq-omap-intc.h | 32 ++++++++++++++++++++++++++++++ ... > +void omap2_init_irq(void); > +void omap3_init_irq(void); > +void ti81xx_init_irq(void); I think these will all go away with DT based booting? So it might be worth waiting for that rather than churn all these files, or.. > +int omap_irq_pending(void); > +void omap_intc_save_context(void); > +void omap_intc_restore_context(void); > +void omap3_intc_suspend(void); > +void omap3_intc_prepare_idle(void); > +void omap3_intc_resume_idle(void); ..how about we pass something like struct omap_intc_data as pdata and let the intc driver populate function pointers for these if runtime PM calls are not enough here? That way we could have just minimal pdata header file. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
