linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 5/5] OMAP: mailbox: add omap_device latency information
Date: Mon, 13 Dec 2010 09:45:46 +0100	[thread overview]
Message-ID: <4D05DD3A.2050807@ti.com> (raw)
In-Reply-To: <AANLkTi=cQVr-T1mJeq9uaRn5VyXxBG-xcp79z898E6nx@mail.gmail.com>

On 12/11/2010 4:25 PM, Ramirez Luna, Omar wrote:
> On Fri, Dec 10, 2010 at 7:51 PM, Omar Ramirez Luna<omar.ramirez@ti.com>  wrote:
>> From: Felipe Contreras<felipe.contreras@gmail.com>
>>
>> So that we can enable the main clock.
>
> This should be:
>
> Subject: OMAP: mailbox: use runtime pm for clk and sysc handling
>
> Use runtime pm APIs to enable/disable mailbox clocks and to configure
> SYSCONFIG registers.
>
> And if someone agrees, device_latency can be merged with the previous
> patch for device_build. I'll wait for comments and resubmit.

Yes, you're right, the device latency has nothing to do in that patch. 
It should be in the previous patch: [PATCH v3 4/5] OMAP: mailbox: build 
device using omap_device/omap_hwmod.

regards,
Benoit

  reply	other threads:[~2010-12-13  8:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-11  1:51 [PATCH v3 0/5] omap: mailbox: hwmod support Omar Ramirez Luna
2010-12-11  1:51 ` [PATCH v3 1/5] OMAP2: hwmod data: add mailbox data Omar Ramirez Luna
2010-12-11  1:51 ` [PATCH v3 2/5] OMAP3: " Omar Ramirez Luna
2010-12-11  1:51 ` [PATCH v3 3/5] OMAP4: " Omar Ramirez Luna
2010-12-11  1:51 ` [PATCH v3 4/5] OMAP: mailbox: build device using omap_device/omap_hwmod Omar Ramirez Luna
2010-12-11  1:51 ` [PATCH v3 5/5] OMAP: mailbox: add omap_device latency information Omar Ramirez Luna
2010-12-11 15:25   ` Ramirez Luna, Omar
2010-12-13  8:45     ` Cousson, Benoit [this message]
2010-12-13 18:28   ` Kanigeri, Hari

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=4D05DD3A.2050807@ti.com \
    --to=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).