Hi Kishon, > > This patchset is based on the two core patches you sent to the > > list which facilitate creating PHYs residing on multi-channel > > controllers. The changes since the last submission centre > > around dynamic PHY creation based solely on what is provided via > > Device Tree, as requested. The other review comments have also > > been addressed in this set. > > Merged the first four patches of this series. (merged v3+1 for 1st patch). > I'm not sure who would be merging the dt patch (5/5). But for now I've merged > 2/5 in linux-phy tree since the phy patch seems to be dependent on it. > So the dt patch can be merged only after -rc1. However if whoever merges > dt wants to get it merged during the merge window, I can prepare a common > branch which both of us can merge to. Either ways, dt Maintainer should > let me know.
Thanks for applying. It would be really helpful if you could put just patch 2/5 onto an immutable branch and provide a tag e that Maxime could pull from. Kind regards, Lee > > .../devicetree/bindings/phy/phy-miphy365x.txt | 76 +++ > > arch/arm/boot/dts/stih416-b2020-revE.dts | 10 + > > arch/arm/boot/dts/stih416-b2020.dts | 12 + > > arch/arm/boot/dts/stih416.dtsi | 22 + > > drivers/phy/Kconfig | 10 + > > drivers/phy/Makefile | 1 + > > drivers/phy/phy-miphy365x.c | 636 > > +++++++++++++++++++++ > > include/dt-bindings/phy/phy-miphy365x.h | 14 + > > 8 files changed, 781 insertions(+) -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
