From: khilman@deeprootsystems•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: OMAP: convert I2C driver to PM QoS for MPU latency constraints
Date: Mon, 24 Sep 2012 17:48:07 -0700 [thread overview]
Message-ID: <878vbzj5bs.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1348157283-24119-1-git-send-email-j-pihet@ti.com> (Jean Pihet's message of "Thu, 20 Sep 2012 18:08:03 +0200")
Jean Pihet <jean.pihet@newoldbits•com> writes:
> Convert the driver from the outdated omap_pm_set_max_mpu_wakeup_lat
> API to the new PM QoS API.
> Since the constraint is on the MPU subsystem, use the PM_QOS_CPU_DMA_LATENCY
> class of PM QoS. The resulting MPU constraints are used by cpuidle to
> decide the next power state of the MPU subsystem.
>
> The I2C device latency timing is derived from the FIFO size and the
> clock speed and so is applicable to all OMAP SoCs.
>
> Signed-off-by: Jean Pihet <j-pihet@ti•com>
Acked-by: Kevin Hilman <khilman@ti•com>
next prev parent reply other threads:[~2012-09-25 0:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 16:08 [PATCH] ARM: OMAP: convert I2C driver to PM QoS for MPU latency constraints Jean Pihet
2012-09-21 6:20 ` Shubhrajyoti Datta
2012-09-24 16:29 ` Tony Lindgren
2012-09-25 0:48 ` Kevin Hilman [this message]
2012-10-06 11:46 ` Wolfram Sang
2012-10-08 9:00 ` Jean Pihet
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=878vbzj5bs.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems$(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