Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: wsa@the-dreams.de, kgene@kernel.org,
	linux-samsung-soc@vger.kernel.org, linux-i2c@vger.kernel.org,
	lars@metafoo.de
Subject: Re: [PATCH] i2c: s3c2410: Don't enable PM runtime on the adapter device
Date: Thu, 16 Apr 2015 12:33:08 +0200	[thread overview]
Message-ID: <552F8FE4.7040905@samsung.com> (raw)
In-Reply-To: <1429179025-5352-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>

On 16/04/15 12:10, Charles Keepax wrote:
> Commit 523c5b89640e ("i2c: Remove support for legacy PM") removed the PM
> ops from the bus type, which causes the pm operations on the s3c2410
> adapter device to fail (-ENOSUPP in rpm_callback). The adapter device
> doesn't get bound to a driver and as such can't have its own pm_runtime
> callbacks. Previously this was fine as the bus callbacks would have been
> used, but now this can cause devices which use PM runtime and are
> attached over I2C to fail to resume.
> 
> This commit fixes this issue by just doing the PM operations directly on
> the I2C device, rather than the adapter device in the driver and adding
> some stub callbacks for runtime suspend and resume.
> 
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
>  drivers/i2c/busses/i2c-s3c2410.c |   21 ++++++++++++++++-----
>  1 files changed, 16 insertions(+), 5 deletions(-)

> @@ -1253,7 +1253,6 @@ static int s3c24xx_i2c_probe(struct platform_device *pdev)
>  	platform_set_drvdata(pdev, i2c);
>  

Wouldn't adding

	pm_runtime_no_callbacks(&pdev->dev);

here let us avoid the runtime resume/suspend stubs?

>  	pm_runtime_enable(&pdev->dev);
> -	pm_runtime_enable(&i2c->adap.dev);
>  
>  	dev_info(&pdev->dev, "%s: S3C I2C adapter\n", dev_name(&i2c->adap.dev));
>  	return 0;
> @@ -1270,7 +1269,6 @@ static int s3c24xx_i2c_remove(struct platform_device *pdev)
>  
>  	clk_unprepare(i2c->clk);
>  
> -	pm_runtime_disable(&i2c->adap.dev);
>  	pm_runtime_disable(&pdev->dev);
>  
>  	s3c24xx_i2c_deregister_cpufreq(i2c);
> @@ -1318,6 +1316,16 @@ static int s3c24xx_i2c_resume_noirq(struct device *dev)
>  #endif
>  
>  #ifdef CONFIG_PM
> +static int s3c24xx_runtime_resume(struct device *dev)
> +{
> +	return 0;
> +}
> +
> +static int s3c24xx_runtime_suspend(struct device *dev)
> +{
> +	return 0;
> +}

--
Thanks,
Sylwester

  reply	other threads:[~2015-04-16 10:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 10:10 [PATCH] i2c: s3c2410: Don't enable PM runtime on the adapter device Charles Keepax
2015-04-16 10:33 ` Sylwester Nawrocki [this message]
     [not found]   ` <552F8FE4.7040905-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-04-16 10:39     ` Lars-Peter Clausen
     [not found]       ` <552F916F.6070700-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
2015-04-16 10:48         ` Charles Keepax

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=552F8FE4.7040905@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=kgene@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.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