From: kishon@ti.com (Kishon Vijay Abraham I)
To: linux-arm-kernel@lists.infradead.org
Subject: 3.13-rc2 phy-twl4030-usb.c - Timeout setting T2 HSUSB PHY DPLL
Date: Fri, 10 Jan 2014 10:55:41 +0530 [thread overview]
Message-ID: <52CF8455.5090506@ti.com> (raw)
In-Reply-To: <52CE32AB.1050204@ti.com>
Hi,
On Thursday 09 January 2014 10:54 AM, Roger Quadros wrote:
> Hi Marek,
>
> I have no idea what is happening there. Have you tried using device tree boot?
> Board file boot support would be dropped eventually.
>
> Did you try if I2C read write to the twl4030 device works and all necessary clocks/supplies are
> present?
>
> Kishon, do you know what is causing the USB DPLL failure there?
Not sure what's causing those failures :-s
-Kishon
>
> cheers,
> -roger
>
> On 01/09/2014 02:31 AM, Belisko Marek wrote:
>> Any pointers? Still present in 3.13-rc7.
>>
>> On Wed, Dec 4, 2013 at 1:22 PM, Roger Quadros <rogerq@ti.com> wrote:
>>> +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
>>>>
>>>
>>
>> BR,
>>
>> marek
>>
>
next prev parent reply other threads:[~2014-01-10 5:25 UTC|newest]
Thread overview: 6+ 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-04 12:22 ` Roger Quadros
2014-01-08 21:01 ` Belisko Marek
2014-01-09 5:24 ` Roger Quadros
2014-01-10 5:25 ` Kishon Vijay Abraham I [this message]
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=52CF8455.5090506@ti.com \
--to=kishon@ti.com \
--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).