Hi Daniel, On Mon, Aug 27, 2012 at 17:46:17, Daniel Mack wrote: > > Such a generic routine would help create a driver out of gpmc platform > > code, which would be peripheral agnostic and thus lead to DT finally. > > Input to generic timing calculation routine would be gpmc peripheral > > timings, output - translated timings that gpmc can understand. Later, > > to DT'ify, gpmc peripheral timings could be passed through DT. Input > > timings that has been used here are selected such that it represents > > those that are present in peripheral timing datasheets. > > What I don't understand yet about this new approach is where the gpmc > client code should live in. In order to probe the drivers via DT, each > driver would need to call the gpmc support functions itself, right? Is By gpmc client code, if you are referring to helper functions in mach-omap2/gpmc-*, if things go as per plan, with DT, they will go away and gpmc driver would handle those based on the information from DT. No change would be needed for client drivers like smc91x ethernet drivers, but NAND driver may need some change to live with DT as it is tightly coupled with GPMC. > the plan to obsolete helper functions like gpmc_nand_init() and move > that functionality to the drivers? Yes, plan is to obsolete the functions like gpmc_nand_init, those tasks would be handled by gpmc driver > > I applied these patches locally and would like to help get the NAND > controller on my AX33xx DT-driven board going. Let me know if I can do > anything here. Thanks for offering the help, will take liberty to ask you for help when required. BTW, do you have any OMAP family boards ? Regards Afzal -- 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
