All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@ti.com>
To: Kishon Vijay Abraham I <kishon@ti.com>,
	tony@atomide.com, t-kristo@ti.com, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-omap@vger.kernel.org
Cc: balbi@ti.com, nsekhar@ti.com
Subject: Re: [PATCH 6/7] phy: omap-usb2: Add a new compatible string for USB2 PHY2
Date: Fri, 7 Aug 2015 11:27:20 +0300	[thread overview]
Message-ID: <55C46BE8.9060804@ti.com> (raw)
In-Reply-To: <55C21B35.7010901@ti.com>

On 05/08/15 17:18, Kishon Vijay Abraham I wrote:
> Hi Roger,
> 
> On Wednesday 05 August 2015 01:55 PM, Roger Quadros wrote:
>> On 05/08/15 11:23, Roger Quadros wrote:
>>>
>>> On 04/08/15 18:20, Kishon Vijay Abraham I wrote:
>>>> The USB2 PHY2 has a different register map compared to USB2 PHY1
>>>> to power on/off the PHY. In order to handle it, add a new
>>>> "compatible" string.
>>>>
>>>> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
>>>> ---
>>>>  Documentation/devicetree/bindings/phy/ti-phy.txt |    2 ++
>>>>  drivers/phy/phy-omap-usb2.c                      |    9 +++++++++
>>>>  2 files changed, 11 insertions(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/phy/ti-phy.txt b/Documentation/devicetree/bindings/phy/ti-phy.txt
>>>> index 49e5b0c..a061077 100644
>>>> --- a/Documentation/devicetree/bindings/phy/ti-phy.txt
>>>> +++ b/Documentation/devicetree/bindings/phy/ti-phy.txt
>>>> @@ -31,6 +31,8 @@ OMAP USB2 PHY
>>>>  
>>>>  Required properties:
>>>>   - compatible: Should be "ti,omap-usb2"
>>>> +	       Should be "ti,dra7x-usb2-phy2" for the 2nd instance of USB2 PHY
>>>> +	       in DRA7x
>>>>   - reg : Address and length of the register set for the device.
>>>>   - #phy-cells: determine the number of cells that should be given in the
>>>>     phandle while referencing this phy.
>>>> diff --git a/drivers/phy/phy-omap-usb2.c b/drivers/phy/phy-omap-usb2.c
>>>> index b5c266a..2f7220f 100644
>>>> --- a/drivers/phy/phy-omap-usb2.c
>>>> +++ b/drivers/phy/phy-omap-usb2.c
>>>> @@ -159,6 +159,11 @@ static const struct usb_phy_data dra7x_usb2_data = {
>>>>  	.flags = OMAP_USB2_CALIBRATE_FALSE_DISCONNECT,
>>>>  };
>>>>  
>>>> +static const struct usb_phy_data dra7x_usb2_phy2_data = {
>>>> +	.label = "dra7x_usb2_phy2",
>>>> +	.flags = OMAP_USB2_CALIBRATE_FALSE_DISCONNECT,
>>>> +};
>>>> +
>>>>  static const struct usb_phy_data am437x_usb2_data = {
>>>>  	.label = "am437x_usb2",
>>>>  	.flags =  0,
>>>> @@ -178,6 +183,10 @@ static const struct of_device_id omap_usb2_id_table[] = {
>>>>  		.data = &dra7x_usb2_data,
>>>>  	},
>>>>  	{
>>>> +		.compatible = "ti,dra7x-usb2-phy2",
>>>> +		.data = &dra7x_usb2_phy2_data,
>>>
>>> Why is this needed? You can reuse dra7x_usb2_data as is.
>>
>> OK. I see why we need it in the next patch.
>> Probably both patches could be squashed.
>>
>> What does .label indicate?
> 
> it's actually used only in usb_add_phy() (drivers/usb/phy/phy.c). I don't think
> it's actually important unless you strongly feel so.

I leave it to you then :).

cheers,
-roger

WARNING: multiple messages have this Message-ID (diff)
From: Roger Quadros <rogerq@ti.com>
To: Kishon Vijay Abraham I <kishon@ti.com>, <tony@atomide.com>,
	<t-kristo@ti.com>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-usb@vger.kernel.org>,
	<linux-omap@vger.kernel.org>
Cc: <balbi@ti.com>, <nsekhar@ti.com>
Subject: Re: [PATCH 6/7] phy: omap-usb2: Add a new compatible string for USB2 PHY2
Date: Fri, 7 Aug 2015 11:27:20 +0300	[thread overview]
Message-ID: <55C46BE8.9060804@ti.com> (raw)
In-Reply-To: <55C21B35.7010901@ti.com>

On 05/08/15 17:18, Kishon Vijay Abraham I wrote:
> Hi Roger,
> 
> On Wednesday 05 August 2015 01:55 PM, Roger Quadros wrote:
>> On 05/08/15 11:23, Roger Quadros wrote:
>>>
>>> On 04/08/15 18:20, Kishon Vijay Abraham I wrote:
>>>> The USB2 PHY2 has a different register map compared to USB2 PHY1
>>>> to power on/off the PHY. In order to handle it, add a new
>>>> "compatible" string.
>>>>
>>>> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
>>>> ---
>>>>  Documentation/devicetree/bindings/phy/ti-phy.txt |    2 ++
>>>>  drivers/phy/phy-omap-usb2.c                      |    9 +++++++++
>>>>  2 files changed, 11 insertions(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/phy/ti-phy.txt b/Documentation/devicetree/bindings/phy/ti-phy.txt
>>>> index 49e5b0c..a061077 100644
>>>> --- a/Documentation/devicetree/bindings/phy/ti-phy.txt
>>>> +++ b/Documentation/devicetree/bindings/phy/ti-phy.txt
>>>> @@ -31,6 +31,8 @@ OMAP USB2 PHY
>>>>  
>>>>  Required properties:
>>>>   - compatible: Should be "ti,omap-usb2"
>>>> +	       Should be "ti,dra7x-usb2-phy2" for the 2nd instance of USB2 PHY
>>>> +	       in DRA7x
>>>>   - reg : Address and length of the register set for the device.
>>>>   - #phy-cells: determine the number of cells that should be given in the
>>>>     phandle while referencing this phy.
>>>> diff --git a/drivers/phy/phy-omap-usb2.c b/drivers/phy/phy-omap-usb2.c
>>>> index b5c266a..2f7220f 100644
>>>> --- a/drivers/phy/phy-omap-usb2.c
>>>> +++ b/drivers/phy/phy-omap-usb2.c
>>>> @@ -159,6 +159,11 @@ static const struct usb_phy_data dra7x_usb2_data = {
>>>>  	.flags = OMAP_USB2_CALIBRATE_FALSE_DISCONNECT,
>>>>  };
>>>>  
>>>> +static const struct usb_phy_data dra7x_usb2_phy2_data = {
>>>> +	.label = "dra7x_usb2_phy2",
>>>> +	.flags = OMAP_USB2_CALIBRATE_FALSE_DISCONNECT,
>>>> +};
>>>> +
>>>>  static const struct usb_phy_data am437x_usb2_data = {
>>>>  	.label = "am437x_usb2",
>>>>  	.flags =  0,
>>>> @@ -178,6 +183,10 @@ static const struct of_device_id omap_usb2_id_table[] = {
>>>>  		.data = &dra7x_usb2_data,
>>>>  	},
>>>>  	{
>>>> +		.compatible = "ti,dra7x-usb2-phy2",
>>>> +		.data = &dra7x_usb2_phy2_data,
>>>
>>> Why is this needed? You can reuse dra7x_usb2_data as is.
>>
>> OK. I see why we need it in the next patch.
>> Probably both patches could be squashed.
>>
>> What does .label indicate?
> 
> it's actually used only in usb_add_phy() (drivers/usb/phy/phy.c). I don't think
> it's actually important unless you strongly feel so.

I leave it to you then :).

cheers,
-roger

  reply	other threads:[~2015-08-07  8:27 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 15:20 [PATCH 0/7] phy: use syscon framework APIs to set ctrl mod reg Kishon Vijay Abraham I
2015-08-04 15:20 ` Kishon Vijay Abraham I
2015-08-04 15:20 ` [PATCH 1/7] phy: ti-pipe3: cleanup ti_pipe3_probe() Kishon Vijay Abraham I
2015-08-04 15:20   ` Kishon Vijay Abraham I
     [not found]   ` <1438701646-7876-2-git-send-email-kishon-l0cyMroinI0@public.gmane.org>
2015-08-04 16:00     ` Felipe Balbi
2015-08-04 16:00       ` Felipe Balbi
     [not found]       ` <20150804160028.GG23659-HgARHv6XitJaoMGHk7MhZQC/G2K4zDHf@public.gmane.org>
2015-08-05 14:08         ` Kishon Vijay Abraham I
2015-08-05 14:08           ` Kishon Vijay Abraham I
2015-08-04 15:20 ` [PATCH 2/7] phy: ti-pipe3: use ti_pipe3_power_off to power off the PHY during probe Kishon Vijay Abraham I
2015-08-04 15:20   ` Kishon Vijay Abraham I
2015-08-04 16:06   ` Felipe Balbi
2015-08-04 16:06     ` Felipe Balbi
     [not found]     ` <20150804160631.GH23659-HgARHv6XitJaoMGHk7MhZQC/G2K4zDHf@public.gmane.org>
2015-08-05 14:12       ` Kishon Vijay Abraham I
2015-08-05 14:12         ` Kishon Vijay Abraham I
2015-08-05 15:35         ` Felipe Balbi
2015-08-05 15:35           ` Felipe Balbi
2015-08-04 15:20 ` [PATCH 3/7] phy: ti-pipe3: use *syscon* framework API to power on/off the PHY Kishon Vijay Abraham I
2015-08-04 15:20   ` Kishon Vijay Abraham I
     [not found] ` <1438701646-7876-1-git-send-email-kishon-l0cyMroinI0@public.gmane.org>
2015-08-04 15:20   ` [PATCH 4/7] phy: ti-pipe3: use *syscon* framework API to set PCS value of " Kishon Vijay Abraham I
2015-08-04 15:20     ` Kishon Vijay Abraham I
2015-08-04 15:20 ` [PATCH 5/7] phy: omap-usb2: use omap_usb_power_off to power off the PHY during probe Kishon Vijay Abraham I
2015-08-04 15:20   ` Kishon Vijay Abraham I
2015-08-04 16:07   ` Felipe Balbi
2015-08-04 16:07     ` Felipe Balbi
2015-08-04 15:20 ` [PATCH 6/7] phy: omap-usb2: Add a new compatible string for USB2 PHY2 Kishon Vijay Abraham I
2015-08-04 15:20   ` Kishon Vijay Abraham I
     [not found]   ` <1438701646-7876-7-git-send-email-kishon-l0cyMroinI0@public.gmane.org>
2015-08-05  8:23     ` Roger Quadros
2015-08-05  8:23       ` Roger Quadros
2015-08-05  8:25       ` Roger Quadros
2015-08-05  8:25         ` Roger Quadros
2015-08-05 14:18         ` Kishon Vijay Abraham I
2015-08-05 14:18           ` Kishon Vijay Abraham I
2015-08-07  8:27           ` Roger Quadros [this message]
2015-08-07  8:27             ` Roger Quadros
2015-08-04 15:20 ` [PATCH 7/7] phy: omap-usb2: use *syscon* framework API to power on/off the PHY Kishon Vijay Abraham I
2015-08-04 15:20   ` Kishon Vijay Abraham I
2015-08-05  8:35   ` Roger Quadros
2015-08-05  8:35     ` Roger Quadros
     [not found]     ` <55C1CAE1.3060901-l0cyMroinI0@public.gmane.org>
2015-08-05 14:21       ` Kishon Vijay Abraham I
2015-08-05 14:21         ` Kishon Vijay Abraham I

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55C46BE8.9060804@ti.com \
    --to=rogerq@ti.com \
    --cc=balbi@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=t-kristo@ti.com \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.