From: Daniel Baluta <daniel.baluta@intel.com>
To: jic23@kernel.org, srinivas.pandruvada@linux.intel.com
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
daniel.baluta@intel.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/2] Introduce PM runtime helper functions
Date: Mon, 18 May 2015 19:25:26 +0300 [thread overview]
Message-ID: <1431966328-11058-1-git-send-email-daniel.baluta@intel.com> (raw)
Working on a new driver I noticed that there is a fair amount of duplicate
code for adding PM runtime support.
First patch refactors the PM runtime support in a new header
<linux/iio/pm_runtime> introducing functions for setup/cleanup and
set power state.
Second patch modifies the KXCJK-1013 driver to use the newly created API. If
this is ok follow up patches will modify the rest of the drivers.
There is a small difference for hid-sensors where the setup sequence additionally
calls pm_suspend_ignore_children. This is taken care of by introducing a 3rd
parameter to iio_pm_runtime_setup.
Daniel Baluta (2):
iio: pm_runtime: Introduce PM runtime helper functions
iio: accel: kxcjk1013: Use the new IIO pm runtime helpers
drivers/iio/accel/kxcjk-1013.c | 56 ++++++++++---------------------------
include/linux/iio/pm_runtime.h | 63 ++++++++++++++++++++++++++++++++++++++++++
2 files changed, 77 insertions(+), 42 deletions(-)
create mode 100644 include/linux/iio/pm_runtime.h
--
1.9.1
next reply other threads:[~2015-05-18 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 16:25 Daniel Baluta [this message]
2015-05-18 16:25 ` [RFC PATCH 1/2] iio: pm_runtime: Introduce PM runtime helper functions Daniel Baluta
2015-05-18 17:34 ` Peter Meerwald
2015-05-18 18:24 ` Daniel Baluta
2015-05-18 16:25 ` [RFC PATCH 2/2] iio: accel: kxcjk1013: Use the new IIO pm runtime helpers Daniel Baluta
2015-05-18 16:54 ` [RFC PATCH 0/2] Introduce PM runtime helper functions Lars-Peter Clausen
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=1431966328-11058-1-git-send-email-daniel.baluta@intel.com \
--to=daniel.baluta@intel.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=srinivas.pandruvada@linux.intel.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;
as well as URLs for NNTP newsgroup(s).