From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Mika Westerberg
<mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"Rafael J. Wysocki"
<rafael.j.wysocki-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Lv Zheng <lv.zheng-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Aaron Lu <aaron.lu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [RFC PATCH 1/2] i2c: prepare runtime PM support for I2C client devices
Date: Wed, 28 Aug 2013 11:38:58 +0200 [thread overview]
Message-ID: <20130828093858.GF4086@katana> (raw)
In-Reply-To: <1377007416-13851-2-git-send-email-mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 5379 bytes --]
On Tue, Aug 20, 2013 at 05:03:35PM +0300, Mika Westerberg wrote:
> From: Aaron Lu <aaron.lu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
>
> This patch adds runtime PM support for the I2C bus in a similar way that
> has been done for PCI bus already. This means that the I2C bus core
> prepares runtime PM for a client device just before a driver is about to be
> bound to it. Devices that are not bound to any driver are not prepared for
> runtime PM.
>
> In order to take advantage of this runtime PM support, the client device
> driver needs drop the device runtime PM reference count by calling
> pm_runtime_put() in its ->probe() callback and possibly implement rest of
> the runtime PM callbacks.
>
> However, this does not yet make runtime PM happen for the device, it has to
> be explicitly allowed from userspace per each I2C client device. The
> reason for this is that things like HID over I2C might not work as smoothly
> when runtime PM is active. So we leave it to the user to balance between
> performance and power efficiency.
>
> User can allow runtime PM for the client device by running:
>
> # echo auto > /sys/bus/i2c/devices/<device>/power/control
>
> and it can be forbidden again by:
>
> # echo on > /sys/bus/i2c/devices/<device>/power/control
>
> Status of the device can be monitored by reading files under the device
> power directory.
>
> If the driver doesn't support runtime PM (like most of the existing I2C
> client drivers), the device in question is regarded as being runtime PM
> active and powered on.
>
> The patch adds also runtime PM support for the adapter device because it is
> needed to be able to runtime power manage the I2C controller device. The
> adapter device is handled along with the I2C controller device (it uses
> pm_runtime_no_callbacks()).
>
> Signed-off-by: Aaron Lu <aaron.lu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Signed-off-by: Mika Westerberg <mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
CCing ALKML. Would appreciate comments/tags from the runtime-PM users of
the ARM world.
> ---
> drivers/i2c/i2c-core.c | 48 +++++++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 47 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
> index 3d44292..8fad5ac 100644
> --- a/drivers/i2c/i2c-core.c
> +++ b/drivers/i2c/i2c-core.c
> @@ -254,11 +254,34 @@ static int i2c_device_probe(struct device *dev)
> client->flags & I2C_CLIENT_WAKE);
> dev_dbg(dev, "probe\n");
>
> + /* Make sure the adapter is active */
> + pm_runtime_get_sync(&client->adapter->dev);
> +
> + /*
> + * Enable runtime PM for the client device. If the client wants to
> + * participate on runtime PM it should call pm_runtime_put() in its
> + * probe() callback.
> + *
> + * User still needs to allow the PM runtime before it can actually
> + * happen.
> + */
> + pm_runtime_forbid(&client->dev);
> + pm_runtime_get_noresume(&client->dev);
> + pm_runtime_set_active(&client->dev);
> + pm_runtime_enable(&client->dev);
> +
> status = driver->probe(client, i2c_match_id(driver->id_table, client));
> if (status) {
> client->driver = NULL;
> i2c_set_clientdata(client, NULL);
> +
> + pm_runtime_disable(&client->dev);
> + pm_runtime_set_suspended(&client->dev);
> + pm_runtime_put_noidle(&client->dev);
> }
> +
> + pm_runtime_put(&client->adapter->dev);
> +
> return status;
> }
>
> @@ -271,6 +294,8 @@ static int i2c_device_remove(struct device *dev)
> if (!client || !dev->driver)
> return 0;
>
> + pm_runtime_get_sync(&client->adapter->dev);
> +
> driver = to_i2c_driver(dev->driver);
> if (driver->remove) {
> dev_dbg(dev, "remove\n");
> @@ -283,6 +308,13 @@ static int i2c_device_remove(struct device *dev)
> client->driver = NULL;
> i2c_set_clientdata(client, NULL);
> }
> +
> + /* Undo the runtime PM done in i2c_probe() */
> + pm_runtime_disable(&client->dev);
> + pm_runtime_set_suspended(&client->dev);
> + pm_runtime_put_noidle(&client->dev);
> +
> + pm_runtime_put(&client->adapter->dev);
> return status;
> }
>
> @@ -294,8 +326,11 @@ static void i2c_device_shutdown(struct device *dev)
> if (!client || !dev->driver)
> return;
> driver = to_i2c_driver(dev->driver);
> - if (driver->shutdown)
> + if (driver->shutdown) {
> + pm_runtime_get_sync(&client->adapter->dev);
> driver->shutdown(client);
> + pm_runtime_put(&client->adapter->dev);
> + }
> }
>
> #ifdef CONFIG_PM_SLEEP
> @@ -1263,6 +1298,15 @@ exit_recovery:
> bus_for_each_drv(&i2c_bus_type, NULL, adap, __process_new_adapter);
> mutex_unlock(&core_lock);
>
> + /*
> + * Make sure the adapter runtime PM follows the parent device (the
> + * host controller) so that we can suspend it once there aren't any
> + * active clients anymore.
> + */
> + pm_runtime_set_active(&adap->dev);
> + pm_runtime_no_callbacks(&adap->dev);
> + pm_runtime_enable(&adap->dev);
> +
> return 0;
>
> out_list:
> @@ -1427,6 +1471,8 @@ void i2c_del_adapter(struct i2c_adapter *adap)
> return;
> }
>
> + pm_runtime_disable(&adap->dev);
> +
> /* Tell drivers about this removal */
> mutex_lock(&core_lock);
> bus_for_each_drv(&i2c_bus_type, NULL, adap,
> --
> 1.8.4.rc2
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/2] i2c: prepare runtime PM support for I2C client devices
Date: Wed, 28 Aug 2013 11:38:58 +0200 [thread overview]
Message-ID: <20130828093858.GF4086@katana> (raw)
In-Reply-To: <1377007416-13851-2-git-send-email-mika.westerberg@linux.intel.com>
On Tue, Aug 20, 2013 at 05:03:35PM +0300, Mika Westerberg wrote:
> From: Aaron Lu <aaron.lu@intel.com>
>
> This patch adds runtime PM support for the I2C bus in a similar way that
> has been done for PCI bus already. This means that the I2C bus core
> prepares runtime PM for a client device just before a driver is about to be
> bound to it. Devices that are not bound to any driver are not prepared for
> runtime PM.
>
> In order to take advantage of this runtime PM support, the client device
> driver needs drop the device runtime PM reference count by calling
> pm_runtime_put() in its ->probe() callback and possibly implement rest of
> the runtime PM callbacks.
>
> However, this does not yet make runtime PM happen for the device, it has to
> be explicitly allowed from userspace per each I2C client device. The
> reason for this is that things like HID over I2C might not work as smoothly
> when runtime PM is active. So we leave it to the user to balance between
> performance and power efficiency.
>
> User can allow runtime PM for the client device by running:
>
> # echo auto > /sys/bus/i2c/devices/<device>/power/control
>
> and it can be forbidden again by:
>
> # echo on > /sys/bus/i2c/devices/<device>/power/control
>
> Status of the device can be monitored by reading files under the device
> power directory.
>
> If the driver doesn't support runtime PM (like most of the existing I2C
> client drivers), the device in question is regarded as being runtime PM
> active and powered on.
>
> The patch adds also runtime PM support for the adapter device because it is
> needed to be able to runtime power manage the I2C controller device. The
> adapter device is handled along with the I2C controller device (it uses
> pm_runtime_no_callbacks()).
>
> Signed-off-by: Aaron Lu <aaron.lu@intel.com>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
CCing ALKML. Would appreciate comments/tags from the runtime-PM users of
the ARM world.
> ---
> drivers/i2c/i2c-core.c | 48 +++++++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 47 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
> index 3d44292..8fad5ac 100644
> --- a/drivers/i2c/i2c-core.c
> +++ b/drivers/i2c/i2c-core.c
> @@ -254,11 +254,34 @@ static int i2c_device_probe(struct device *dev)
> client->flags & I2C_CLIENT_WAKE);
> dev_dbg(dev, "probe\n");
>
> + /* Make sure the adapter is active */
> + pm_runtime_get_sync(&client->adapter->dev);
> +
> + /*
> + * Enable runtime PM for the client device. If the client wants to
> + * participate on runtime PM it should call pm_runtime_put() in its
> + * probe() callback.
> + *
> + * User still needs to allow the PM runtime before it can actually
> + * happen.
> + */
> + pm_runtime_forbid(&client->dev);
> + pm_runtime_get_noresume(&client->dev);
> + pm_runtime_set_active(&client->dev);
> + pm_runtime_enable(&client->dev);
> +
> status = driver->probe(client, i2c_match_id(driver->id_table, client));
> if (status) {
> client->driver = NULL;
> i2c_set_clientdata(client, NULL);
> +
> + pm_runtime_disable(&client->dev);
> + pm_runtime_set_suspended(&client->dev);
> + pm_runtime_put_noidle(&client->dev);
> }
> +
> + pm_runtime_put(&client->adapter->dev);
> +
> return status;
> }
>
> @@ -271,6 +294,8 @@ static int i2c_device_remove(struct device *dev)
> if (!client || !dev->driver)
> return 0;
>
> + pm_runtime_get_sync(&client->adapter->dev);
> +
> driver = to_i2c_driver(dev->driver);
> if (driver->remove) {
> dev_dbg(dev, "remove\n");
> @@ -283,6 +308,13 @@ static int i2c_device_remove(struct device *dev)
> client->driver = NULL;
> i2c_set_clientdata(client, NULL);
> }
> +
> + /* Undo the runtime PM done in i2c_probe() */
> + pm_runtime_disable(&client->dev);
> + pm_runtime_set_suspended(&client->dev);
> + pm_runtime_put_noidle(&client->dev);
> +
> + pm_runtime_put(&client->adapter->dev);
> return status;
> }
>
> @@ -294,8 +326,11 @@ static void i2c_device_shutdown(struct device *dev)
> if (!client || !dev->driver)
> return;
> driver = to_i2c_driver(dev->driver);
> - if (driver->shutdown)
> + if (driver->shutdown) {
> + pm_runtime_get_sync(&client->adapter->dev);
> driver->shutdown(client);
> + pm_runtime_put(&client->adapter->dev);
> + }
> }
>
> #ifdef CONFIG_PM_SLEEP
> @@ -1263,6 +1298,15 @@ exit_recovery:
> bus_for_each_drv(&i2c_bus_type, NULL, adap, __process_new_adapter);
> mutex_unlock(&core_lock);
>
> + /*
> + * Make sure the adapter runtime PM follows the parent device (the
> + * host controller) so that we can suspend it once there aren't any
> + * active clients anymore.
> + */
> + pm_runtime_set_active(&adap->dev);
> + pm_runtime_no_callbacks(&adap->dev);
> + pm_runtime_enable(&adap->dev);
> +
> return 0;
>
> out_list:
> @@ -1427,6 +1471,8 @@ void i2c_del_adapter(struct i2c_adapter *adap)
> return;
> }
>
> + pm_runtime_disable(&adap->dev);
> +
> /* Tell drivers about this removal */
> mutex_lock(&core_lock);
> bus_for_each_drv(&i2c_bus_type, NULL, adap,
> --
> 1.8.4.rc2
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130828/1864a4f7/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-i2c@vger.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Lv Zheng <lv.zheng@intel.com>, Aaron Lu <aaron.lu@intel.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 1/2] i2c: prepare runtime PM support for I2C client devices
Date: Wed, 28 Aug 2013 11:38:58 +0200 [thread overview]
Message-ID: <20130828093858.GF4086@katana> (raw)
In-Reply-To: <1377007416-13851-2-git-send-email-mika.westerberg@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 5295 bytes --]
On Tue, Aug 20, 2013 at 05:03:35PM +0300, Mika Westerberg wrote:
> From: Aaron Lu <aaron.lu@intel.com>
>
> This patch adds runtime PM support for the I2C bus in a similar way that
> has been done for PCI bus already. This means that the I2C bus core
> prepares runtime PM for a client device just before a driver is about to be
> bound to it. Devices that are not bound to any driver are not prepared for
> runtime PM.
>
> In order to take advantage of this runtime PM support, the client device
> driver needs drop the device runtime PM reference count by calling
> pm_runtime_put() in its ->probe() callback and possibly implement rest of
> the runtime PM callbacks.
>
> However, this does not yet make runtime PM happen for the device, it has to
> be explicitly allowed from userspace per each I2C client device. The
> reason for this is that things like HID over I2C might not work as smoothly
> when runtime PM is active. So we leave it to the user to balance between
> performance and power efficiency.
>
> User can allow runtime PM for the client device by running:
>
> # echo auto > /sys/bus/i2c/devices/<device>/power/control
>
> and it can be forbidden again by:
>
> # echo on > /sys/bus/i2c/devices/<device>/power/control
>
> Status of the device can be monitored by reading files under the device
> power directory.
>
> If the driver doesn't support runtime PM (like most of the existing I2C
> client drivers), the device in question is regarded as being runtime PM
> active and powered on.
>
> The patch adds also runtime PM support for the adapter device because it is
> needed to be able to runtime power manage the I2C controller device. The
> adapter device is handled along with the I2C controller device (it uses
> pm_runtime_no_callbacks()).
>
> Signed-off-by: Aaron Lu <aaron.lu@intel.com>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
CCing ALKML. Would appreciate comments/tags from the runtime-PM users of
the ARM world.
> ---
> drivers/i2c/i2c-core.c | 48 +++++++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 47 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
> index 3d44292..8fad5ac 100644
> --- a/drivers/i2c/i2c-core.c
> +++ b/drivers/i2c/i2c-core.c
> @@ -254,11 +254,34 @@ static int i2c_device_probe(struct device *dev)
> client->flags & I2C_CLIENT_WAKE);
> dev_dbg(dev, "probe\n");
>
> + /* Make sure the adapter is active */
> + pm_runtime_get_sync(&client->adapter->dev);
> +
> + /*
> + * Enable runtime PM for the client device. If the client wants to
> + * participate on runtime PM it should call pm_runtime_put() in its
> + * probe() callback.
> + *
> + * User still needs to allow the PM runtime before it can actually
> + * happen.
> + */
> + pm_runtime_forbid(&client->dev);
> + pm_runtime_get_noresume(&client->dev);
> + pm_runtime_set_active(&client->dev);
> + pm_runtime_enable(&client->dev);
> +
> status = driver->probe(client, i2c_match_id(driver->id_table, client));
> if (status) {
> client->driver = NULL;
> i2c_set_clientdata(client, NULL);
> +
> + pm_runtime_disable(&client->dev);
> + pm_runtime_set_suspended(&client->dev);
> + pm_runtime_put_noidle(&client->dev);
> }
> +
> + pm_runtime_put(&client->adapter->dev);
> +
> return status;
> }
>
> @@ -271,6 +294,8 @@ static int i2c_device_remove(struct device *dev)
> if (!client || !dev->driver)
> return 0;
>
> + pm_runtime_get_sync(&client->adapter->dev);
> +
> driver = to_i2c_driver(dev->driver);
> if (driver->remove) {
> dev_dbg(dev, "remove\n");
> @@ -283,6 +308,13 @@ static int i2c_device_remove(struct device *dev)
> client->driver = NULL;
> i2c_set_clientdata(client, NULL);
> }
> +
> + /* Undo the runtime PM done in i2c_probe() */
> + pm_runtime_disable(&client->dev);
> + pm_runtime_set_suspended(&client->dev);
> + pm_runtime_put_noidle(&client->dev);
> +
> + pm_runtime_put(&client->adapter->dev);
> return status;
> }
>
> @@ -294,8 +326,11 @@ static void i2c_device_shutdown(struct device *dev)
> if (!client || !dev->driver)
> return;
> driver = to_i2c_driver(dev->driver);
> - if (driver->shutdown)
> + if (driver->shutdown) {
> + pm_runtime_get_sync(&client->adapter->dev);
> driver->shutdown(client);
> + pm_runtime_put(&client->adapter->dev);
> + }
> }
>
> #ifdef CONFIG_PM_SLEEP
> @@ -1263,6 +1298,15 @@ exit_recovery:
> bus_for_each_drv(&i2c_bus_type, NULL, adap, __process_new_adapter);
> mutex_unlock(&core_lock);
>
> + /*
> + * Make sure the adapter runtime PM follows the parent device (the
> + * host controller) so that we can suspend it once there aren't any
> + * active clients anymore.
> + */
> + pm_runtime_set_active(&adap->dev);
> + pm_runtime_no_callbacks(&adap->dev);
> + pm_runtime_enable(&adap->dev);
> +
> return 0;
>
> out_list:
> @@ -1427,6 +1471,8 @@ void i2c_del_adapter(struct i2c_adapter *adap)
> return;
> }
>
> + pm_runtime_disable(&adap->dev);
> +
> /* Tell drivers about this removal */
> mutex_lock(&core_lock);
> bus_for_each_drv(&i2c_bus_type, NULL, adap,
> --
> 1.8.4.rc2
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-28 9:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 14:03 [RFC PATCH 0/2] runtime PM support for I2C clients Mika Westerberg
2013-08-20 14:03 ` Mika Westerberg
2013-08-20 14:03 ` [RFC PATCH 1/2] i2c: prepare runtime PM support for I2C client devices Mika Westerberg
2013-08-20 14:16 ` Rafael J. Wysocki
[not found] ` <1377007416-13851-2-git-send-email-mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2013-08-28 9:38 ` Wolfram Sang [this message]
2013-08-28 9:38 ` Wolfram Sang
2013-08-28 9:38 ` Wolfram Sang
2013-09-02 10:56 ` Mika Westerberg
2013-08-20 14:03 ` [RFC PATCH 2/2] i2c: attach/detach I2C client device to the ACPI power domain Mika Westerberg
2013-08-20 14:16 ` Rafael J. Wysocki
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=20130828093858.GF4086@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=aaron.lu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lv.zheng-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=rafael.j.wysocki-ral2JQCrhuEAvxtiuMwx3w@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 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.