From: Pavel Machek <pavel@ucw.cz>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] Null suspend/resume functions
Date: Sun, 22 Nov 2009 00:45:10 +0100 [thread overview]
Message-ID: <20091121234509.GC1411@ucw.cz> (raw)
In-Reply-To: <20091119112102.GF9763@rakim.wolfsonmicro.main>
On Thu 2009-11-19 11:21:03, Mark Brown wrote:
> On Wed, Nov 18, 2009 at 05:09:08PM +0100, Pavel Machek wrote:
> > On Tue 2009-11-17 12:41:25, Mark Brown wrote:
>
> > > The problem I have with that is that for most APIs noop functions are a
> > > big fat warning sign that something is going wrong and the API is being
> > > abused. This then creates noise and code review problems in the driver
> > > code since you've got something that normally suggests a problem.
>
> > That still sounds like poor reason to add tests to core. But return 0
> > function for that purpose should be ok (and should make code easy to
> > review, too).
>
> What makes you believe that this is a poor reason? The issue isn't that
> the driver code is complex, the issue is that it's noise in the driver
> which suggests that the driver isn't doing something it's supposed to
> do.
So you place a comment there; it should be there anyway. Having nop
during suspend/resume *is* unusual, and it should raise red flags.
Plus, if we allowed NULLs there, we'd not know if the driver does not
implement it because it is not neccessary, or because they don't care.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-11-21 23:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ud43sjtaf.wl%morimoto.kuninori@renesas.com>
[not found] ` <20091109105858.GB1245@sirena.org.uk>
2009-11-09 13:31 ` [alsa-devel] [PATCH 1/2 v2] ASoC: sh: fsi: Add runtime PM support Mark Brown
[not found] ` <20091109133136.GC1245@sirena.org.uk>
2009-11-16 15:30 ` Null suspend/resume functions Mark Brown
[not found] ` <20091116153000.GB29479@sirena.org.uk>
2009-11-16 19:07 ` Rafael J. Wysocki
2009-11-17 11:52 ` Pavel Machek
[not found] ` <20091117115236.GB1376@ucw.cz>
2009-11-17 12:41 ` Mark Brown
[not found] ` <20091117124125.GD823@rakim.wolfsonmicro.main>
2009-11-18 16:09 ` Pavel Machek
[not found] ` <20091118160908.GD20887@elf.ucw.cz>
2009-11-19 11:21 ` Mark Brown
[not found] ` <20091119112102.GF9763@rakim.wolfsonmicro.main>
2009-11-21 23:45 ` Pavel Machek [this message]
2009-11-23 11:02 ` [linux-pm] " Mark Brown
2009-11-24 11:57 ` Pavel Machek
2009-11-17 12:46 ` Magnus Damm
[not found] ` <aec7e5c30911170446n71031671i48aca11f5276405d@mail.gmail.com>
2009-11-17 12:59 ` Mark Brown
[not found] ` <20091117125901.GF823@rakim.wolfsonmicro.main>
2009-11-17 22:14 ` Rafael J. Wysocki
2009-11-18 10:09 ` Magnus Damm
[not found] ` <aec7e5c30911180209x1981978es80db2dadf7dd8ef4@mail.gmail.com>
2009-11-18 12:05 ` Mark Brown
[not found] ` <200911172314.04396.rjw@sisk.pl>
2009-11-18 13:41 ` 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=20091121234509.GC1411@ucw.cz \
--to=pavel@ucw.cz \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.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