devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: devicetree@vger.kernel.org, "Dave Gerlach" <d-gerlach@ti.com>,
	Keerthy <j-keerthy@ti.com>, "Tero Kristo" <t-kristo@ti.com>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/4] Update am437x and am335x dts to probe with ti-sysc
Date: Wed, 26 Sep 2018 16:31:11 -0700	[thread overview]
Message-ID: <20180926233111.GY5662@atomide.com> (raw)
In-Reply-To: <cfc3f1db-9468-ed92-a673-882b51b4dec8@ti.com>

* Grygorii Strashko <grygorii.strashko@ti.com> [180926 21:41]:
> On 09/26/2018 11:23 AM, Tony Lindgren wrote:
> > +static int __maybe_unused omap_i2c_suspend(struct device *dev)
> > +{
> > +	struct omap_i2c_dev *ddata = dev_get_drvdata(dev);
> > +	int error;
> > +
> > +	/* Is device still enabled because of autosuspend? */
> > +	if (ddata->is_suspended)
> > +		return 0;
> 
> Sry, but you can't do this. There is no sync between suspend and PM runtime.
> 
> 
> > +
> > +	/* Paired with call in omap_i2c_resume() */
> > +	error = pm_runtime_put_sync_suspend(dev);
> 
> This is nop!!! More over, in general you can't predict how many times pm_runtime_get was called and
> what's the current value of usage_count.

Hmm yeah that's a good point.

> To make things work the pm_runtime_force_xx() have to be used, or
> like with omap_device, platform/bus code have to handle device state
> at suspend_no_irq stage.

OK. So looks like the other i2c bus drivers have already solved it
with simply SET_NOIRQ_SYSTEM_SLEEP_PM_OPS which is along the lines
you're suggesting.

The following works for me, does it look OK to you?

Regards,

Tony

8< ---------------------
diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
--- a/drivers/i2c/busses/i2c-omap.c
+++ b/drivers/i2c/busses/i2c-omap.c
@@ -1498,8 +1498,7 @@ static int omap_i2c_remove(struct platform_device *pdev)
 	return 0;
 }
 
-#ifdef CONFIG_PM
-static int omap_i2c_runtime_suspend(struct device *dev)
+static int __maybe_unused omap_i2c_runtime_suspend(struct device *dev)
 {
 	struct omap_i2c_dev *omap = dev_get_drvdata(dev);
 
@@ -1525,7 +1524,7 @@ static int omap_i2c_runtime_suspend(struct device *dev)
 	return 0;
 }
 
-static int omap_i2c_runtime_resume(struct device *dev)
+static int __maybe_unused omap_i2c_runtime_resume(struct device *dev)
 {
 	struct omap_i2c_dev *omap = dev_get_drvdata(dev);
 
@@ -1540,20 +1539,18 @@ static int omap_i2c_runtime_resume(struct device *dev)
 }
 
 static const struct dev_pm_ops omap_i2c_pm_ops = {
+	SET_NOIRQ_SYSTEM_SLEEP_PM_OPS(pm_runtime_force_suspend,
+				      pm_runtime_force_resume)
 	SET_RUNTIME_PM_OPS(omap_i2c_runtime_suspend,
 			   omap_i2c_runtime_resume, NULL)
 };
-#define OMAP_I2C_PM_OPS (&omap_i2c_pm_ops)
-#else
-#define OMAP_I2C_PM_OPS NULL
-#endif /* CONFIG_PM */
 
 static struct platform_driver omap_i2c_driver = {
 	.probe		= omap_i2c_probe,
 	.remove		= omap_i2c_remove,
 	.driver		= {
 		.name	= "omap_i2c",
-		.pm	= OMAP_I2C_PM_OPS,
+		.pm	= &omap_i2c_pm_ops,
 		.of_match_table = of_match_ptr(omap_i2c_of_match),
 	},
 };
-- 
2.19.0

  reply	other threads:[~2018-09-26 23:31 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25  0:05 [PATCH 0/4] Update am437x and am335x dts to probe with ti-sysc Tony Lindgren
2018-09-25  0:05 ` [PATCH 1/4] ARM: dts: am437x: Add l4 interconnect hierarchy and ti-sysc data Tony Lindgren
2018-09-25  0:05 ` [PATCH 2/4] ARM: dts: am437x: Move l4 child devices to probe them with ti-sysc Tony Lindgren
2018-12-04 12:23   ` Peter Ujfalusi
2018-12-04 18:11     ` Tony Lindgren
2018-12-04 23:18       ` Tony Lindgren
2018-12-05  6:14         ` Peter Ujfalusi
2018-12-05 19:00           ` Tony Lindgren
2018-12-05 23:02             ` Tony Lindgren
2018-12-07 12:46               ` Peter Ujfalusi
2018-09-25  0:05 ` [PATCH 3/4] ARM: dts: am335x: Add l4 interconnect hierarchy and ti-sysc data Tony Lindgren
2018-09-27 14:56   ` Tony Lindgren
2018-09-25  0:05 ` [PATCH 4/4] ARM: dts: am335x: Move l4 child devices to probe them with ti-sysc Tony Lindgren
2018-11-27 13:03   ` Peter Ujfalusi
2018-11-27 16:16     ` Tony Lindgren
2018-11-28 12:52       ` Peter Ujfalusi
2018-11-29 19:07         ` Tony Lindgren
2018-09-25  5:14 ` [PATCH 0/4] Update am437x and am335x dts to probe " Keerthy
2018-09-25 14:40   ` Tony Lindgren
2018-09-25 17:55     ` Tony Lindgren
2018-09-25 21:16       ` Grygorii Strashko
2018-09-26  4:08       ` Keerthy
2018-09-26 15:59         ` Tony Lindgren
2018-09-26 16:23           ` Tony Lindgren
2018-09-26 21:36             ` Grygorii Strashko
2018-09-26 23:31               ` Tony Lindgren [this message]
2018-09-27  4:55                 ` Keerthy
2018-09-27 14:53                   ` Tony Lindgren
2018-09-27 21:43                     ` Tony Lindgren
2018-10-01 16:32                   ` Tony Lindgren
2018-10-04  4:29                     ` Keerthy
2018-10-04 14:23                       ` Tony Lindgren
2018-09-27 19:11                 ` Grygorii Strashko
2018-09-27 19:38                   ` Tony Lindgren

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=20180926233111.GY5662@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=d-gerlach@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grygorii.strashko@ti.com \
    --cc=j-keerthy@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=t-kristo@ti.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).