linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Munegowda, Keshava" <keshava_mgowda@ti.com>
Cc: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
	linux-omap@vger.kernel.org, Partha Basak <parthab@india.ti.com>,
	sameo@linux.intel.com, balbi@ti.com,
	Kevin Hilman <khilman@ti.com>
Subject: Re: [PATCH] OMAP: config : disable the usb host configuration in omap2plus_defconfig
Date: Fri, 6 Jul 2012 05:39:13 -0700	[thread overview]
Message-ID: <20120706123913.GX1122@atomide.com> (raw)
In-Reply-To: <CAP05o4L6CXjgDCe_eoY15aKFNDf7vMcYJGOqxpE3rMPSAxU57w@mail.gmail.com>

* Munegowda, Keshava <keshava_mgowda@ti.com> [120706 05:30]:
> On Fri, Jul 6, 2012 at 5:37 PM, Tony Lindgren <tony@atomide.com> wrote:
> >
> > I think it's best to fix things properly, even if it means that it will
> > take longer and go into next kernel version.
> 
>     This requires ehci remote wakeup feature to be implemented, which
> will take at least to 3 months to
> get reviewed in opensource.
> hence for now  kevin is also agreed to disable it by default;

Why does echi need a "remote wakeup" feature? If you're talking about
echi wake-up events, I don't see how that would affect core retention.

Tony

  reply	other threads:[~2012-07-06 12:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06 11:49 [PATCH] OMAP: config : disable the usb host configuration in omap2plus_defconfig Keshava Munegowda
2012-07-06 11:55 ` Munegowda, Keshava
2012-07-06 11:59   ` Shilimkar, Santosh
2012-07-06 12:01     ` Munegowda, Keshava
2012-07-06 12:07       ` Tony Lindgren
2012-07-06 12:25         ` Munegowda, Keshava
2012-07-06 12:39           ` Tony Lindgren [this message]
2012-07-06 13:34             ` Munegowda, Keshava
2012-07-06 14:13 ` Kevin Hilman
     [not found]   ` <87d349c70t.fsf-l0cyMroinI0@public.gmane.org>
2012-07-06 18:11     ` Kevin Hilman

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=20120706123913.GX1122@atomide.com \
    --to=tony@atomide.com \
    --cc=balbi@ti.com \
    --cc=keshava_mgowda@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=parthab@india.ti.com \
    --cc=sameo@linux.intel.com \
    --cc=santosh.shilimkar@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 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).