linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Bibby Hsieh <bibby.hsieh@mediatek.com>,
	Wolfram Sang <wsa@the-dreams.de>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	<linux-i2c@vger.kernel.org>
Cc: <tfiga@chromium.org>, <drinkcat@chromium.org>,
	<srv_heupstream@mediatek.com>, <robh+dt@kernel.org>,
	<mark.rutland@arm.com>, <devicetree@vger.kernel.org>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v14 2/2] i2c: core: support bus regulator controlling in adapter
Date: Tue, 28 Apr 2020 14:25:05 +0300	[thread overview]
Message-ID: <e3583893-f49d-0e78-6414-ed565099af63@ti.com> (raw)
In-Reply-To: <20200428061813.27072-3-bibby.hsieh@mediatek.com>



On 28/04/2020 09:18, Bibby Hsieh wrote:
> Although in the most platforms, the bus power of i2c
> are alway on, some platforms disable the i2c bus power
> in order to meet low power request.
> 
> We get and enable bulk regulator in i2c adapter device.
> 
> Signed-off-by: Bibby Hsieh <bibby.hsieh@mediatek.com>
> ---
>   drivers/i2c/i2c-core-base.c | 82 +++++++++++++++++++++++++++++++++++++
>   include/linux/i2c.h         |  2 +
>   2 files changed, 84 insertions(+)
> 
> diff --git a/drivers/i2c/i2c-core-base.c b/drivers/i2c/i2c-core-base.c
> index 5cc0b0ec5570..f81b42a4ed07 100644
> --- a/drivers/i2c/i2c-core-base.c
> +++ b/drivers/i2c/i2c-core-base.c
> @@ -313,6 +313,7 @@ static int i2c_smbus_host_notify_to_irq(const struct i2c_client *client)
>   static int i2c_device_probe(struct device *dev)
>   {
>   	struct i2c_client	*client = i2c_verify_client(dev);
> +	struct i2c_adapter	*adap = client->adapter;
>   	struct i2c_driver	*driver;
>   	int status;
>   
> @@ -378,6 +379,12 @@ static int i2c_device_probe(struct device *dev)
>   
>   	dev_dbg(dev, "probe\n");
>   
> +	status = regulator_enable(adap->bus_regulator);
> +	if (status < 0) {
> +		dev_err(&adap->dev, "Failed to enable power regulator\n");
> +		goto err_clear_wakeup_irq;
> +	}
> +

Sry, but this is confusing.
What if there is separate regulators for I2C device and bus/adapter?

I2C bus is transaction based and usually I2C bus drivers ensures that i2c bus is
in proper state to perform transaction. While I2C devices can be enable, configured and
function without actually interacting with I2C bus unless required (irq for example).

With you change any I2C device will enable and keep bus regulator on all the time it's active
even if there is no I2C interruptions.

Following the problem description it seems
  - i2c bus driver should get regulator and ensure it's enabled for the duration of transaction(s)
  - i2c device should get its own regulator (or the same if shared)  ensure it's enabled for
    the period device is active.


>   	status = of_clk_set_defaults(dev->of_node, false);
>   	if (status < 0)
>   		goto err_clear_wakeup_irq;
> @@ -414,6 +421,7 @@ static int i2c_device_probe(struct device *dev)
>   static int i2c_device_remove(struct device *dev)
>   {
>   	struct i2c_client	*client = i2c_verify_client(dev);
> +	struct i2c_adapter      *adap = client->adapter;
>   	struct i2c_driver	*driver;
>   	int status = 0;
>   
> @@ -427,6 +435,8 @@ static int i2c_device_remove(struct device *dev)
>   	}
>   
>   	dev_pm_domain_detach(&client->dev, true);
> +	if (!pm_runtime_status_suspended(&client->dev))
> +		regulator_disable(adap->bus_regulator);
>   
>   	dev_pm_clear_wake_irq(&client->dev);
>   	device_init_wakeup(&client->dev, false);
> @@ -438,6 +448,72 @@ static int i2c_device_remove(struct device *dev)
>   	return status;
>   }
>   
> +#ifdef CONFIG_PM_SLEEP
> +static int i2c_resume_early(struct device *dev)
> +{
> +	struct i2c_client *client = i2c_verify_client(dev);
> +	struct i2c_adapter *adap = client->adapter;
> +	int err;
> +
> +	if (!pm_runtime_status_suspended(&client->dev)) {
> +		err = regulator_enable(adap->bus_regulator);
> +		if (err)
> +			return err;
> +	}
> +
> +	return pm_generic_resume_early(&client->dev);
> +}
> +
> +static int i2c_suspend_late(struct device *dev)
> +{
> +	struct i2c_client *client = i2c_verify_client(dev);
> +	struct i2c_adapter *adap = client->adapter;
> +	int err;
> +
> +	err = pm_generic_suspend_late(&client->dev);
> +	if (err)
> +		return err;
> +
> +	if (!pm_runtime_status_suspended(&client->dev))
> +		return regulator_disable(adap->bus_regulator);
> +
> +	return err;
> +}
> +#endif

