From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Nayak, Rajendra" <rnayak@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: collaboration on hwmod conversions and runtime PM
Date: Fri, 21 May 2010 08:06:33 -0700 [thread overview]
Message-ID: <87ljbdl2fa.fsf@deeprootsystems.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB0322FA7EE5@dbde02.ent.ti.com> (Rajendra Nayak's message of "Fri\, 21 May 2010 16\:28\:12 +0530")
"Nayak, Rajendra" <rnayak@ti.com> writes:
>> There has been quite a bit of activity on the hwmod front, but no
>> common place to combine patches for testing.
>>
>> To that end, I've update the pm-wip/hwmods branch in my tree to
>> the two fixes/cleanup series from Benoit (which will be merged
>> via for 2.6.35):
>>
>> [PATCH 00/10] OMAP: HWMOD fixes and cleanup
>> [PATCH 0/5] OMAP4: PRCM: Spring cleanup
>>
>> On top of this, there is the pm-wip/hwmods-omap4 branch which includes
>> the OMAP4 series from Benoit
>>
>> [PATCH 0/6] OMAP: hwmod: Full data set for OMAP4430 ES1.0
>>
>> so that conversions for OMAP4 can also be done and tested. Note that
>> I've reverted the two "temporary" patches in this series since they
>> cause problems on OMAP3,
>
> Hi Kevin,
>
> These temp patches might not be needed anymore, even for omap4. The clockdomain
> has cpu checks to take care of the dependency, and there is already a patch from
> Santosh to keep the emif clocks always active.
>
> If you pull these 2 patches, we don't need the hacks anymore and multi omap build
> would work as well on these branches.
> https://patchwork.kernel.org/patch/100932/
> https://patchwork.kernel.org/patch/96048/
OK, I'll pull those two in while waiting for them to merge upstream.
> I was able to boot test on my 4430sdp with these 2 patches on pm-wip/hwmods-omap4
> branch.
Excellent, Thanks for testing!
Kevin
prev parent reply other threads:[~2010-05-21 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 23:56 collaboration on hwmod conversions and runtime PM Kevin Hilman
2010-05-21 10:58 ` Nayak, Rajendra
2010-05-21 15:06 ` 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=87ljbdl2fa.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@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 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.