From: Johannes Berg <johannes@sipsolutions.net>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-pm <linux-pm@lists.osdl.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH] power management: no valid states w/o pm_ops + docs
Date: Tue, 13 Feb 2007 18:36:24 +0100 [thread overview]
Message-ID: <1171388184.10344.55.camel@johannes.berg> (raw)
In-Reply-To: <20070213092357.7ea02880.randy.dunlap@oracle.com>
[-- Attachment #1.1: Type: text/plain, Size: 2957 bytes --]
On Tue, 2007-02-13 at 09:23 -0800, Randy Dunlap wrote:
> On Tue, 13 Feb 2007 17:26:20 +0100 Johannes Berg wrote:
>
> > This patch changes /sys/power/state to not advertise any valid states
> > (except for disk if SOFTWARE_SUSPEND is enabled) when no pm_ops have been
> > set so userspace can easily discover what states should be available.
> >
> > Also, because the pm ops in powermac are obviously not using them as
> > intended, I added documentation for it in kernel-doc format.
>
> Thanks... but it's not quite in kernel-doc format.
Hmm ok :)
> Did you test it?
Yes! The output (in html) looked fine to me.
> > +/**
> > + * struct pm_ops
> > + *
> > + * Callbacks for managing platform dependent suspend states.
> > + *
>
> * struct pm_ops - callbacks for managing platform-dependent suspend states
But then the description "callbacks for ..." disappears completely in
the HTML output! Should I duplicate it or something?
> > + * @valid: Callback to determine whether the given state can be entered.
> > + * If %CONFIG_SOFTWARE_SUSPEND is set then %PM_SUSPEND_DISK is
> > + * always valid and never passed to this call.
> > + * If not assigned, all suspend states are advertised as valid
> > + * in /sys/power/state (but can still be rejected by prepare or enter.)
> > + * @prepare: Prepare the platform for the given suspend state. Can return a
> > + * negative error code if necessary.
> > + * @enter: Enter the given suspend state, must be assigned. Can return a
> > + * negative error code if necessary.
> > + * @finish: Called when the system has left the given state and all devices
> > + * are resumed. The return value is ignored.
> > + * @pm_disk_mode: Set to the disk method that the user should be able to
> > + * configure for suspend-to-disk. Since %PM_DISK_SHUTDOWN,
> > + * %PM_DISK_REBOOT, %PM_DISK_TEST and %PM_DISK_TESTPROC
> > + * are always allowed, currently only %PM_DISK_PLATFORM
> > + * makes sense. If the user then choses %PM_DISK_PLATFORM,
> > + * the @prepare call will be called before suspending to disk
> > + * (if present), the @enter call should be present and will
> > + * be called after all state has been saved and the machine
> > + * is ready to be shut down/suspended/..., and the @finish
> > + * callback is called after state has been restored. All
> > + * these calls are called with %PM_SUSPEND_DISK as the state.
>
> We usually just indent the following lines the same for all function
> parameters or struct members.
So I should indent them to the deepest indent I have like this?
@x: description for x
in two lines
@verylong: description for verylong
in two lines
Thanks,
Johannes
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2007-02-13 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 16:26 [PATCH] power management: no valid states w/o pm_ops + docs Johannes Berg
2007-02-13 17:23 ` Randy Dunlap
2007-02-13 17:36 ` Johannes Berg [this message]
2007-02-13 17:41 ` Randy Dunlap
2007-02-13 17:54 ` Johannes Berg
2007-02-13 17:57 ` Randy Dunlap
2007-02-13 18:02 ` Johannes Berg
2007-02-13 18:03 ` Randy Dunlap
2007-02-13 18:08 ` Johannes Berg
2007-02-13 18:09 ` Johannes Berg
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=1171388184.10344.55.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=akpm@osdl.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
--cc=randy.dunlap@oracle.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