lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFp+6iFr3y7+362xZ1KMkfYjJdoa5F0sWfQ+6=S11ZPwVCTDZQ@mail.gmail.com>
Date:	Wed, 19 Dec 2012 11:19:32 +0530
From:	Vivek Gautam <gautamvivek1987@...il.com>
To:	linux-samsung-soc@...r.kernel.org
Cc:	dianders@...omium.org,
	Sylwester Nawrocki <sylvester.nawrocki@...il.com>,
	linux-usb@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org,
	linux-kernel@...r.kernel.org, kgene.kim@...sung.com, balbi@...com,
	thomas.abraham@...aro.org, rob.herring@...xeda.com,
	grant.likely@...retlab.ca, p.paneri@...sung.com,
	Vivek Gautam <gautam.vivek@...sung.com>
Subject: 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.nawrocki@...il.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 Gautam<gautam.vivek@...sung.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@...30000 {
>>                 compatible = "samsung,exynos5250-usbphy";
>> -               reg =<0x12130000 0x100>;
>> +               reg =<0x12130000 0x100>,
>> +               <0x12100000 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_h0&phy_h1&phy_h2>;
>>                 samsung,enable-mask =<1>;
>>         };
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc"
> in
> the body of a message to majordomo@...r.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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