From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Kuninori Morimoto <morimoto.kuninori@renesas.com>,
alsa-devel@alsa-project.org, linux-pm@lists.linux-foundation.org,
Magnus Damm <damm@opensource.se>,
linux-kernel@vger.kernel.org
Subject: Re: Null suspend/resume functions
Date: Tue, 17 Nov 2009 12:59:01 +0000 [thread overview]
Message-ID: <20091117125901.GF823@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <aec7e5c30911170446n71031671i48aca11f5276405d@mail.gmail.com>
On Tue, Nov 17, 2009 at 09:46:35PM +0900, Magnus Damm wrote:
> On SuperH we have Runtime PM enabled on a few platforms together with
> a few updated drivers. The latest driver to become more power aware is
> this FSI driver.
I understand exactly what the runtime PM stuff and the driver are doing
here, the issue is the mandatory suspend and resume functions.
> At this point the SuperH specific platform bus code requires the
> callbacks ->runtime_suspend() and ->runtime_resume() to be present. It
> may be a good idea to allow them to be NULL in the future or maybe
> having some shared functions, but before starting to break out stuff
> I'd like to see how other Runtime PM implementations deal with this.
> So unless people object I prefer to keep it as-is for now.
What is the reason for requiring that the driver provide stub functions?
For me the issue is that if it's mandatory for the driver to provide the
functions then having stub functions in there makes the driver look like
it is abusing the API by not implementing mandatory functionality.
Given that the arch is now dealing with clocking and power for the
device using the runtime PM system it seems fairly clear that there are
going to be drivers like this one that can at least skip the suspend
part and may not need to do anything at resume time either.
next prev parent reply other threads:[~2009-11-17 12:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ud43sjtaf.wl%morimoto.kuninori@renesas.com>
2009-11-09 10:58 ` [alsa-devel] [PATCH 1/2 v2] ASoC: sh: fsi: Add runtime PM support Mark Brown
2009-11-09 13:31 ` Mark Brown
2009-11-16 15:30 ` Null suspend/resume functions Mark Brown
2009-11-16 19:07 ` Rafael J. Wysocki
2009-11-17 11:52 ` [linux-pm] " Pavel Machek
2009-11-17 12:41 ` Mark Brown
2009-11-18 16:09 ` Pavel Machek
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-17 12:46 ` Magnus Damm
2009-11-17 12:59 ` Mark Brown [this message]
2009-11-17 22:14 ` Rafael J. Wysocki
2009-11-18 13:41 ` Mark Brown
2009-11-18 10:09 ` Magnus Damm
2009-11-18 12:05 ` Mark Brown
2009-11-27 11:06 ` [alsa-devel] [PATCH 1/2 v2] ASoC: sh: fsi: Add runtime PM support 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=20091117125901.GF823@rakim.wolfsonmicro.main \
--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=magnus.damm@gmail.com \
--cc=morimoto.kuninori@renesas.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