From: jon-hunter@ti•com (Jon Hunter)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/3] ARM: OMAP4: Clock fixes
Date: Thu, 29 Nov 2012 11:03:00 -0600 [thread overview]
Message-ID: <50B79544.8030507@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1211291120220.20529@utopia.booyaka.com>
On 11/29/2012 05:21 AM, Paul Walmsley wrote:
> Hi Jon,
>
> On Wed, 7 Nov 2012, Jon Hunter wrote:
>
>> Fixes included, fixing up timer clock aliases for v3.8 and working
>> around ABE DPLL issue seen with latest u-boot bootloader (v2012.10).
>>
>> Testing includes:
>> - Boot testing on OMAP3430 Beagle, OMAP4430 Panda and OMAP4460 Panda
>> - Boot tested with device-tree on OMAP4430 Panda and OMAP4460 Panda
>> and validated that all timers are working.
>> - Suspend testing on OMAP3430 Beagle and OMAP4430 Panda (suspend not
>> functional on OMAP4460 Panda prior to this series and so could not
>> be tested).
>> - Core retention validated on OMAP3430 Beagle.
>>
>> Jon Hunter (3):
>> ARM: OMAP4: Update timer clock aliases
>> ARM: OMAP4: Enhance support for DPLLs with 4X multiplier
>> ARM: OMAP4460: Workaround ABE DPLL failing to turn-on
>
> So I'd plan to queue #2 and #3 for v3.8-rc1. But they need to be updated
> after the common clock framework conversion. Could you update those to
> apply on the arm-soc for-next branch?
Yes no problem.
Cheers
Jon
prev parent reply other threads:[~2012-11-29 17:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 18:42 [PATCH 0/3] ARM: OMAP4: Clock fixes Jon Hunter
2012-11-07 18:43 ` [PATCH 1/3] ARM: OMAP4: Update timer clock aliases Jon Hunter
2012-11-29 10:53 ` Paul Walmsley
2012-11-29 17:02 ` Jon Hunter
2012-11-07 18:43 ` [PATCH 2/3] ARM: OMAP4: Enhance support for DPLLs with 4X multiplier Jon Hunter
2012-11-07 18:43 ` [PATCH 3/3] ARM: OMAP4460: Workaround ABE DPLL failing to turn-on Jon Hunter
2012-11-29 11:21 ` [PATCH 0/3] ARM: OMAP4: Clock fixes Paul Walmsley
2012-11-29 17:03 ` Jon Hunter [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=50B79544.8030507@ti.com \
--to=jon-hunter@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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