linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 4/4] spi: spi-coldfire-qspi: enable RuntimePM before registering to the core
Date: Fri, 09 Oct 2015 18:27:29 +0000	[thread overview]
Message-ID: <20151009182729.GA1544@katana> (raw)
In-Reply-To: <1444383567-18113-4-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1579 bytes --]

On Fri, Oct 09, 2015 at 10:39:27AM +0100, Wolfram Sang wrote:
> From: Wolfram Sang <wsa+renesas@sang-engineering.com>
> 
> The core may register clients attached to this master which may use
> funtionality from the master. So, RuntimePM must be enabled before, otherwise
> this will fail.
> 
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

V2 adds disabling runtime_pm in the error path. There are no
dependencies. Patches 1-3 do the same for I2C drivers. I generated this
series from a branch and sent out as is; probably I should have sent the
SPI one individually.

Thanks,

   Wolfram

> ---
>  drivers/spi/spi-coldfire-qspi.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/spi/spi-coldfire-qspi.c b/drivers/spi/spi-coldfire-qspi.c
> index 688956ff5095c2..23f6fffd75e111 100644
> --- a/drivers/spi/spi-coldfire-qspi.c
> +++ b/drivers/spi/spi-coldfire-qspi.c
> @@ -420,19 +420,20 @@ static int mcfqspi_probe(struct platform_device *pdev)
>  	master->auto_runtime_pm = true;
>  
>  	platform_set_drvdata(pdev, master);
> +	pm_runtime_enable(&pdev->dev);
>  
>  	status = devm_spi_register_master(&pdev->dev, master);
>  	if (status) {
>  		dev_dbg(&pdev->dev, "spi_register_master failed\n");
>  		goto fail2;
>  	}
> -	pm_runtime_enable(&pdev->dev);
>  
>  	dev_info(&pdev->dev, "Coldfire QSPI bus driver\n");
>  
>  	return 0;
>  
>  fail2:
> +	pm_runtime_disable(&pdev->dev);
>  	mcfqspi_cs_teardown(mcfqspi);
>  fail1:
>  	clk_disable(mcfqspi->clk);
> -- 
> 2.1.4
> 

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-10-09 18:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09  9:39 [PATCH v2 1/4] i2c: designware-platdrv: enable RuntimePM before registering to the core Wolfram Sang
2015-10-09  9:39 ` [PATCH v2 2/4] i2c: rcar: " Wolfram Sang
2015-10-15 11:43   ` Wolfram Sang
2015-10-09  9:39 ` [PATCH v2 3/4] i2c: s3c2410: " Wolfram Sang
2015-10-10  6:08   ` Krzysztof Kozlowski
2015-10-10  7:20     ` Wolfram Sang
2015-10-09  9:39 ` [PATCH v2 4/4] spi: spi-coldfire-qspi: " Wolfram Sang
     [not found]   ` <1444383567-18113-4-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-10-09 18:27     ` Wolfram Sang [this message]
2015-10-15 11:49 ` [PATCH v2 1/4] i2c: designware-platdrv: " Wolfram Sang
2015-10-15 12:27   ` Mika Westerberg

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=20151009182729.GA1544@katana \
    --to=wsa@the-dreams.de \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@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 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).