From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: "Jan Lübbe" <jlu@pengutronix.de>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Mark A. Greer" <mgreer@animalcreek.com>,
"Porter, Matt" <mporter@ti.com>
Subject: Re: am3517: USB state in 3.5-rc6
Date: Thu, 02 Aug 2012 11:52:08 +0200 [thread overview]
Message-ID: <501A4DC8.1010401@visionsystems.de> (raw)
In-Reply-To: <1343143805.834.3.camel@coredoba.hi.pengutronix.de>
Am 24.07.2012 17:30, schrieb Jan Lübbe:
> Hi,
>
> On Mon, 2012-07-23 at 09:08 +0200, Yegor Yefremov wrote:
>> After getting MMC working I now have following issues: both musb and EHCI make problems.
>>
>> musb:
>>
>> musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
>> musb-am35x musb-am35x: failed to get clock
>> musb-am35x: probe of musb-am35x failed with error -2
> I've seen the same problem after merging omap-devel-d-for-3.6 onto v3.5.
> (see http://git.kernel.org/?p=linux/kernel/git/pjw/omap-pending.git;a=tag;h=refs/tags/omap-devel-d-for-3.6)
>
> So far I've worked around it like this (I'm not sure this is the correct
> approach, but it works):
>
> diff --git a/drivers/usb/musb/am35x.c b/drivers/usb/musb/am35x.c
> index 9f3eda9..2184693 100644
> --- a/drivers/usb/musb/am35x.c
> +++ b/drivers/usb/musb/am35x.c
> @@ -480,14 +480,14 @@ static int __devinit am35x_probe(struct platform_device *pdev)
> goto err1;
> }
>
> - phy_clk = clk_get(&pdev->dev, "fck");
> + phy_clk = clk_get(&pdev->dev, "hsotgusb_ick");
> if (IS_ERR(phy_clk)) {
> dev_err(&pdev->dev, "failed to get PHY clock\n");
> ret = PTR_ERR(phy_clk);
> goto err2;
> }
>
> - clk = clk_get(&pdev->dev, "ick");
> + clk = clk_get(&pdev->dev, "hsotgusb_fck");
> if (IS_ERR(clk)) {
> dev_err(&pdev->dev, "failed to get clock\n");
> ret = PTR_ERR(clk);
Jan, thanks for the patch. It helped. I've taken the upcoming vanila 3.6 kernel and got both musb and EHCI running. I will test it further after linux-omap will be merged with linux-2.6 after merge window is closed.
Yegor
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-08-02 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 7:08 am3517: USB state in 3.5-rc6 Yegor Yefremov
2012-07-24 15:30 ` Jan Lübbe
2012-08-02 9:52 ` Yegor Yefremov [this message]
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=501A4DC8.1010401@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--cc=jlu@pengutronix.de \
--cc=linux-omap@vger.kernel.org \
--cc=mgreer@animalcreek.com \
--cc=mporter@ti.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.