* Roger Quadros <rogerq@xxxxxx> [140611 01:58]: > Some devices (e.g. TUSB6010, omap-onenand) need to reconfigure the GPMC > timings in order to operate with different peripheral clock frequencies. > Introduce omap_gpmc_retime() to allow them to do that. The driver > needs to pass the chips select number, GPMC settings and Device timings to > omap_gpmc_retime(). > > NOTE: Device tree and board code must still pass the most conservative > timings to GPMC so that the device can be probed by the respective driver. > e.g. Onenand must operate in asynchronous mode at bootup. The device driver > can then request for more optimal timings via omap_gpmc_retime(). Hmm but many of the devices are Linux generic like sms91x and 8250 so it's not nice to start stuffing omap bus specific data there. I wonder if we should just keep device specific gpmc-smc91x.c etc in drivers/memory? 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
