Hi Daniel, On Monday 29 October 2012 04:45 PM, Daniel Mack wrote:
On 29.10.2012 09:10, Afzal Mohammed wrote:
Also perhaps memory size (and offset if needed) to be mapped for peripherals can go with reg property of child.
Which detail are you referring to here? The only "size" property that is effective is the one of the generic GPMC block, and there it's in the "reg"-property.
I was referring to that of child, now in gpmc_nand_init(), gpmc_cs_request() is being done, later on if we want to make it generic and remove gpmc_nand_init(), additional information that would be required from DT at least is the memory size to be reserved in gpmc address space for the connected peripheral (assuming gpmc_cs_request() would be done by gpmc driver generically later) What I had in mind was example for external bus in [1], but I had not looked deep into this aspect yet. Regards Afzal [1] http://devicetree.org/Device_Tree_Usage#Memory_Mapped_Devices -- 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
