On 05/10/2014 06:00 AM, Vivek Gautam wrote: > Using devm_ioremap_resource() API should actually be preferred over > devm_ioremap(), since the former request the mem region first and then > gives back the ioremap'ed memory pointer. > devm_ioremap_resource() calls request_mem_region(), therby preventing > other drivers to make any overlapping call to the same region. This patch on its own works OK on Tegra. However, if a similar patch were to be applied to the Tegra PHY driver, then I expect that would break USB on Tegra. The reason is that the Tegra USB controller and PHY registers are interleaved a bit randomly within the same address range, and rather than call out which individual addresses are relevant to the controller and the PHY, the DT for both devices just specifies the same whole range, and the drivers only touch the appropriate registers within the range. Perhaps we should have described that as an MFD rather than separate DT nodes and devices, but that's not what we ended up with. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
