Hi, On Thu, 14 Feb 2013, Tony Lindgren wrote: > The other option could be to allow custom ioremap function pointers > based on address range in __arm_ioremap_pfn_caller() the same way as > the SoC specific static mappings are allowed. That would require adding > a function pointer to struct map_desc. > > Maybe that would do the trick? That sounds fine to me too. To me it makes sense to eventually handle the I/O mappings automatically from data in the DT -- hence the association with a bus device, which should be present in DT data. - Paul -- 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
