From: Jonathan Cameron <jic23@kernel.org>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: Jonathan Cameron <jic23@cam.ac.uk>, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: document missing elements
Date: Tue, 28 Aug 2012 20:41:56 +0100 [thread overview]
Message-ID: <503D1F04.7010709@kernel.org> (raw)
In-Reply-To: <1345985019-24288-2-git-send-email-pmeerw@pmeerw.net>
On 08/26/2012 01:43 PM, Peter Meerwald wrote:
> Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>
merged to togreg branch
> ---
> include/linux/iio/iio.h | 4 ++++
> include/linux/iio/trigger.h | 5 +++--
> 2 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/iio/iio.h b/include/linux/iio/iio.h
> index f323e7b..f966a7e 100644
> --- a/include/linux/iio/iio.h
> +++ b/include/linux/iio/iio.h
> @@ -229,6 +229,7 @@ ssize_t iio_enum_write(struct iio_dev *indio_dev,
> * @indexed: Specify the channel has a numerical index. If not,
> * the channel index number will be suppressed for sysfs
> * attributes but not for event codes.
> + * @output: Channel is output.
> * @differential: Channel is differential.
> */
> struct iio_chan_spec {
> @@ -312,6 +313,9 @@ struct iio_dev;
> * Meaning is event dependent.
> * @validate_trigger: function to validate the trigger when the
> * current trigger gets changed.
> + * @update_scan_mode: function to configure device and scan buffer when
> + * channels have changed
> + * @debugfs_reg_access: function to read or write register value of device
> **/
> struct iio_info {
> struct module *driver_module;
> diff --git a/include/linux/iio/trigger.h b/include/linux/iio/trigger.h
> index a981994..f0af267 100644
> --- a/include/linux/iio/trigger.h
> +++ b/include/linux/iio/trigger.h
> @@ -39,7 +39,7 @@ struct iio_trigger_ops {
>
> /**
> * struct iio_trigger - industrial I/O trigger device
> - *
> + * @ops: [DRIVER] operations structure
> * @id: [INTERN] unique id number
> * @name: [DRIVER] unique name
> * @dev: [DRIVER] associated device (if relevant)
> @@ -104,7 +104,8 @@ void iio_trigger_unregister(struct iio_trigger *trig_info);
>
> /**
> * iio_trigger_poll() - called on a trigger occurring
> - * @trig: trigger which occurred
> + * @trig: trigger which occurred
> + * @time: timestamp when trigger occurred
> *
> * Typically called in relevant hardware interrupt handler.
> **/
>
next prev parent reply other threads:[~2012-08-28 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-26 12:43 [PATCH] iio: fix typos Peter Meerwald
2012-08-26 12:43 ` [PATCH] iio: document missing elements Peter Meerwald
2012-08-28 19:41 ` Jonathan Cameron [this message]
2012-08-26 12:43 ` [PATCH] iio: whitespace cleanup and removal of semicolon after functions Peter Meerwald
2012-08-28 19:42 ` Jonathan Cameron
2012-08-28 19:41 ` [PATCH] iio: fix typos Jonathan Cameron
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=503D1F04.7010709@kernel.org \
--to=jic23@kernel.org \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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.