From: "Cousson, Benoit" <b-cousson@ti.com>
To: "DebBarma, Tarun Kanti" <tarun.kanti@ti.com>
Cc: "tony@atomide.com" <tony@atomide.com>,
"Hilman, Kevin" <khilman@ti.com>,
"paul@pwsan.com" <paul@pwsan.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/2] ARM: OMAP2+: timer fixes / cleanup
Date: Mon, 10 Oct 2011 13:56:19 +0200 [thread overview]
Message-ID: <4E92DD63.6090906@ti.com> (raw)
In-Reply-To: <CAC83ZvLd27nER5z1R1L27KFR4CQ1mwhmQ18BR7OCBZEDtNFWYg@mail.gmail.com>
On 10/10/2011 12:05 PM, DebBarma, Tarun Kanti wrote:
> On Mon, Oct 10, 2011 at 11:10 AM, DebBarma, Tarun Kanti
> <tarun.kanti@ti.com> wrote:
>> On Wed, Oct 5, 2011 at 3:06 AM, Cousson, Benoit<b-cousson@ti.com> wrote:
>>> Hi Tarun,
>>>
>>> On 10/4/2011 11:20 PM, Cousson, Benoit wrote:
>>>>
>>>> Hi Tony,
>>>>
>>>> Here is the series to fix the warning and remove the redundant
>>>> latency structure that be removed since the timer runtime PM
>>>> adaptation was just pulled.
>>>>
>>>> I was just able to test that on OMAP4.
>>>
>>> It will be nice if you can test that on the other platforms.
>>> In theory, if they are properly using hwmod that should work fine.
>> Yes, I will test in other platforms.
> I have tested on OMAP2420, OMAP2430 and OMAP3430.
Thanks Tarun,
Regards,
Benoit
next prev parent reply other threads:[~2011-10-10 11:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 21:20 [PATCH 0/2] ARM: OMAP2+: timer fixes / cleanup Benoit Cousson
2011-10-04 21:20 ` [PATCH 1/2] ARM: OMAP2+: clock data: Remove redundant timer clkdev Benoit Cousson
2011-10-04 21:20 ` [PATCH 2/2] ARM: OMAP2+: timer: Remove omap_device_pm_latency Benoit Cousson
2011-10-04 21:36 ` [PATCH 0/2] ARM: OMAP2+: timer fixes / cleanup Cousson, Benoit
2011-10-10 5:40 ` DebBarma, Tarun Kanti
2011-10-10 10:05 ` DebBarma, Tarun Kanti
2011-10-10 11:56 ` Cousson, Benoit [this message]
2011-10-06 20:12 ` Tony Lindgren
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=4E92DD63.6090906@ti.com \
--to=b-cousson@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tarun.kanti@ti.com \
--cc=tony@atomide.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