From: Roger Quadros <rogerq@ti.com>
To: Belisko Marek <marek.belisko@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
"ABRAHAM, KISHON VIJAY" <kishon@ti.com>,
Linux USB Mailing List <linux-usb@vger.kernel.org>
Subject: Re: 3.13-rc2 phy-twl4030-usb.c - Timeout setting T2 HSUSB PHY DPLL
Date: Wed, 4 Dec 2013 14:22:33 +0200 [thread overview]
Message-ID: <529F1E89.6080700@ti.com> (raw)
In-Reply-To: <CAAfyv37aM6SrpuU9fzKA6GKsWn=To5ANOpG_kSX509NjMjdecA@mail.gmail.com>
+Kishon
On 12/03/2013 11:33 PM, Belisko Marek wrote:
> Hi,
>
> current 3.13-rcX break usb support on gta04 board (similar to
> beagleboard) when booting via board file.
>
> In console we can see messages:
> [ 5227.287841] twl4030_usb twl4030_usb: Timeout setting T2 HSUSB PHY DPLL clock
> [ 5232.936096] omap_musb_mailbox: musb core is not yet ready
> [ 5233.958160] twl4030_usb twl4030_usb: Timeout setting T2 HSUSB PHY DPLL clock
> [ 5235.058227] twl4030_usb twl4030_usb: Timeout setting T2 HSUSB PHY DPLL clock
>
> Any pointer what could cause that? (in 3.12 usb works fine)
>
> BR,
>
> marek
>
WARNING: multiple messages have this Message-ID (diff)
From: rogerq@ti.com (Roger Quadros)
To: linux-arm-kernel@lists.infradead.org
Subject: 3.13-rc2 phy-twl4030-usb.c - Timeout setting T2 HSUSB PHY DPLL
Date: Wed, 4 Dec 2013 14:22:33 +0200 [thread overview]
Message-ID: <529F1E89.6080700@ti.com> (raw)
In-Reply-To: <CAAfyv37aM6SrpuU9fzKA6GKsWn=To5ANOpG_kSX509NjMjdecA@mail.gmail.com>
+Kishon
On 12/03/2013 11:33 PM, Belisko Marek wrote:
> Hi,
>
> current 3.13-rcX break usb support on gta04 board (similar to
> beagleboard) when booting via board file.
>
> In console we can see messages:
> [ 5227.287841] twl4030_usb twl4030_usb: Timeout setting T2 HSUSB PHY DPLL clock
> [ 5232.936096] omap_musb_mailbox: musb core is not yet ready
> [ 5233.958160] twl4030_usb twl4030_usb: Timeout setting T2 HSUSB PHY DPLL clock
> [ 5235.058227] twl4030_usb twl4030_usb: Timeout setting T2 HSUSB PHY DPLL clock
>
> Any pointer what could cause that? (in 3.12 usb works fine)
>
> BR,
>
> marek
>
next prev parent reply other threads:[~2013-12-04 12:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 21:33 3.13-rc2 phy-twl4030-usb.c - Timeout setting T2 HSUSB PHY DPLL Belisko Marek
2013-12-03 21:33 ` Belisko Marek
2013-12-04 12:22 ` Roger Quadros [this message]
2013-12-04 12:22 ` Roger Quadros
2014-01-08 21:01 ` Belisko Marek
2014-01-08 21:01 ` Belisko Marek
[not found] ` <CAAfyv36sNyEiEHEOKfZWN1xRYLGUt-NW18uhcJbSTWRBA5=2BA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-01-09 5:24 ` Roger Quadros
2014-01-09 5:24 ` Roger Quadros
2014-01-09 5:24 ` Roger Quadros
2014-01-10 5:25 ` Kishon Vijay Abraham I
2014-01-10 5:25 ` Kishon Vijay Abraham I
2014-01-10 5:25 ` Kishon Vijay Abraham I
[not found] ` <52CF8455.5090506-l0cyMroinI0@public.gmane.org>
2014-01-10 6:55 ` Belisko Marek
2014-01-10 6:55 ` Belisko Marek
2014-01-10 6:55 ` Belisko Marek
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=529F1E89.6080700@ti.com \
--to=rogerq@ti.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marek.belisko@gmail.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.