Tony Lindgren wrote on Thursday, February 10, 2011 7:18 AM: > * Tony Lindgren <tony@xxxxxxxxxxx> [110209 17:45]: >> >> We should just have separate struct map_desc omapti816x_io_desc[] then. >> Maybe have a common struct map_desc omap3_io_desc[] and then separate >> omap3xxx_io_desc and omapti816x_io_desc? > > Oh and this will work just fine for map_io without having cpu_is_omap > macros working yet because we call set_globals from the board > file with > the processor class data. > > Tony So probably I need to create another function (ti816x_map_common_io()) to map just the L4 slow region and call it from board file (after set globals) as distinguishing between OMAP3xxx and TI816X is not possible at that time inside omap34xx_map_common_io() as they both have same class. Does this approach look ok? Thanks. Hemant-- 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
