From: Kishon Vijay Abraham I <kishon@ti.com>
To: Roger Quadros <rogerq@ti.com>, balbi@ti.com, tony@atomide.com
Cc: nm@ti.com, t-kristo@ti.com, linux-omap@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH 1/3] phy: omap-usb2: Manage PHY 3.3V supply regulator
Date: Tue, 1 Jul 2014 15:50:52 +0530 [thread overview]
Message-ID: <53B28B84.9080404@ti.com> (raw)
In-Reply-To: <53B289B1.6020705@ti.com>
Hi,
On Tuesday 01 July 2014 03:43 PM, Roger Quadros wrote:
> On 07/01/2014 12:56 PM, Kishon Vijay Abraham I wrote:
>> Hi Roger,
>>
>> On Monday 30 June 2014 04:30 PM, Roger Quadros wrote:
>>> On some SoCs e.g. J6 the 3.3V supply to the USB2 PHY can be
>>> powered down when the PHY is not in use. Add regulator
>>> management code to control this power line.
>>>
>>> Signed-off-by: Roger Quadros <rogerq@ti.com>
>>> ---
>>> drivers/phy/phy-omap-usb2.c | 25 +++++++++++++++++++++++++
>>> include/linux/phy/omap_usb.h | 1 +
>>> 2 files changed, 26 insertions(+)
>>>
>>> diff --git a/drivers/phy/phy-omap-usb2.c b/drivers/phy/phy-omap-usb2.c
>>> index 7007c11..2afc79c 100644
>>> --- a/drivers/phy/phy-omap-usb2.c
>>> +++ b/drivers/phy/phy-omap-usb2.c
>>> @@ -30,6 +30,7 @@
>>> #include <linux/phy/omap_control_phy.h>
>>> #include <linux/phy/phy.h>
>>> #include <linux/of_platform.h>
>>> +#include <linux/regulator/consumer.h>
>>>
>>> #define USB2PHY_DISCON_BYP_LATCH (1 << 31)
>>> #define USB2PHY_ANA_CONFIG1 0x4c
>>> @@ -107,6 +108,14 @@ static int omap_usb_power_off(struct phy *x)
>>>
>>> omap_control_phy_power(phy->control_dev, 0);
>>>
>>> + if (phy->pwr) {
>>> + int ret;
>>> +
>>> + ret = regulator_disable(phy->pwr);
>>> + if (ret)
>>> + return ret;
>>> + }
>>> +
>>> return 0;
>>> }
>>>
>>> @@ -114,6 +123,14 @@ static int omap_usb_power_on(struct phy *x)
>>> {
>>> struct omap_usb *phy = phy_get_drvdata(x);
>>>
>>> + if (phy->pwr) {
>>> + int ret;
>>> +
>>> + ret = regulator_enable(phy->pwr);
>>> + if (ret)
>>> + return ret;
>>> + }
>>> +
>>
>> Shouldn't we do this in phy_power_on/phy_power_off in phy-core?
>
> I thought about that earlier, but could not find a way to defer probing if the regulator is not-yet probed.
> Any clues how it could be done in phy-core?
We can try to do regulator_get in phy_create and return EPROBE_DEFER if the
regulator_get returns EPROBE_DEFER no?
Cheers
Kishon
next prev parent reply other threads:[~2014-07-01 10:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 11:00 [PATCH 0/3] PHY: ti-pipe3: Manage 3.3V PHY regulator Roger Quadros
[not found] ` <1404126038-19974-1-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2014-06-30 11:00 ` [PATCH 1/3] phy: omap-usb2: Manage PHY 3.3V supply regulator Roger Quadros
[not found] ` <1404126038-19974-2-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2014-06-30 17:09 ` Felipe Balbi
2014-07-01 9:56 ` Kishon Vijay Abraham I
[not found] ` <53B285DC.8070102-l0cyMroinI0@public.gmane.org>
2014-07-01 10:13 ` Roger Quadros
2014-07-01 10:20 ` Kishon Vijay Abraham I [this message]
2014-07-01 10:25 ` Roger Quadros
[not found] ` <53B28CB5.1070306-l0cyMroinI0@public.gmane.org>
2014-07-01 10:37 ` Kishon Vijay Abraham I
2014-06-30 11:00 ` [PATCH 2/3] phy: omap-usb2: Add PHY regulator to DT binding documentation Roger Quadros
2014-06-30 11:00 ` [PATCH 3/3] ARM: dts: dra7-evm: Add regulator information to USB2 PHYs Roger Quadros
2014-07-09 11:56 ` Tony Lindgren
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=53B28B84.9080404@ti.com \
--to=kishon@ti.com \
--cc=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nm@ti.com \
--cc=rogerq@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox