On Tue, Nov 06, 2012 at 14:59:45, Hiremath, Vaibhav wrote: [...] > > > > Ok I checked this one. The change I made was indirectly fixing another > > issue with the AM33xx hwmod data. am33xx_cpgmac0_addr_space[] has two > > entries and the SYSC register is part of the second entry. The function > > _find_mpu_rt_addr_space in omap_hwmod.c looks for the first entry with > > the flag ADDR_TYPE_RT flag. The change I made indirectly made the second > > entry in am33xx_cpgmac0_addr_space[] become the first memory space with > > the ADDR_TYPE_RT flag. Due to this the hwmod code wrote to the correct > > SYSC address of CPGMAC0 and the IP went to standby during bootup. > > After changing the order of the entries in am33xx_cpgmac0_addr_space[] > > things work fine. > > > > Good catch. > > Just a side note on this, driver expects the addresses in this order > only, first SS and then WR. > Sorry I didn't understand your comment. For HWMOD code to work as expected, we need to change the order. Are you saying that I should not be doing this because the driver will get affected? Regards, Vaibhav -- 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
