public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anand Gadiyar <gadiyar@ti.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Benoit Cousson <b-cousson@ti.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Paul Walmsley <paul@pwsan.com>, Greg KH <greg@kroah.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Felipe Balbi <balbi@ti.com>, Tony Lindgren <tony@atomide.com>,
	linux-omap@vger.kernel.org
Subject: Re: linux-next: manual merge of the usb tree with the omap tree
Date: Mon, 10 Jan 2011 19:39:24 +0530	[thread overview]
Message-ID: <4D2B1314.3010901@ti.com> (raw)
In-Reply-To: <AANLkTimakCyo5WB4v677-y+V=EO3nPiMTh+msnxkJiwH@mail.gmail.com>

On 1/10/2011 7:23 PM, Ming Lei wrote:
> Hi,
> 
> 2011/1/7 Anand Gadiyar <gadiyar@ti.com>:
> 
>> Update: I disabled CONFIG_OMAP_RESET_CLOCKS and the PHY and other
>> connected devices enumerate just fine. Could you try this out on
>> your board as well?
> 
> Yes, it does work for me if CONFIG_OMAP_RESET_CLOCKS is disabled.
> 
> thanks,

Great, patch coming up in a few minutes.

I figured out why we need auxclk3 - the PHY's reference clock
is provided by it.

- Anand


  reply	other threads:[~2011-01-10 14:09 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-23  6:18 linux-next: manual merge of the usb tree with the omap tree Stephen Rothwell
2010-12-23  8:36 ` Felipe Balbi
2010-12-23 18:29 ` Cousson, Benoit
2011-01-06 15:02   ` Ming Lei
2011-01-06 15:07     ` Anand Gadiyar
2011-01-06 15:25       ` Ming Lei
2011-01-06 15:50         ` Ming Lei
2011-01-07 14:07           ` Anand Gadiyar
2011-01-07 14:15             ` Ming Lei
2011-01-07 14:39               ` Anand Gadiyar
2011-01-07 15:20                 ` Anand Gadiyar
2011-01-07 18:54                   ` Gadiyar, Anand
2011-01-07 19:24                     ` Felipe Balbi
2011-01-10 13:53                   ` Ming Lei
2011-01-10 14:09                     ` Anand Gadiyar [this message]
2011-01-06 15:43       ` Brad Parker
2011-01-06 16:59         ` Koen Kooi
2011-01-06 17:57           ` Nishanth Menon
2011-01-06 18:15           ` Kevin Hilman
2011-01-06 18:21             ` Nishanth Menon
2011-01-06 18:38               ` Kevin Hilman
2011-01-06 20:24                 ` Nishanth Menon
2011-01-06 21:29                   ` Kevin Hilman
2011-01-06 18:27             ` Paul Walmsley
  -- strict thread matches above, loose matches on Subject: below --
2011-03-02  5:58 Stephen Rothwell
2011-03-02  5:58 Stephen Rothwell
2011-03-02  5:57 Stephen Rothwell
2011-03-03  8:48 ` Felipe Balbi
2011-03-03 16:02   ` Greg KH
2011-03-03 17:39     ` Felipe Balbi
2011-03-02  5:57 Stephen Rothwell
2011-03-02  8:23 ` Felipe Balbi
2011-03-02 14:23 ` Greg KH
2011-03-03  8:18   ` Felipe Balbi
2009-11-11  8:30 Stephen Rothwell
2009-11-11 19:12 ` Tony Lindgren
2009-11-11 19:20   ` Tony Lindgren
2009-11-11 21:52     ` Stephen Rothwell

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=4D2B1314.3010901@ti.com \
    --to=gadiyar@ti.com \
    --cc=b-cousson@ti.com \
    --cc=balbi@ti.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=sfr@canb.auug.org.au \
    --cc=tom.leiming@gmail.com \
    --cc=tony@atomide.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