LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Liam Girdwood <lg@opensource.wolfsonmicro.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 2/6] regulator: regulator driver interface.
Date: Sat, 23 Feb 2008 00:05:32 -0800	[thread overview]
Message-ID: <20080223000532.a0eb106f.akpm@linux-foundation.org> (raw)
In-Reply-To: <1203527341.4071.90.camel@localhost.localdomain>

On Wed, 20 Feb 2008 17:09:00 +0000 Liam Girdwood <lg@opensource.wolfsonmicro.com> wrote:

> This interface allows regulator drivers to register their voltage and current
> regulators with the core. It also has a notifier call chain for propagating
> regulator events to clients.
> 
> +
> +/**
> + * struct regulator_ops - regulator operations.
> + *
> + * This struct describes regulator operations.
> + */

You can actually document the struct's fields in the kerneldoc comment
here, although I tend to think that it's better to document them as you
have done - ther eis more room, and people are more likely to remember to
update the comments when adding/removing/modifying fields.

> +struct regulator_ops {
> +
> +	/* get/set regulator voltage */
> +	int (*set_voltage)(struct regulator_cdev *, int uV);
> +	int (*get_voltage)(struct regulator_cdev *);
> +
> +	/* get/set regulator current  */
> +	int (*set_current)(struct regulator_cdev *, int uA);
> +	int (*get_current)(struct regulator_cdev *);
> +
> +	/* enable/disable regulator */
> +	int (*enable)(struct regulator_cdev *);
> +	int (*disable)(struct regulator_cdev *);
> +	int (*is_enabled)(struct regulator_cdev *);
> +
> +	/* get/set regulator operating mode (defined in regulator.h) */
> +	int (*set_mode)(struct regulator_cdev *, unsigned int mode);
> +	unsigned int (*get_mode)(struct regulator_cdev *);
> +
> +	/* get most efficient regulator operating mode for load */
> +	unsigned int (*get_optimum_mode)(struct regulator_cdev *, int input_uV,
> +		int output_uV, int load_uA);
> +};
>
> ...
>
> +/**
> + * regulator_get_drvdata - get regulator driver data
> + * @regulator: regulator
> + */
> +void *rcdev_get_drvdata (struct regulator_cdev *rcdev);
> +
> +/**
> + * regulator_get_id - get regulator ID
> + * @regulator: regulator
> + */
> +int rcdev_get_id (struct regulator_cdev *rcdev);

Please use scripts/checkpatch.pl...

      reply	other threads:[~2008-02-23  8:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 17:09 Liam Girdwood
2008-02-23  8:05 ` Andrew Morton [this message]

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=20080223000532.a0eb106f.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lg@opensource.wolfsonmicro.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH 2/6] regulator: regulator driver interface.' \
    /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

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).