All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Kuninori Morimoto <morimoto.kuninori@renesas.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	alsa-devel@alsa-project.org, linux-pm@lists.linux-foundation.org,
	Magnus Damm <damm@opensource.se>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2 v2] ASoC: sh: fsi: Add runtime PM	support
Date: Mon, 9 Nov 2009 13:31:36 +0000	[thread overview]
Message-ID: <20091109133136.GC1245@sirena.org.uk> (raw)
In-Reply-To: <20091109105858.GB1245@sirena.org.uk>

On Mon, Nov 09, 2009 at 10:58:58AM +0000, Mark Brown wrote:

Adding in an address for Magnus which hopefully won't bounce and also
the linux-pm list which get_maintainers didn't find.

> On Mon, Nov 09, 2009 at 11:54:47AM +0900, Kuninori Morimoto wrote:
> > This patch add support runtime PM.
> > Driver callbacks for Runtime PM are empty because
> > the device registers are always re-initialized after
> > pm_runtime_get_sync(). The Runtime PM functions replaces the
> > clock framework module stop bit handling in this driver.
> 
> > Signed-off-by: Kuninori Morimoto <morimoto.kuninori@renesas.com>
> 
> Hrm.  I'll have to see how this plays with ASoC core pm_runtime support
> when that appears.  It should be OK as-is, I think.
> 
> > +	pm_suspend_ignore_children(&pdev->dev, true);
> > +	pm_runtime_enable(&pdev->dev);
> > +	pm_runtime_resume(&pdev->dev);
> 
> Why pm_suspend_ignore_all_children()?  I'd not expect the device to have
> any children and if it did it doesn't seem like an entirely safe
> assumption.
> 
> > +static int fsi_runtime_nop(struct device *dev)
> > +{
> > +	/* Runtime PM callback shared between ->runtime_suspend()
> > +	 * and ->runtime_resume(). Simply returns success.
> > +	 *
> > +	 * This driver re-initializes all registers after
> > +	 * pm_runtime_get_sync() anyway so there is no need
> > +	 * to save and restore registers here.
> > +	 */
> > +	return 0;
> > +}
> 
> This sets off alarm bells but it's perfectly reasonable, especially with
> platforms able to put things into a low power state with no explicit
> driver code now they can do power domain style things like SH.  I've
> CCed in the PM folks since this seems like a perfectly reasonable use
> case which ought to be handled more nicely.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

-- 
"You grabbed my hand and we fell into it, like a daydream - or a fever."

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Kuninori Morimoto <morimoto.kuninori@renesas.com>
Cc: alsa-devel@alsa-project.org, Magnus Damm <damm@opensource.se>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-kernel@vger.kernel.org,
	linux-pm@lists.linux-foundation.org
Subject: Re: [alsa-devel] [PATCH 1/2 v2] ASoC: sh: fsi: Add runtime PM support
Date: Mon, 9 Nov 2009 13:31:36 +0000	[thread overview]
Message-ID: <20091109133136.GC1245@sirena.org.uk> (raw)
In-Reply-To: <20091109105858.GB1245@sirena.org.uk>

On Mon, Nov 09, 2009 at 10:58:58AM +0000, Mark Brown wrote:

Adding in an address for Magnus which hopefully won't bounce and also
the linux-pm list which get_maintainers didn't find.

