From: Kishon Vijay Abraham I <kishon@ti.com>
To: Vivek Gautam <gautamvivek1987@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Vivek Gautam <gautam.vivek@samsung.com>,
Linux USB Mailing List <linux-usb@vger.kernel.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
linux-omap@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>, Felipe Balbi <balbi@ti.com>,
Sarah Sharp <sarah.a.sharp@linux.intel.com>,
Kukjin Kim <kgene.kim@samsung.com>,
Jingoo Han <jg1.han@samsung.com>,
Julius Werner <jwerner@chromium.org>
Subject: Re: [PATCH RFC 1/4] phy: Add provision for tuning phy.
Date: Wed, 11 Dec 2013 13:47:13 +0530 [thread overview]
Message-ID: <52A81F89.4010603@ti.com> (raw)
In-Reply-To: <CAFp+6iENkrSUT=_iv+uZnVpDSGDQGOzF_oyZ6Dmzr8VcQfjztw@mail.gmail.com>
On Wednesday 11 December 2013 12:08 PM, Vivek Gautam wrote:
> Hi,
>
>
> On Tue, Dec 10, 2013 at 7:31 PM, Heikki Krogerus
> <heikki.krogerus@linux.intel.com> wrote:
>> Hi,
>
> Thanks for reviewing this.
>
>>
>> On Tue, Dec 10, 2013 at 04:25:23PM +0530, Vivek Gautam wrote:
>>> Some PHY controllers may need to tune PHY post-initialization,
>>> so that the PHY consumers can call phy-tuning at appropriate
>>> point of time.
>>>
>>> Signed-off-by: vivek Gautam <gautam.vivek@samsung.com>
>>> ---
>>> drivers/phy/phy-core.c | 20 ++++++++++++++++++++
>>> include/linux/phy/phy.h | 7 +++++++
>>> 2 files changed, 27 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c
>>> index 03cf8fb..68dbb90 100644
>>> --- a/drivers/phy/phy-core.c
>>> +++ b/drivers/phy/phy-core.c
>>> @@ -239,6 +239,26 @@ out:
>>> }
>>> EXPORT_SYMBOL_GPL(phy_power_off);
>>>
>>> +int phy_tune(struct phy *phy)
>>> +{
>>> + int ret = -ENOTSUPP;
>>> +
>>> + mutex_lock(&phy->mutex);
>>> + if (phy->ops->tune) {
>>> + ret = phy->ops->tune(phy);
>>> + if (ret < 0) {
>>> + dev_err(&phy->dev, "phy tuning failed --> %d\n", ret);
>>> + goto out;
>>> + }
>>> + }
>>> +
>>> +out:
>>> + mutex_unlock(&phy->mutex);
>>> +
>>> + return ret;
>>> +}
>>> +EXPORT_SYMBOL_GPL(phy_tune);
>>
>> I think "setup" instead of "tune" is much more clear and reusable.
>
> I think "setup" will look more like first time setting up the phy,
> which is rather served by "init" callback.
> This i thought would serve the purpose of over-riding certain PHY
> parameters, which would not have been
> possible at "init" time.
> Please correct my thinking if i am unable to understand your point here.
how about 'calibrate'?
Thanks
Kishon
>
>>
>> Thanks,
>>
>> --
>> heikki
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
next prev parent reply other threads:[~2013-12-11 8:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 10:55 [PATCH RFC 0/4] Fine tune USB 3.0 PHY on exynos5420 Vivek Gautam
2013-12-10 10:55 ` [PATCH RFC 1/4] phy: Add provision for tuning phy Vivek Gautam
2013-12-10 14:01 ` Heikki Krogerus
2013-12-11 6:38 ` Vivek Gautam
2013-12-11 8:09 ` Heikki Krogerus
2013-12-11 8:32 ` Vivek Gautam
2013-12-11 8:54 ` Heikki Krogerus
2013-12-11 8:17 ` Kishon Vijay Abraham I [this message]
2013-12-11 8:33 ` Vivek Gautam
2013-12-10 10:55 ` [PATCH RFC 2/4] xhci: Add quirk for DWC3-Exynos controller Vivek Gautam
2013-12-10 18:25 ` Julius Werner
2013-12-10 10:55 ` [PATCH RFC 3/4] xhci: Tune PHY for the DWC3-Exynos host controller Vivek Gautam
2013-12-10 13:55 ` Heikki Krogerus
2014-04-15 12:54 ` Vivek Gautam
2014-04-16 14:12 ` Heikki Krogerus
2014-04-21 4:20 ` Vivek Gautam
2013-12-10 10:55 ` [PATCH RFC 4/4] phy-exynos-usb3: Fine tune LOS levels for exynos5420 Vivek Gautam
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=52A81F89.4010603@ti.com \
--to=kishon@ti.com \
--cc=balbi@ti.com \
--cc=gautam.vivek@samsung.com \
--cc=gautamvivek1987@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jg1.han@samsung.com \
--cc=jwerner@chromium.org \
--cc=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.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