GPIO regression in Linux next caused by syscon change
From: tony@atomide.com (Tony Lindgren)
Date: 2016-02-15 16:01:15
Also in:
linux-omap
From: tony@atomide.com (Tony Lindgren)
Date: 2016-02-15 16:01:15
Also in:
linux-omap
* Philipp Zabel [off-list ref] [160214 11:24]:
I've just replaced the of_iomap() call with an open coded version, calling of_address_to_resource() and ioremap() directly. That was needed so I can use the struct resource returned by of_address_to_resource() to set the syscon_config.max_register. I don't see where this could cause resource overlap. Does just setting syscon_config.max_register to zero again make the problem disappear?
Yes commenting out the syscon_config.max_register line in your patch makes things work again. So what does that tell us about the problem? Regards, Tony