Have you considered pm_runtime_force_suspend/pm_runtime_force_resume?

> +
> +#ifdef CONFIG_PM
> +static int i2c_runtime_resume(struct device *dev)
> +{
> +	struct i2c_client *client = i2c_verify_client(dev);
> +	struct i2c_adapter *adap = client->adapter;
> +	int err;
> +
> +	err = regulator_enable(adap->bus_regulator);
> +	if (err)
> +		return err;
> +
> +	return pm_generic_runtime_resume(&client->dev);
> +}
> +
> +static int i2c_runtime_suspend(struct device *dev)
> +{
> +	struct i2c_client *client = i2c_verify_client(dev);
> +	struct i2c_adapter *adap = client->adapter;
> +	int err;
> +
> +	err = pm_generic_runtime_suspend(&client->dev);
> +	if (err)
> +		return err;
> +
> +	return regulator_disable(adap->bus_regulator);
> +}
> +#endif
> +
> +static const struct dev_pm_ops i2c_device_pm = {
> +	SET_LATE_SYSTEM_SLEEP_PM_OPS(i2c_suspend_late, i2c_resume_early)
> +	SET_RUNTIME_PM_OPS(i2c_runtime_suspend, i2c_runtime_resume, NULL)
> +};
> +
>   static void i2c_device_shutdown(struct device *dev)
>   {
>   	struct i2c_client *client = i2c_verify_client(dev);
> @@ -495,6 +571,7 @@ struct bus_type i2c_bus_type = {
>   	.probe		= i2c_device_probe,
>   	.remove		= i2c_device_remove,
>   	.shutdown	= i2c_device_shutdown,
> +	.pm		= &i2c_device_pm,
>   };
>   EXPORT_SYMBOL_GPL(i2c_bus_type);
>   
> @@ -1333,6 +1410,11 @@ static int i2c_register_adapter(struct i2c_adapter *adap)
>   	if (res)
>   		goto out_reg;
>   
> +	adap->bus_regulator = devm_regulator_get(&adap->dev, "bus");
> +	if (IS_ERR(adap->bus_regulator)) {
> +		res = PTR_ERR(adap->bus_regulator);
> +		goto out_reg;
> +	}
>   	dev_dbg(&adap->dev, "adapter [%s] registered\n", adap->name);
>   
>   	pm_runtime_no_callbacks(&adap->dev);
> diff --git a/include/linux/i2c.h b/include/linux/i2c.h
> index 456fc17ecb1c..bc83af0d38d1 100644
> --- a/include/linux/i2c.h
> +++ b/include/linux/i2c.h
> @@ -15,6 +15,7 @@
>   #include <linux/device.h>	/* for struct device */
>   #include <linux/sched.h>	/* for completion */
>   #include <linux/mutex.h>
> +#include <linux/regulator/consumer.h>
>   #include <linux/rtmutex.h>
>   #include <linux/irqdomain.h>		/* for Host Notify IRQ */
>   #include <linux/of.h>		/* for struct device_node */
> @@ -721,6 +722,7 @@ struct i2c_adapter {
>   	const struct i2c_adapter_quirks *quirks;
>   
>   	struct irq_domain *host_notify_domain;
> +	struct regulator *bus_regulator;
>   };
>   #define to_i2c_adapter(d) container_of(d, struct i2c_adapter, dev)
>   
> 

-- 
Best regards,
grygorii

  reply	other threads:[~2020-04-28 11:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28  6:18 [PATCH v14 0/2] add power control in i2c Bibby Hsieh
2020-04-28  6:18 ` [PATCH v14 1/2] dt-binding: i2c: add bus-supply property Bibby Hsieh
2020-04-28 15:02   ` Rob Herring
2020-05-19  6:53   ` Wolfram Sang
2020-05-19  7:00     ` Wolfram Sang
2020-04-28  6:18 ` [PATCH v14 2/2] i2c: core: support bus regulator controlling in adapter Bibby Hsieh
2020-04-28 11:25   ` Grygorii Strashko [this message]
2020-04-28 11:44     ` Tomasz Figa
2020-04-28 12:15       ` Grygorii Strashko
2020-04-28 11:45   ` Tomasz Figa
2020-05-19  6:59   ` Wolfram Sang
2020-05-19  7:26     ` Bibby Hsieh

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=e3583893-f49d-0e78-6414-ed565099af63@ti.com \
    --to=grygorii.strashko@ti.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=bibby.hsieh@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=drinkcat@chromium.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=robh+dt@kernel.org \
    --cc=srv_heupstream@mediatek.com \
    --cc=tfiga@chromium.org \
    --cc=wsa@the-dreams.de \
    /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).