public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCHv2] OMAP3: PM: Ensure MUSB is accessible before we attempt to reset it
Date: Fri, 14 Aug 2009 11:11:20 -0700	[thread overview]
Message-ID: <87fxbu8dvb.fsf@deeprootsystems.com> (raw)
In-Reply-To: <4A859DF7.1070303@ti.com> (Jon Hunter's message of "Fri\, 14 Aug 2009 12\:25\:11 -0500")

Jon Hunter <jon-hunter@ti.com> writes:

> Kevin Hilman wrote:
>> Jon, you're raising the bar and spoiling us with such descriptive
>> changelogs.  If everyone was as thorough as you, the world would be a
>> merrier place. :)
>>
>> Thanks, pushing to PM branch and pm-2.6.29.
>>
>> Kevin
>
> No problem. You are welcome. Just an FYI, but for 2.6.29, I was doing
> some testing this morning and I found that I needed to make the
> following change to the patch to make it work for 2.6.29. You are
> probably aware already as this makes the patch similar to your
> original patch for mmc-reset.
>
> -	dev_set_name(dev, "musb_hdrc");
> -	otg_clk = clk_get(dev, "ick");
> +	otg_clk = clk_get(dev, "hsotgusb_ick");

Ah yes, I thought of that when I first saw the patch but forgot to do
that on pm-2.6.29.

Thanks, pushing to pm-2.6.29.

Kevin

  reply	other threads:[~2009-08-14 18:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 20:46 [PATCHv2] OMAP3: PM: Ensure MUSB is accessible before we attempt to reset it Jon Hunter
2009-08-13 22:20 ` Kevin Hilman
2009-08-13 22:52   ` Kevin Hilman
2009-08-14 17:25   ` Jon Hunter
2009-08-14 18:11     ` Kevin Hilman [this message]
2009-08-17  8:13       ` Tony Lindgren
2009-08-18  9:04         ` Kevin Hilman
2009-08-18  9:07         ` 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=87fxbu8dvb.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=jon-hunter@ti.com \
    --cc=linux-omap@vger.kernel.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