From: Felipe Balbi <balbi@ti.com>
To: Kevin Hilman <khilman@ti.com>
Cc: Hema HK <hemahk@ti.com>,
linux-omap@vger.kernel.org, linux-usb@vger.kernel.org,
Felipe Balbi <balbi@ti.com>, Tony Lindgren <tony@atomide.com>,
"Cousson, Benoit" <b-cousson@ti.com>,
Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 4/5 v6] OMAP2+: musb: HWMOD adaptation for musb. registration
Date: Tue, 15 Feb 2011 10:32:36 +0200 [thread overview]
Message-ID: <20110215083235.GG2570@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <87vd0mw3u9.fsf@ti.com>
On Mon, Feb 14, 2011 at 04:15:10PM -0800, Kevin Hilman wrote:
> Hema HK <hemahk@ti.com> writes:
>
> > Using omap_device_build API instead of platform_device_register for
> > OMAP2430,OMAP34xx and OMAP4430 musb device registration.
> > The device specific resources defined in centralized
> > database will be used.
>
> Except for AM35x.
>
> NACK, for same reasons as previous version of this patch.
Does it really make sense to hold on omap2plus HWMOD conversion because
of AM35x ? I mean, I understand it would be better to get all fixed up,
but loose another merge window for that ?
Can we get omap2plus in and AM35x on the next merge window ? At least
omap2plus would have been converted to hwmod and would be using
pm_runtime as we want.
--
balbi
next prev parent reply other threads:[~2011-02-15 8:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 14:07 Subject: [PATCH 0/5 v6]usb: musb: hwmod and runtime pm support for musb Hema HK
2011-02-10 14:07 ` [PATCH 2/5 v6] OMAP3xxx: hwmod data: Add USBOTG Hema HK
2011-02-10 14:07 ` [PATCH 3/5 v6] OMAP4430: hwmod data: Adding USBOTG Hema HK
[not found] ` <1297346881-13438-1-git-send-email-hemahk-l0cyMroinI0@public.gmane.org>
2011-02-10 14:07 ` [PATCH 1/5 v6] OMAP2430: hwmod data: Add USBOTG Hema HK
2011-02-10 14:08 ` [PATCH 4/5 v6] OMAP2+: musb: HWMOD adaptation for musb. registration Hema HK
[not found] ` <1297346881-13438-5-git-send-email-hemahk-l0cyMroinI0@public.gmane.org>
2011-02-15 0:15 ` Kevin Hilman
[not found] ` <87vd0mw3u9.fsf-l0cyMroinI0@public.gmane.org>
2011-02-15 6:30 ` Hema Kalliguddi
2011-02-15 8:32 ` Felipe Balbi [this message]
2011-02-15 16:12 ` Kevin Hilman
[not found] ` <87r5b9uvj8.fsf-l0cyMroinI0@public.gmane.org>
2011-02-16 10:57 ` Hema Kalliguddi
2011-02-10 14:08 ` [PATCH 5/5 v6] usb: musb: Using runtime pm APIs for musb Hema HK
2011-02-10 14:26 ` Felipe Balbi
2011-02-10 16:39 ` Hema Kalliguddi
2011-02-15 0:42 ` Kevin Hilman
[not found] ` <87oc6ew2lh.fsf-l0cyMroinI0@public.gmane.org>
2011-02-15 4:01 ` Kalliguddi, Hema
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=20110215083235.GG2570@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=b-cousson@ti.com \
--cc=hemahk@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=paul@pwsan.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 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.