public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Vikram Pandita <vikram.pandita@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH][pm-2.6.29] OMAP: PM: Fix MUSB power domain association
Date: Fri, 07 Aug 2009 17:02:32 -0700	[thread overview]
Message-ID: <87iqgzkw9z.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1249688520-22946-1-git-send-email-vikram.pandita@ti.com> (Vikram Pandita's message of "Fri\,  7 Aug 2009 18\:42\:00 -0500")

Vikram Pandita <vikram.pandita@ti.com> writes:

> MUSB lies in CORE power domain.
> Current code wrongly associates MUSB with USBHOST domain.
> USBHOST domain is for EHCI/OHCI controller.
>
> Correct the association of MUSB to CORE power domain.
>
> Signed-off-by: Vikram Pandita <vikram.pandita@ti.com>

Thanks, pushed to pm-2.6.29 branch.
(Not relevant to current PM branch due to new omap_hwmod/omap_device 
infrastructure.)

Kevin

> ---
>  arch/arm/mach-omap2/omapdev3xxx.h |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/omapdev3xxx.h b/arch/arm/mach-omap2/omapdev3xxx.h
> index d2772c4..fd29129 100644
> --- a/arch/arm/mach-omap2/omapdev3xxx.h
> +++ b/arch/arm/mach-omap2/omapdev3xxx.h
> @@ -663,7 +663,7 @@ static struct omapdev usbhost_3xxx_omapdev = {
>  
>  static struct omapdev usbotg_3xxx_omapdev = {
>  	.name		= "usbotg_omapdev",
> -	.pwrdm		= { .name = "usbhost_pwrdm" },
> +	.pwrdm		= { .name = "core_pwrdm" },
>  	.pdev_name	= "musb_hdrc",
>  	.pdev_id	= -1,
>  	.omap_chip	= OMAP_CHIP_INIT(CHIP_GE_OMAP3430ES2),
> -- 
> 1.6.3.3.334.g916e1

      reply	other threads:[~2009-08-08  0:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07 23:42 [PATCH][pm-2.6.29] OMAP: PM: Fix MUSB power domain association Vikram Pandita
2009-08-08  0:02 ` Kevin Hilman [this message]

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=87iqgzkw9z.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=vikram.pandita@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