On 12/31/2016 12:56 AM, Krzysztof Kozlowski wrote: > On Wed, Dec 28, 2016 at 07:34:50PM +0900, Jaehoon Chung wrote: >> This patch is for using PHY generic framework. >> When Exynos5440 had upstreamed, there was no PHY subsytem. >> Now the using PHY framework is mandantory. >> In future, Exynos variant should be supported in pci-exynos.c >> >> Theses pathces based on the below patches >> > > Aren't you breaking DTB ABI here? If yes, then I don't mind but please > put it in the commit message. Also order the patches in a way > preserving bisectability. Will resend the patch v2. Best Regards, Jaehoon Chung > > Best regards, > Krzysztof > >> - Jaehoon's patches >> http://patchwork.ozlabs.org/patch/706998/ >> http://patchwork.ozlabs.org/patch/706997/ >> http://patchwork.ozlabs.org/patch/706995/ >> http://patchwork.ozlabs.org/patch/706994/ >> >> - Srinivas's patch >> http://patchwork.ozlabs.org/patch/703530/ >> >> - Pankaj's patch >> http://patchwork.ozlabs.org/patch/708414/ >> >> Jaehoon Chung (4): >> phy: exynos-pcie: Add support for Exynos PCIe phy >> Documetation: samsung-phy: add the exynos-pcie-phy binding >> Documetation: binding: modify the exynos5440 pcie binding >> ARM: dts: exynos5440: support the phy-pcie node for pcie >> >> .../bindings/pci/samsung,exynos5440-pcie.txt | 29 ++- >> .../devicetree/bindings/phy/samsung-phy.txt | 23 ++ >> arch/arm/boot/dts/exynos5440.dtsi | 44 +++- >> drivers/pci/host/pci-exynos.c | 198 ++------------ >> drivers/phy/Kconfig | 9 + >> drivers/phy/Makefile | 1 + >> drivers/phy/phy-exynos-pcie.c | 289 +++++++++++++++++++++ >> 7 files changed, 395 insertions(+), 198 deletions(-) >> create mode 100644 drivers/phy/phy-exynos-pcie.c >> >> -- >> 2.10.2 >> > -- > To unsubscribe from this list: send the line "unsubscribe linux-pci" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > -- 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