> On Mon, Nov 09, 2009 at 11:54:47AM +0900, Kuninori Morimoto wrote:
> > This patch add support runtime PM.
> > Driver callbacks for Runtime PM are empty because
> > the device registers are always re-initialized after
> > pm_runtime_get_sync(). The Runtime PM functions replaces the
> > clock framework module stop bit handling in this driver.
> 
> > Signed-off-by: Kuninori Morimoto <morimoto.kuninori@renesas.com>
> 
> Hrm.  I'll have to see how this plays with ASoC core pm_runtime support
> when that appears.  It should be OK as-is, I think.
> 
> > +	pm_suspend_ignore_children(&pdev->dev, true);
> > +	pm_runtime_enable(&pdev->dev);
> > +	pm_runtime_resume(&pdev->dev);
> 
> Why pm_suspend_ignore_all_children()?  I'd not expect the device to have
> any children and if it did it doesn't seem like an entirely safe
> assumption.
> 
> > +static int fsi_runtime_nop(struct device *dev)
> > +{
> > +	/* Runtime PM callback shared between ->runtime_suspend()
> > +	 * and ->runtime_resume(). Simply returns success.
> > +	 *
> > +	 * This driver re-initializes all registers after
> > +	 * pm_runtime_get_sync() anyway so there is no need
> > +	 * to save and restore registers here.
> > +	 */
> > +	return 0;
> > +}
> 
> This sets off alarm bells but it's perfectly reasonable, especially with
> platforms able to put things into a low power state with no explicit
> driver code now they can do power domain style things like SH.  I've
> CCed in the PM folks since this seems like a perfectly reasonable use
> case which ought to be handled more nicely.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

-- 
"You grabbed my hand and we fell into it, like a daydream - or a fever."

  reply	other threads:[~2009-11-09 13:31 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09  2:54 [PATCH 1/2 v2] ASoC: sh: fsi: Add runtime PM support Kuninori Morimoto
2009-11-09 10:58 ` Mark Brown
2009-11-09 10:58   ` [alsa-devel] " Mark Brown
2009-11-09 13:31   ` Mark Brown [this message]
2009-11-09 13:31     ` Mark Brown
2009-11-16 15:30     ` Null suspend/resume functions Mark Brown
2009-11-16 15:30       ` Mark Brown
2009-11-16 19:07       ` Rafael J. Wysocki
2009-11-16 19:07       ` Rafael J. Wysocki
2009-11-17 11:52       ` Pavel Machek
2009-11-17 11:52       ` [linux-pm] " Pavel Machek
2009-11-17 11:52         ` Pavel Machek
2009-11-17 12:41         ` Mark Brown
2009-11-17 12:41           ` Mark Brown
2009-11-18 16:09           ` Pavel Machek
2009-11-19 11:21             ` Mark Brown
2009-11-19 11:21               ` Mark Brown
2009-11-21 23:45               ` Pavel Machek
2009-11-23 11:02                 ` Mark Brown
2009-11-24 11:57                   ` Pavel Machek
2009-11-19 11:21             ` Mark Brown
2009-11-18 16:09           ` Pavel Machek
2009-11-17 12:41         ` Mark Brown
2009-11-17 12:46       ` Magnus Damm
2009-11-17 12:46         ` Magnus Damm
2009-11-17 12:59         ` Mark Brown
2009-11-17 12:59           ` Mark Brown
2009-11-17 22:14           ` Rafael J. Wysocki
2009-11-18 13:41             ` Mark Brown
2009-11-18 13:41             ` Mark Brown
2009-11-18 13:41               ` Mark Brown
2009-11-17 22:14           ` Rafael J. Wysocki
2009-11-18 10:09           ` Magnus Damm
2009-11-18 10:09             ` Magnus Damm
2009-11-18 12:05             ` Mark Brown
2009-11-18 12:05             ` Mark Brown
2009-11-18 12:05               ` Mark Brown
2009-11-18 10:09           ` Magnus Damm
2009-11-17 12:59         ` Mark Brown
2009-11-17 12:46       ` Magnus Damm
2009-11-16 15:30     ` Mark Brown
2009-11-09 13:31   ` [alsa-devel] [PATCH 1/2 v2] ASoC: sh: fsi: Add runtime PM support Mark Brown
2009-11-27 11:06   ` Mark Brown
2009-11-27 11:06     ` [alsa-devel] " Mark Brown

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=20091109133136.GC1245@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=damm@opensource.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=morimoto.kuninori@renesas.com \
    --cc=rjw@sisk.pl \
    /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.