[PATCH v2] ARM: OMAP2/3: hwmod data: add gpmc

Mohammed, Afzal afzal at ti.com
Tue Jun 12 06:23:48 EDT 2012


Hi Paul,

On Mon, Jun 11, 2012 at 18:45:03, Mohammed, Afzal wrote:
> Add gpmc hwmod and associated interconnect data
> 
> HWMOD_INIT_NO_RESET can be removed once kernel is updated to
> configure GPMC for all peripherals. Currently many depend on
> bootloader, this facility will be removed.
> (feature-removal-schedule.txt will get updated in upcoming
> gpmc series).
> 
> No reset is also required for smooth migration to gpmc driver;
> approach being taken is to hold old interface until boards are
> converted to use driver interface one-by-one. Till that time,
> this flag is a must as old interface rely on bootloader
> 
> Signed-off-by: Afzal Mohammed <afzal at ti.com>
> ---
> 
> v2: rebased to 3.5-rc1

Please let me know your comments on this. I am proceeding as you
have suggested; beagle board, omap3evm had been made to configure
in Kernel at runtime [1] and provision has been given in gpmc
driver to cry loud if no configuration in Kernel [2]

Updating feature-removal-schedule.txt will be done as part of
another series (yet to be posted, that series depends on gpmc
driver conversion series [3], needs to know Tony's comments on
driver series first and if fine, it will be posted). Right now
it won't make sense to post a patch on feature-removal as first
all boards that depend on bootloader has to modified to make use
of driver interface. So patch on feature-removal-schedule.txt
will be posted along with migration of remaining boards to use
driver interface.

And this patch is necessary for gpmc driver conversion [3] to proceed.

Regards
Afzal

[1] http://www.mail-archive.com/linux-omap@vger.kernel.org/msg69917.html
[2] http://www.mail-archive.com/linux-omap@vger.kernel.org/msg69906.html
[3] http://www.mail-archive.com/linux-omap@vger.kernel.org/msg69897.html




More information about the linux-arm-kernel mailing list