From: Jonathan Cameron <jic23@kernel.org>
To: Octavian Purdila <octavian.purdila@intel.com>, linux-iio@vger.kernel.org
Cc: srinivas.pandruvada@linux.intel.com,
Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>
Subject: Re: [PATCH v4 1/3] iio: bmc150: change sampling frequency
Date: Sun, 08 Mar 2015 11:17:13 +0000 [thread overview]
Message-ID: <54FC2FB9.6090107@kernel.org> (raw)
In-Reply-To: <1425399478-5464-2-git-send-email-octavian.purdila@intel.com>
On 03/03/15 16:17, Octavian Purdila wrote:
> From: Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>
>
> Currently driver reports device bandwidth list as available
> sampling frequency. But sampling frequency is actually twice
> the device bandwidth. This patch fixes this issue.
>
> Signed-off-by: Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>
I was going to reject this on the basis that it should be using the
low_pass_filter_3db_bandwidth rather than sampling frequency but in
this device the two are tied together in a fashion not often seen.
Anyhow, fair enough.
It's probably going to make life messy with the rest of the series, but this
is clearly a fix that wants to stable as well.
Note Octavian that as you handled the patch it ought to have your sign off
as well as Sathyanarayanan's.
Jonathan
> ---
> drivers/iio/accel/bmc150-accel.c | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/iio/accel/bmc150-accel.c b/drivers/iio/accel/bmc150-accel.c
> index 8004ce3..74ee54e 100644
> --- a/drivers/iio/accel/bmc150-accel.c
> +++ b/drivers/iio/accel/bmc150-accel.c
> @@ -168,14 +168,14 @@ static const struct {
> int val;
> int val2;
> u8 bw_bits;
> -} bmc150_accel_samp_freq_table[] = { {7, 810000, 0x08},
> - {15, 630000, 0x09},
> - {31, 250000, 0x0A},
> - {62, 500000, 0x0B},
> - {125, 0, 0x0C},
> - {250, 0, 0x0D},
> - {500, 0, 0x0E},
> - {1000, 0, 0x0F} };
> +} bmc150_accel_samp_freq_table[] = { {15, 620000, 0x08},
> + {31, 260000, 0x09},
> + {62, 500000, 0x0A},
> + {125, 0, 0x0B},
> + {250, 0, 0x0C},
> + {500, 0, 0x0D},
> + {1000, 0, 0x0E},
> + {2000, 0, 0x0F} };
>
> static const struct {
> int bw_bits;
> @@ -783,7 +783,7 @@ static int bmc150_accel_validate_trigger(struct iio_dev *indio_dev,
> }
>
> static IIO_CONST_ATTR_SAMP_FREQ_AVAIL(
> - "7.810000 15.630000 31.250000 62.500000 125 250 500 1000");
> + "15.620000 31.260000 62.50000 125 250 500 1000 2000");
>
> static struct attribute *bmc150_accel_attributes[] = {
> &iio_const_attr_sampling_frequency_available.dev_attr.attr,
>
next prev parent reply other threads:[~2015-03-08 11:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 16:17 [PATCH v4 0/3] iio: bmc150: refactoring in preparation for hardware fifo support Octavian Purdila
2015-03-03 16:17 ` [PATCH v4 1/3] iio: bmc150: change sampling frequency Octavian Purdila
2015-03-08 11:17 ` Jonathan Cameron [this message]
2015-03-08 14:56 ` Octavian Purdila
2015-03-03 16:17 ` [PATCH v4 2/3] iio: bmc150: introduce bmc150_accel_interrupt Octavian Purdila
2015-03-08 11:22 ` Jonathan Cameron
2015-03-09 20:40 ` Srinivas Pandruvada
2015-03-14 18:39 ` Jonathan Cameron
2015-03-03 16:17 ` [PATCH v4 3/3] iio: bmc150: introduce bmc150_accel_trigger Octavian Purdila
2015-03-14 18:40 ` 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=54FC2FB9.6090107@kernel.org \
--to=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=octavian.purdila@intel.com \
--cc=sathyanarayanan.kuppuswamy@intel.com \
--cc=srinivas.pandruvada@linux.intel.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 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.