From: Jonathan Cameron <jic23@cam.ac.uk>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: gregkh@linuxfoundation.org, grant.likely@secretlab.ca,
rob.herring@calxeda.com, jbrenner@taosinc.com, rklein@nvidia.com,
max@stro.at, linux-iio@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH V4 1/2] staging: iio: add channel info for sampling frequency
Date: Thu, 12 Apr 2012 15:27:51 +0100 [thread overview]
Message-ID: <4F86E667.6060606@cam.ac.uk> (raw)
In-Reply-To: <1334239266-29505-2-git-send-email-ldewangan@nvidia.com>
On 4/12/2012 3:01 PM, Laxman Dewangan wrote:
> Adding channel info IIO_CHAN_INFO_SAMP_FREQ to select
> different sampling frequency per channel wise.
>
> Signed-off-by: Laxman Dewangan<ldewangan@nvidia.com>
Acked-by: Jonathan Cameron <jic23@kernel.org>
> ---
> changes from V3:
> - Change the info name to "sampling_frequency"
>
> drivers/staging/iio/iio.h | 5 +++++
> drivers/staging/iio/industrialio-core.c | 1 +
> 2 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/staging/iio/iio.h b/drivers/staging/iio/iio.h
> index b9cd454..9aa0dd5 100644
> --- a/drivers/staging/iio/iio.h
> +++ b/drivers/staging/iio/iio.h
> @@ -36,6 +36,7 @@ enum iio_chan_info_enum {
> IIO_CHAN_INFO_QUADRATURE_CORRECTION_RAW,
> IIO_CHAN_INFO_AVERAGE_RAW,
> IIO_CHAN_INFO_LOW_PASS_FILTER_3DB_FREQUENCY,
> + IIO_CHAN_INFO_SAMP_FREQ,
> };
>
> #define IIO_CHAN_INFO_SHARED_BIT(type) BIT(type*2)
> @@ -81,6 +82,10 @@ enum iio_chan_info_enum {
> #define IIO_CHAN_INFO_LOW_PASS_FILTER_3DB_FREQUENCY_SEPARATE_BIT \
> IIO_CHAN_INFO_SEPARATE_BIT( \
> IIO_CHAN_INFO_LOW_PASS_FILTER_3DB_FREQUENCY)
> +#define IIO_CHAN_INFO_SAMP_FREQ_SEPARATE_BIT \
> + IIO_CHAN_INFO_SEPARATE_BIT(IIO_CHAN_INFO_SAMP_FREQ)
> +#define IIO_CHAN_INFO_SAMP_FREQ_SHARED_BIT \
> + IIO_CHAN_INFO_SHARED_BIT(IIO_CHAN_INFO_SAMP_FREQ)
>
> enum iio_endian {
> IIO_CPU,
> diff --git a/drivers/staging/iio/industrialio-core.c b/drivers/staging/iio/industrialio-core.c
> index d303bfb..9e42713 100644
> --- a/drivers/staging/iio/industrialio-core.c
> +++ b/drivers/staging/iio/industrialio-core.c
> @@ -90,6 +90,7 @@ static const char * const iio_chan_info_postfix[] = {
> [IIO_CHAN_INFO_AVERAGE_RAW] = "mean_raw",
> [IIO_CHAN_INFO_LOW_PASS_FILTER_3DB_FREQUENCY]
> = "filter_low_pass_3db_frequency",
> + [IIO_CHAN_INFO_SAMP_FREQ] = "sampling_frequency",
> };
>
> const struct iio_chan_spec
next prev parent reply other threads:[~2012-04-12 14:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 14:01 [PATCH V4 0/2] staging: iio: add isl29028 driver Laxman Dewangan
2012-04-12 14:01 ` [PATCH V4 1/2] staging: iio: add channel info for sampling frequency Laxman Dewangan
2012-04-12 14:27 ` Jonathan Cameron [this message]
2012-04-12 14:01 ` [PATCH V4 2/2] staging: iio: add driver for isl29028 Laxman Dewangan
2012-04-12 14:34 ` Jonathan Cameron
2012-04-13 9:48 ` Laxman Dewangan
2012-04-13 10:05 ` Jonathan Cameron
2012-04-13 9:49 ` Laxman Dewangan
2012-04-12 15:36 ` Stephen Warren
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=4F86E667.6060606@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=jbrenner@taosinc.com \
--cc=ldewangan@nvidia.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max@stro.at \
--cc=rklein@nvidia.com \
--cc=rob.herring@calxeda.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;
as well as URLs for NNTP newsgroup(s).