On Wed, 2017-05-24 at 16:29 +0200, Andrew Lunn wrote: > On Wed, May 24, 2017 at 05:00:04PM +0300, Andy Shevchenko wrote: > > On Wed, 2017-05-24 at 15:41 +0200, Andrew Lunn wrote: > > > > I'm wondering where exactly first resource acquiring is > > > > happening. > > > > > > drivers/phy/phy-mvebu-sata.c > > > > > > > In which tree? I have nothing like this in linux-next. > > git log drivers/phy/phy-mvebu-sata.c > > It has been there since Tue Dec 17 21:21:50 2013. > > > I'm on the side that revert just hides the real issue back. > > What issue? You are allowed to have overlapping memory resources. Exactly, and then the question why did you do a revert? AFAIU the problem is that platform core tries to reserve the resource and you can't do it twice for overlapping region (see insert_resource() call implementation). Since it's allowed and we have more devices which requires that (basically that ones that have phy embedded in common address space) we might reconsider the policy used in platform core. -- Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> Intel Finland Oy -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
