From: Kevin Hilman <khilman@ti.com>
To: jean.pihet@newoldbits.com
Cc: Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
linux-omap@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Paul Walmsley <paul@pwsan.com>,
magnus.damm@gmail.com, Todd Poynor <toddpoynor@google.com>,
Jean Pihet <j-pihet@ti.com>
Subject: Re: [PATCH 1/2] OMAP: convert I2C driver to PM QoS for latency constraints
Date: Wed, 14 Dec 2011 16:17:27 -0800 [thread overview]
Message-ID: <87iplipu20.fsf@ti.com> (raw)
In-Reply-To: <1319034531-22964-2-git-send-email-j-pihet@ti.com> (jean pihet's message of "Wed, 19 Oct 2011 16:28:50 +0200")
jean.pihet@newoldbits.com writes:
> From: Jean Pihet <j-pihet@ti.com>
>
> 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>
Nice.
Acked-by: Kevin Hilman <khilman@ti.com>
I'll queue this with the other I2C changes I've queued once the QoS
series has been merged.
Kevin
next prev parent reply other threads:[~2011-12-15 0:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 14:28 [PATCH 0/2] OMAP: PM: switch from omap_pm_ functions to PM QoS jean.pihet
2011-10-19 14:28 ` [PATCH 1/2] OMAP: convert I2C driver to PM QoS for latency constraints jean.pihet
2011-12-15 0:17 ` Kevin Hilman [this message]
2011-10-19 14:28 ` [PATCH 2/2] OMAP: PM: remove the latency related functions from the API jean.pihet
2011-12-15 0:19 ` Kevin Hilman
2011-12-12 16:27 ` [PATCH 0/2] OMAP: PM: switch from omap_pm_ functions to PM QoS Jean Pihet
2011-12-14 14:57 ` 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=87iplipu20.fsf@ti.com \
--to=khilman@ti.com \
--cc=j-pihet@ti.com \
--cc=jean.pihet@newoldbits.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=magnus.damm@gmail.com \
--cc=paul@pwsan.com \
--cc=rjw@sisk.pl \
--cc=toddpoynor@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.