From: Jonathan Cameron <jic23@kernel.org>
To: Jean-Baptiste Maneyrol <JManeyrol@invensense.com>
Cc: Martin Kelly <mkelly@xevo.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: imu: inv_mpu6050: add comment about frequencies
Date: Tue, 22 May 2018 18:33:24 +0100 [thread overview]
Message-ID: <20180522183324.412667f2@archlinux> (raw)
In-Reply-To: <CY4PR1201MB0184CB717224AA426AF6E501C4940@CY4PR1201MB0184.namprd12.prod.outlook.com>
On Tue, 22 May 2018 12:55:23 +0000
Jean-Baptiste Maneyrol <JManeyrol@invensense.com> wrote:
> Acked-by: Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>
>=20
>=20
> From: Martin Kelly <mkelly@xevo.com>
> Sent: Monday, May 21, 2018 20:41
> To: linux-iio@vger.kernel.org
> Cc: Jean-Baptiste Maneyrol; Jonathan Cameron; Martin Kelly
> Subject: [PATCH] iio: imu: inv_mpu6050: add comment about frequencies
>=20
> Although the driver allows frequencies between 4 and 1000 Hz, only the
> frequencies advertised in the available frequencies file are backed
> properly by a low-pass filter to prevent aliasing, so it's best to use
> them. Since this is not obvious to the user, add a comment explaining
> what's going on.
>=20
> Signed-off-by: Martin Kelly <mkelly@xevo.com>
Applied to the togreg branch of iio.git and pushed out as testing for the
autobuilders to play with it.
Thanks,
Jonathan
> ---
> =C2=A0drivers/iio/imu/inv_mpu6050/inv_mpu_core.c | 9 ++++++++-
> =C2=A01 file changed, 8 insertions(+), 1 deletion(-)
>=20
> diff --git a/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c b/drivers/iio/imu=
/inv_mpu6050/inv_mpu_core.c
> index 43fba5f7532b..f9c0624505a2 100644
> --- a/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> +++ b/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> @@ -798,7 +798,14 @@ static const struct iio_chan_spec inv_mpu_channels[]=
=3D {
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 INV_MPU6050_CHAN(IIO_ACCEL, II=
O_MOD_Z, INV_MPU6050_SCAN_ACCL_Z),
> =C2=A0};
>=20
> -/* constant IIO attribute */
> +/*
> + * The user can choose any frequency between INV_MPU6050_MIN_FIFO_RATE a=
nd
> + * INV_MPU6050_MAX_FIFO_RATE, but only these frequencies are matched by =
the
> + * low-pass filter. Specifically, each of these sampling rates are about=
twice
> + * the bandwidth of a corresponding low-pass filter, which should elimin=
ate
> + * aliasing following the Nyquist principle. By picking a frequency diff=
erent
> + * from these, the user risks aliasing effects.
> + */
> =C2=A0static IIO_CONST_ATTR_SAMP_FREQ_AVAIL("10 20 50 100 200 500");
> =C2=A0static IIO_CONST_ATTR(in_anglvel_scale_available,
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 "0.000133090 0.000266181 0.000532362 0.001064724");
> --
> 2.11.0
>=20
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-05-22 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 18:41 [PATCH] iio: imu: inv_mpu6050: add comment about frequencies Martin Kelly
2018-05-22 12:55 ` Jean-Baptiste Maneyrol
2018-05-22 17:33 ` Jonathan Cameron [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=20180522183324.412667f2@archlinux \
--to=jic23@kernel.org \
--cc=JManeyrol@invensense.com \
--cc=linux-iio@vger.kernel.org \
--cc=mkelly@xevo.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).