Re: Guidelines to move mach-omap2/gpmc to drivers/memory-controller

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 02/15/2013 01:53 PM, Paul Walmsley wrote:
> Hi,
> 
> On Fri, 15 Feb 2013, Ezequiel Garcia wrote:
> 
>> I imagine one of the biggest issues is GPMC's dependency on
>> hwmod code. Can anyone shed some light on how to handle this?
> 
> What dependency is this?  I'm not aware of any GPMC dependency to hwmod; 
> there shouldn't be any.

If Ezequiel is referring to the code in omap_gpmc_init() that is looking
up the hwmod struct for gpmc, then this not a dependency. This function
should remain in mach-omap2/gpmc.c and not be moved into drivers/.
Eventually once we have migrated to DT, this function will be removed
altogether.

Cheers
Jon
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux