[PATCHv9 00/18] omap PRCM chain handler
Hello, Following set contains the version 9 of this work. This patch set contains a number of patches tagged as 'TEMP', they are only meant for testing purposes and to provide proof of concept. Most of the 'TEMP' patches are related to UART runtime handling and they will be replaced by work done by Govindraj Raja. As this is a new set sent to linux-arm and linux-kernel lists, the basic concept being tackled with this set is to provide a mechanism for multiple drivers to register for PRCM interrupts. PRCM interrupt contains a SoC depenpend number of events, which of most interesting ones are wakeup and IO chain. These are the only supported events in the driver currently, but it is possible to add more by tweaking omap3xxx-prm.c and omap4xxx-prm.c files. This driver should also be expanded later to contain much of the code currently included within the OMAP voltage framework, which resides under arch/arm/mach-omap2/voltage*,vc*,vp*. Changes compared to previous version of this set: - PRM driver is now moved under /drivers/mfd - PRM driver split into three parts now, common, omap3 and omap4 - version of the driver to init is detected based on PRM version (patch 11) - cleaned up the initialization logic a bit (platform device is built separately, provide two different drivers) - renamed PRM hwmods as prm3xxx and prm4xxx These patches have been tested on omap3 beagle and omap4 blaze platforms. Tested features include suspend and dynamic idle. Tested trees are available at: g...@gitorious.org:~kristo/omap-pm/omap-pm-work.git branches: omap3_prcm_chain and omap4_prcm_chain -Tero Texas Instruments Oy, Tekniikantie 12, 02150 Espoo. Y-tunnus: 0115040-6. Kotipaikka: Helsinki -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCHv9 00/18] omap PRCM chain handler
On Fri, 23 Sep 2011 15:46:08 +0300, Tero Kristo said: Following set contains the version 9 of this work. This patch set contains a number of patches tagged as 'TEMP', they are only meant for testing purposes and to provide proof of concept. Most of the 'TEMP' patches are related to UART runtime handling and they will be replaced by work done by Govindraj Raja. What do we do with these TEMP patches if the UART patches don't make the same merge window, or have other issues? I'm always leery of will be replaced code, because I've seen too many times when it *didn't* get replaced. (I really don't care what the 'Plan B' is, as long as we have one...) pgpprmOWHQJUp.pgp Description: PGP signature
Re: [PATCHv9 00/18] omap PRCM chain handler
Hi Valdis.Kletnieks, On Sat, Sep 24, 2011 at 3:53 AM, valdis.kletni...@vt.edu wrote: On Fri, 23 Sep 2011 15:46:08 +0300, Tero Kristo said: Following set contains the version 9 of this work. This patch set contains a number of patches tagged as 'TEMP', they are only meant for testing purposes and to provide proof of concept. Most of the 'TEMP' patches are related to UART runtime handling and they will be replaced by work done by Govindraj Raja. What do we do with these TEMP patches if the UART patches don't make the same merge window, or have other issues? I'm always leery of will be replaced code, because I've seen too many times when it *didn't* get replaced. (I really don't care what the 'Plan B' is, as long as we have one...) UART Runtime patches are already posted for review and it's also targeted for next merge window. Our intention is to push both the features together for next merge window. Regards Vishwa ___ linux-arm-kernel mailing list linux-arm-ker...@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCHv9 00/18] omap PRCM chain handler
On Sat, 24 Sep 2011 10:54:29 +0530, Sripathy, Vishwanath said: UART Runtime patches are already posted for review and it's also targeted for next merge window. Our intention is to push both the features together for next merge window. Oh, OK. That should work then. Thanks for the clarification... pgpy6RReAWKiK.pgp Description: PGP signature
