This patchset is for using PHY generic framework. Current pci-exyons doesn't use the phy framework since there haven't been on PHY subsystem when Exynos5440 had been upstremed. The not using PHY framework make the difficult to upstream the other Exynos SoCs. Before upstreaming the other Exynos SoCs, it's goal what make to use the PHY framework. This patchset has the below modifications: 1) Introduces the phy-pcie-pcie 2) Handles Phy controller from PHY framework for pci-exynos 3) Modifies the dt-binding of pci-exynos - The using the getting configuration space address from ranges is old. - Deprecated the old way. 4) Maintains the backward compatibility NOTE: These patches based on below 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/ http://patchwork.ozlabs.org/patch/703530/ - This patch should be conflicted. so fixes the manually. http://patchwork.ozlabs.org/patch/708414/ Changelog on V2: - Keep current codes for backward compatibility - Fixes some typos - Split the patches for removing the dependency - Removes the unnecessary codes - Change the patch's sequence - Based on latest PCI git repository.(next branch) Jaehoon Chung (5): Documetation: samsung-phy: add the exynos-pcie-phy binding phy: phy-exynos-pcie: Add support for Exynos PCIe phy Documetation: binding: modify the exynos5440 pcie binding PCI: exynos: support the using PHY generic framework ARM: dts: exynos5440: support the phy-pcie node for pcie .../bindings/pci/samsung,exynos5440-pcie.txt | 29 +++ .../devicetree/bindings/phy/samsung-phy.txt | 17 ++ arch/arm/boot/dts/exynos5440.dtsi | 34 ++- drivers/pci/host/pci-exynos.c | 61 ++++- drivers/phy/Kconfig | 9 + drivers/phy/Makefile | 1 + drivers/phy/phy-exynos-pcie.c | 280 +++++++++++++++++++++ 7 files changed, 408 insertions(+), 23 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
