From: Chaithrika U S <chaithrika-l0cyMroinI0@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org,
Chaithrika U S <chaithrika-l0cyMroinI0@public.gmane.org>
Subject: [PATCH v3 0/4] i2c: davinci: Add power management features
Date: Wed, 6 Jan 2010 14:54:56 +0530 [thread overview]
Message-ID: <1262769900-2710-1-git-send-email-chaithrika@ti.com> (raw)
Add suspend/resume and cpufreq features to DaVinci I2C driver
All patches apply to Linus' kernel tree.
Testing of these features was done on DA850/OMAP-L138 EVM.
Chaithrika U S (4):
i2c: davinci: Remove MOD_REG_BIT and IO_ADDRESS usage
i2c: davinci: Add helper functions
i2c: davinci: Add suspend/resume support
i2c: davinci: Add cpufreq support
drivers/i2c/busses/i2c-davinci.c | 228 ++++++++++++++++++++++++++++---------
1 files changed, 172 insertions(+), 56 deletions(-)
In this version, the suspend/resume support patch has been updated to
use dev_pm_ops.
next reply other threads:[~2010-01-06 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 9:24 Chaithrika U S [this message]
[not found] ` <1262769900-2710-1-git-send-email-chaithrika-l0cyMroinI0@public.gmane.org>
2010-01-06 9:24 ` [PATCH v2 1/4] i2c: davinci: Remove MOD_REG_BIT and IO_ADDRESS usage Chaithrika U S
[not found] ` <1262769900-2710-2-git-send-email-chaithrika-l0cyMroinI0@public.gmane.org>
2010-01-06 9:24 ` [PATCH v2 2/4] i2c: davinci: Add helper functions Chaithrika U S
[not found] ` <1262769900-2710-3-git-send-email-chaithrika-l0cyMroinI0@public.gmane.org>
2010-01-06 9:24 ` [PATCH v3 3/4] i2c: davinci: Add suspend/resume support Chaithrika U S
2010-01-06 9:25 ` [PATCH v2 4/4] i2c: davinci: Add cpufreq support Chaithrika U S
2010-01-06 15:24 ` [PATCH v3 0/4] i2c: davinci: Add power management features Kevin Hilman
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=1262769900-2710-1-git-send-email-chaithrika@ti.com \
--to=chaithrika-l0cymroini0@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).