linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mkl@pengutronix.de (Marc Kleine-Budde)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] usb: phy: omap-usb2: enable 960Mhz clock for omap5
Date: Wed, 19 Sep 2012 16:50:12 +0200	[thread overview]
Message-ID: <5059DBA4.5010906@pengutronix.de> (raw)
In-Reply-To: <20120919144247.GB7004@arwen.pp.htv.fi>

On 09/19/2012 04:42 PM, Felipe Balbi wrote:
> On Wed, Sep 19, 2012 at 04:45:01PM +0200, Marc Kleine-Budde wrote:
>> On 09/19/2012 01:56 PM, Felipe Balbi wrote:
>>> On Wed, Sep 19, 2012 at 05:00:29PM +0530, Kishon Vijay Abraham I wrote:
>>>> "usb_otg_ss_refclk960m" is needed by usb2 phy present in omap5. For
>>>> omap4, the clk_get of this clock will fail since it does not have this
>>>> clock.
>>>>
>>>> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
>>>> ---
>>>>  Documentation/devicetree/bindings/usb/usb-phy.txt |    3 +++
>>>>  drivers/usb/phy/omap-usb2.c                       |   28 ++++++++++++++++++++-
>>>>  2 files changed, 30 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/usb/usb-phy.txt b/Documentation/devicetree/bindings/usb/usb-phy.txt
>>>> index 7c5fd89..d5626de 100644
>>>> --- a/Documentation/devicetree/bindings/usb/usb-phy.txt
>>>> +++ b/Documentation/devicetree/bindings/usb/usb-phy.txt
>>>> @@ -24,6 +24,9 @@ Required properties:
>>>>  add the address of control module phy power register until a driver for
>>>>  control module is added
>>>>  
>>>> +Optional properties:
>>>> + - has960mhzclk: should be added if the phy needs 960mhz clock
>>>> +
>>>>  This is usually a subnode of ocp2scp to which it is connected.
>>>>  
>>>>  usb3phy at 4a084400 {
>>>> diff --git a/drivers/usb/phy/omap-usb2.c b/drivers/usb/phy/omap-usb2.c
>>>> index d36c282..d6612ba 100644
>>>> --- a/drivers/usb/phy/omap-usb2.c
>>>> +++ b/drivers/usb/phy/omap-usb2.c
>>>> @@ -146,6 +146,7 @@ static int __devinit omap_usb2_probe(struct platform_device *pdev)
>>>>  	struct omap_usb			*phy;
>>>>  	struct usb_otg			*otg;
>>>>  	struct resource			*res;
>>>> +	struct device_node		*np = pdev->dev.of_node;
>>>>  
>>>>  	phy = devm_kzalloc(&pdev->dev, sizeof(*phy), GFP_KERNEL);
>>>>  	if (!phy) {
>>>> @@ -190,6 +191,15 @@ static int __devinit omap_usb2_probe(struct platform_device *pdev)
>>>>  	}
>>>>  	clk_prepare(phy->wkupclk);
>>>>  
>>>> +	if (of_property_read_bool(np, "has960mhzclk")) {
>>>> +		phy->optclk = devm_clk_get(phy->dev, "usb_otg_ss_refclk960m");
>>>> +		if (IS_ERR(phy->optclk)) {
>>>> +			dev_err(&pdev->dev, "unable to get refclk960m\n");
>>>> +			return PTR_ERR(phy->optclk);
>>>> +		}
>>>> +		clk_prepare(phy->optclk);
>>>> +	}
>>>
>>> instead, can't you just always try to get the clock but ignore the error
>>> if it fails ?
>>
>> On imx we add no-op dummy clocks, so that the drivers will always find
>> all needed clocks. If a clk_get fails it's an error.
> 
> It's an error from a clk API point of view, it doesn't mean device can't
> work without that optional clock. Drivers are free to treat errors
> however they like, even by ignoring it and defaulting to some other
> behavior.

Sure.

> Adding dummy clocks just bloats the kernel with useless data IMHO.

Just wanted to point out there's more than one way to do it.

Marc
-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120919/d09bd1e8/attachment-0001.sig>

  reply	other threads:[~2012-09-19 14:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 11:30 [PATCH 0/4] usb: phy: add usb3 phy driver Kishon Vijay Abraham I
2012-09-19 11:30 ` [PATCH 1/4] usb: phy: add a new driver for usb3 phy Kishon Vijay Abraham I
2012-09-19 14:41   ` Marc Kleine-Budde
2012-09-21  6:08     ` ABRAHAM, KISHON VIJAY
2012-10-11  0:59   ` Tony Lindgren
2012-10-12  9:08     ` kishon
2012-10-12 15:03       ` Tony Lindgren
2012-09-19 11:30 ` [PATCH 2/4] usb: dwc3: Fix gadget pullup in SS mode Kishon Vijay Abraham I
2012-09-19 11:53   ` Felipe Balbi
2012-09-19 15:02     ` Sonasath, Moiz
2012-09-19 16:04       ` Felipe Balbi
2012-09-19 16:50         ` Sonasath, Moiz
2012-09-19 17:24           ` Felipe Balbi
2012-09-19 17:29             ` Felipe Balbi
2012-09-19 11:30 ` [PATCH 3/4] usb: phy: omap-usb3: Decrease the number of transitions to recovery Kishon Vijay Abraham I
2012-09-19 11:55   ` Felipe Balbi
2012-09-19 11:30 ` [PATCH 4/4] usb: phy: omap-usb2: enable 960Mhz clock for omap5 Kishon Vijay Abraham I
2012-09-19 11:56   ` Felipe Balbi
2012-09-19 14:45     ` Marc Kleine-Budde
2012-09-19 14:42       ` Felipe Balbi
2012-09-19 14:50         ` Marc Kleine-Budde [this message]
2012-09-26  5:40     ` ABRAHAM, KISHON VIJAY
2012-09-26 18:27       ` Felipe Balbi
2012-09-27  5:13         ` ABRAHAM, KISHON VIJAY
2012-09-27  5:13           ` Felipe Balbi

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=5059DBA4.5010906@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).