* Kishon Vijay Abraham I <kishon@xxxxxx> [151215 04:47]: > On Tuesday 15 December 2015 05:25 PM, Arnd Bergmann wrote: > >>> > >>> Can you explain here what the conversion is good for? Why do you > >>> prefer the syscon mapping over a high-level driver in this case? > >> > >> phy-omap-control driver was added when there was no proper > >> infrastructure for doing control module initializations. The > >> phy-omap-control driver is not an 'actual' PHY driver and it > >> was just a hack to do PHY related control module initializations. > >> phy-omap-control is also getting unmanageable with the number of > >> platforms each having number of modules (like USB, SATA, PCIe), > >> using the same driver for control module initializations. > >> > >> Now with SYSCON framework being added to the kernel, phy-omap-control > >> shouldn't be needed and it also provides a uniform API across all the > >> modules to program the control module. > > > > Ok, so the "phy-control" devices were really just a few registers of > > a system controller device that does a lot of other things as well, right? > > right. > > > > Can you put your description above into the cover-letter for the series, > > and the merge commit? Just to confirm.. Seems like this series keeps USB working and the dts changes can be done later after the driver changes have been merged? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
