linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rajendra Nayak <rnayak@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: mturquette@ti.com, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC 00/24] Move OMAP2+ over to use COMMON clock
Date: Mon, 04 Jun 2012 14:08:10 +0530	[thread overview]
Message-ID: <4FCC73F2.4030808@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1206010735540.17068@utopia.booyaka.com>

On Friday 01 June 2012 07:07 PM, Paul Walmsley wrote:
> On Fri, 1 Jun 2012, Rajendra Nayak wrote:
>
>> This RFC series is based of Mikes' latest clk-next. I will
>> rebase it once 3.5-rc1 is out and post with more testing thats
>> in progress. Meanwhile, the RFC is for me to get some early
>> feedback on the patches.
>
> Please describe further what's been tested with this series, and what
> hasn't been.

Hi Paul,

I have been mostly boot-testing on the OMAP3/4 boards I have access to, 
3430SDP, 3630 Beagle, 4430 Panda/SDP. Apart from this I was using
omapconf to run the clkspeed audit tests on OMAP4.
I used powerdebug to make sure the tree modeling (parent/child
relations, clk rates etc) are sane after bootup.
I haven't done any low power tests around suspend/idle for OMAP3
or OMAP4 which is on my list to do before I do a repost/rebase on
3.5-rc1. And so is testing on OMAP2430sdp and N800. Any other tests
you recommend I do?

Meanwhile it would be good to know if you see any major issues around
the migration itself and/or the way the patches are structured.

regards,
Rajendra

>
>
> - Paul


  reply	other threads:[~2012-06-04  8:38 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-01 12:07 [RFC 00/24] Move OMAP2+ over to use COMMON clock Rajendra Nayak
2012-06-01 12:07 ` [RFC 01/24] clk: Add CLK_IS_BASIC flag to identify basic clocks Rajendra Nayak
2012-06-01 12:07 ` [RFC 02/24] ARM: omap4: cm: add bitfield width values Rajendra Nayak
2012-06-01 12:07 ` [RFC 03/24] ARM: omap: clk: convert all clk_enable to clk_prepare_enable Rajendra Nayak
2012-06-01 12:07 ` [RFC 04/24] ARM: omap: hwmod: get rid of all omap_clk_get_by_name usage Rajendra Nayak
2012-06-01 12:07 ` [RFC 05/24] ARM: omap: clk: Nuke plat clock.c & clock.h if CONFIG_COMMON_CLK Rajendra Nayak
2012-06-04 13:57   ` Jon Hunter
2012-06-04 14:16     ` Rajendra Nayak
2012-06-04 14:25       ` Jon Hunter
2012-06-05  4:58         ` Rajendra Nayak
2012-06-05 13:11           ` Jon Hunter
2012-06-01 12:07 ` [RFC 06/24] ARM: omap: clk: Remove all direct dereferncing of struct clk Rajendra Nayak
2012-06-01 12:07 ` [RFC 07/24] ARM: omap: hwmod: Fix up hwmod based clkdm accesses Rajendra Nayak
2012-06-01 12:07 ` [RFC 08/24] ARM: omap4: clk: Convert to common clk Rajendra Nayak
2012-06-01 12:07 ` [RFC 09/24] ARM: omap3: " Rajendra Nayak
2012-06-01 12:07 ` [RFC 10/24] ARM: omap2: " Rajendra Nayak
2012-06-01 12:07 ` [RFC 11/24] ARM: omap: clk: list all clk_hw_omap clks to enable/disable autoidle Rajendra Nayak
2012-06-04  5:44   ` Tony Lindgren
2012-06-04  8:53     ` Rajendra Nayak
2012-06-01 12:07 ` [RFC 12/24] ARM: omap: clk: Define a function to enable clocks at init Rajendra Nayak
2012-06-01 12:07 ` [RFC 13/24] ARM: omap4: clk: Add 44xx data using common struct clk Rajendra Nayak
2012-06-04 22:14   ` Jon Hunter
2012-06-05  4:35     ` Rajendra Nayak
2012-06-05  6:42   ` Tony Lindgren
2012-06-05  6:44     ` Tony Lindgren
2012-06-07  5:29     ` Rajendra Nayak
2012-06-20 11:39       ` Tony Lindgren
2012-06-21  6:28         ` Rajendra Nayak
2012-06-21  7:00           ` Tony Lindgren
2012-06-01 12:07 ` [RFC 14/24] ARM: omap3: clk: Add 3xxx " Rajendra Nayak
2012-06-01 12:07 ` [RFC 15/24] ARM: omap2: clk: Add 24xx " Rajendra Nayak
2012-06-01 12:07 ` [RFC 16/24] ARM: omap: clk: Switch to COMMON clk Rajendra Nayak
2012-06-01 12:07 ` [RFC 17/24] ARM: omap: clk: Use plat clock.c & clock.h only for OMAP1 Rajendra Nayak
2012-06-01 12:07 ` [RFC 18/24] ARM: omap: hwmod: Cleanup !CONFIG_COMMON_CLK parts Rajendra Nayak
2012-06-01 12:08 ` [RFC 19/24] ARM: omap4: clk: " Rajendra Nayak
2012-06-01 12:08 ` [RFC 20/24] ARM: omap3: " Rajendra Nayak
2012-06-01 12:08 ` [RFC 21/24] ARM: omap2: " Rajendra Nayak
2012-06-01 12:08 ` [RFC 22/24] ARM: omap4: clk: Delete old OMAP clock data Rajendra Nayak
2012-06-01 12:08 ` [RFC 23/24] ARM: omap3: " Rajendra Nayak
2012-06-01 12:08 ` [RFC 24/24] ARM: omap2: " Rajendra Nayak
2012-06-01 13:37 ` [RFC 00/24] Move OMAP2+ over to use COMMON clock Paul Walmsley
2012-06-04  8:38   ` Rajendra Nayak [this message]
2012-06-01 17:58 ` Mike Turquette
2012-06-01 20:37 ` Jon Hunter
2012-06-01 23:27 ` Jon Hunter
2012-06-04  8:52   ` Rajendra Nayak
2012-06-04 13:51     ` Jon Hunter
2012-06-04 14:04       ` Rajendra Nayak

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=4FCC73F2.4030808@ti.com \
    --to=rnayak@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@ti.com \
    --cc=paul@pwsan.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;
as well as URLs for NNTP newsgroup(s).