[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55C21CCD.6050101@ti.com>
Date: Wed, 5 Aug 2015 19:55:17 +0530
From: Kishon Vijay Abraham I <kishon@...com>
To: Roger Quadros <rogerq@...com>, <tony@...mide.com>,
<t-kristo@...com>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-usb@...r.kernel.org>,
<linux-omap@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>
CC: <balbi@...com>, <bcousson@...libre.com>, <linux@....linux.org.uk>,
<nsekhar@...com>
Subject: Re: [PATCH 10/10] ARM: dts: omap4: Use "syscon-otghs" instead of
"ctrl-module" in USB node
Hi Roger,
On Wednesday 05 August 2015 01:38 PM, Roger Quadros wrote:
> On 05/08/15 11:02, Roger Quadros wrote:
>> Kishon,
>>
>> On 04/08/15 18:30, Kishon Vijay Abraham I wrote:
>>> Add "syscon-otghs" property and remove the deprecated "ctrl-module"
>>> property from MUSB devicetree node.
>>>
>>> Since "omap_control_usbotg" devicetree node is no longer used, remove
>>> it.
>>>
>>> Signed-off-by: Kishon Vijay Abraham I <kishon@...com>
>>> ---
>>> arch/arm/boot/dts/omap4.dtsi | 8 +-------
>>> 1 file changed, 1 insertion(+), 7 deletions(-)
>>>
>>> diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
>>> index b27634d..2fb49a5 100644
>>> --- a/arch/arm/boot/dts/omap4.dtsi
>>> +++ b/arch/arm/boot/dts/omap4.dtsi
>>> @@ -854,12 +854,6 @@
>>> };
>>> };
>>>
>>> - omap_control_usbotg: control-phy@...0233c {
>>> - compatible = "ti,control-phy-otghs";
>>> - reg = <0x4a00233c 0x4>;
>>> - reg-names = "otghs_control";
>>> - };
>>> -
>>> usb_otg_hs: usb_otg_hs@...ab000 {
>>> compatible = "ti,omap4-musb";
>>> reg = <0x4a0ab000 0x7ff>;
>>> @@ -872,7 +866,7 @@
>>> multipoint = <1>;
>>> num-eps = <16>;
>>> ram-bits = <12>;
>>> - ctrl-module = <&omap_control_usbotg>;
>>> + syscon-otghs = <&scm_conf 0x33c>;
>>
>> All other properties were of the format "syscon-phy-foo".
>> Why use a different format here?
>>
>
> Ah, looks like we don't have a dedicated phy driver for this?
> We will need to add a PHY driver I guess then and handle this register
> in that driver rather than in the musb driver.
I was explaining in the other thread to Tony on why this shouldn't be done in a
PHY driver [1].
Thanks
Kishon
[1] -> https://lkml.org/lkml/2015/8/5/455
--
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