Re: [PATCH 2/2] ARM: Exynos5250: Enabling USB 3.0 phy for samsung-usbphy driver
CC: Doug Anderson. On Wed, Dec 19, 2012 at 5:02 AM, Sylwester Nawrocki wrote: > On 12/18/2012 04:39 PM, Vivek Gautam wrote: >> >> Adding base address information required for enabling >> USB 3.0 DRD phy on exynos5250 SOC. >> >> Signed-off-by: Vivek Gautam >> --- >> arch/arm/boot/dts/exynos5250.dtsi |3 ++- >> 1 files changed, 2 insertions(+), 1 deletions(-) >> >> diff --git a/arch/arm/boot/dts/exynos5250.dtsi >> b/arch/arm/boot/dts/exynos5250.dtsi >> index bbdb2c2..07b7477 100644 >> --- a/arch/arm/boot/dts/exynos5250.dtsi >> +++ b/arch/arm/boot/dts/exynos5250.dtsi >> @@ -316,7 +316,8 @@ >> >> usbphy@1213 { >> compatible = "samsung,exynos5250-usbphy"; >> - reg =<0x1213 0x100>; >> + reg =<0x1213 0x100>, >> + <0x1210 0x100>; > > > Doesn't this second memory region mean distinct PHY controller device ? > Why separate usbphy node can't/shouldn't be created for it ? > >> samsung,usb-phyhandle =<_h0_h1_h2>; >> samsung,enable-mask =<1>; >> }; > > -- > To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" > in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Thanks & Regards Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 2/2] ARM: Exynos5250: Enabling USB 3.0 phy for samsung-usbphy driver
On 12/18/2012 04:39 PM, Vivek Gautam wrote: Adding base address information required for enabling USB 3.0 DRD phy on exynos5250 SOC. Signed-off-by: Vivek Gautam --- arch/arm/boot/dts/exynos5250.dtsi |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/arch/arm/boot/dts/exynos5250.dtsi b/arch/arm/boot/dts/exynos5250.dtsi index bbdb2c2..07b7477 100644 --- a/arch/arm/boot/dts/exynos5250.dtsi +++ b/arch/arm/boot/dts/exynos5250.dtsi @@ -316,7 +316,8 @@ usbphy@1213 { compatible = "samsung,exynos5250-usbphy"; - reg =<0x1213 0x100>; + reg =<0x1213 0x100>, + <0x1210 0x100>; Doesn't this second memory region mean distinct PHY controller device ? Why separate usbphy node can't/shouldn't be created for it ? samsung,usb-phyhandle =<_h0_h1_h2>; samsung,enable-mask =<1>; }; -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH 2/2] ARM: Exynos5250: Enabling USB 3.0 phy for samsung-usbphy driver
Adding base address information required for enabling USB 3.0 DRD phy on exynos5250 SOC. Signed-off-by: Vivek Gautam --- arch/arm/boot/dts/exynos5250.dtsi |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/arch/arm/boot/dts/exynos5250.dtsi b/arch/arm/boot/dts/exynos5250.dtsi index bbdb2c2..07b7477 100644 --- a/arch/arm/boot/dts/exynos5250.dtsi +++ b/arch/arm/boot/dts/exynos5250.dtsi @@ -316,7 +316,8 @@ usbphy@1213 { compatible = "samsung,exynos5250-usbphy"; - reg = <0x1213 0x100>; + reg = <0x1213 0x100>, + <0x1210 0x100>; samsung,usb-phyhandle = <_h0 _h1 _h2>; samsung,enable-mask = <1>; }; -- 1.7.6.5 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH 2/2] ARM: Exynos5250: Enabling USB 3.0 phy for samsung-usbphy driver
Adding base address information required for enabling USB 3.0 DRD phy on exynos5250 SOC. Signed-off-by: Vivek Gautam gautam.vi...@samsung.com --- arch/arm/boot/dts/exynos5250.dtsi |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/arch/arm/boot/dts/exynos5250.dtsi b/arch/arm/boot/dts/exynos5250.dtsi index bbdb2c2..07b7477 100644 --- a/arch/arm/boot/dts/exynos5250.dtsi +++ b/arch/arm/boot/dts/exynos5250.dtsi @@ -316,7 +316,8 @@ usbphy@1213 { compatible = samsung,exynos5250-usbphy; - reg = 0x1213 0x100; + reg = 0x1213 0x100, + 0x1210 0x100; samsung,usb-phyhandle = phy_h0 phy_h1 phy_h2; samsung,enable-mask = 1; }; -- 1.7.6.5 -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 2/2] ARM: Exynos5250: Enabling USB 3.0 phy for samsung-usbphy driver
On 12/18/2012 04:39 PM, Vivek Gautam wrote: Adding base address information required for enabling USB 3.0 DRD phy on exynos5250 SOC. Signed-off-by: Vivek Gautamgautam.vi...@samsung.com --- arch/arm/boot/dts/exynos5250.dtsi |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/arch/arm/boot/dts/exynos5250.dtsi b/arch/arm/boot/dts/exynos5250.dtsi index bbdb2c2..07b7477 100644 --- a/arch/arm/boot/dts/exynos5250.dtsi +++ b/arch/arm/boot/dts/exynos5250.dtsi @@ -316,7 +316,8 @@ usbphy@1213 { compatible = samsung,exynos5250-usbphy; - reg =0x1213 0x100; + reg =0x1213 0x100, + 0x1210 0x100; Doesn't this second memory region mean distinct PHY controller device ? Why separate usbphy node can't/shouldn't be created for it ? samsung,usb-phyhandle =phy_h0phy_h1phy_h2; samsung,enable-mask =1; }; -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 2/2] ARM: Exynos5250: Enabling USB 3.0 phy for samsung-usbphy driver
CC: Doug Anderson. On Wed, Dec 19, 2012 at 5:02 AM, Sylwester Nawrocki sylvester.nawro...@gmail.com wrote: On 12/18/2012 04:39 PM, Vivek Gautam wrote: Adding base address information required for enabling USB 3.0 DRD phy on exynos5250 SOC. Signed-off-by: Vivek Gautamgautam.vi...@samsung.com --- arch/arm/boot/dts/exynos5250.dtsi |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/arch/arm/boot/dts/exynos5250.dtsi b/arch/arm/boot/dts/exynos5250.dtsi index bbdb2c2..07b7477 100644 --- a/arch/arm/boot/dts/exynos5250.dtsi +++ b/arch/arm/boot/dts/exynos5250.dtsi @@ -316,7 +316,8 @@ usbphy@1213 { compatible = samsung,exynos5250-usbphy; - reg =0x1213 0x100; + reg =0x1213 0x100, + 0x1210 0x100; Doesn't this second memory region mean distinct PHY controller device ? Why separate usbphy node can't/shouldn't be created for it ? samsung,usb-phyhandle =phy_h0phy_h1phy_h2; samsung,enable-mask =1; }; -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Thanks Regards Vivek -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/