From: Jonathan Cameron <jic23@kernel.org>
To: Ge Gao <GGao@invensense.com>, Adriana Reus <adriana.reus@intel.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] iio: inv-mpu: Specify the expected format/precision for write channels
Date: Sat, 13 Jun 2015 19:00:18 +0100 [thread overview]
Message-ID: <557C6FB2.3010206@kernel.org> (raw)
In-Reply-To: <E7747D604FBC9F43A71AA431AFF4476299C52ADD@IUSEXCH01.invcorp.invensense.com>
On 11/06/15 18:31, Ge Gao wrote:
> These code looks good to me.
> Thanks.
>
> Best Regards,
>
> Ge GAO
Ge, formal Ack definitely preferred, but thanks for taking a look.
Adriana, please put fixes at the start of such a series. It didn't
matter here as the two changes were non overlapping but they take
different paths so if there is overlap I need to get the fix
out ASAP and then the improvements such as patch 1 can follow slower.
Anyhow, applied to the fixes-togreg branch of iio.git (probably to
go upstream post the merge window now). Marked for stable.
>
>
> -----Original Message-----
> From: Adriana Reus [mailto:adriana.reus@intel.com]
> Sent: Friday, June 12, 2015 8:10 AM
> To: Ge Gao; jic23@kernel.org
> Cc: linux-iio@vger.kernel.org; linux-kernel@vger.kernel.org; Adriana Reus
> Subject: [PATCH 2/2] iio: inv-mpu: Specify the expected format/precision for write channels
>
> The gyroscope needs IIO_VAL_INT_PLUS_NANO for the scale channel and unless specified write returns MICRO by default.
> This needs to be properly specified so that write operations into scale have the expected behaviour.
>
> Signed-off-by: Adriana Reus <adriana.reus@intel.com>
> ---
> drivers/iio/imu/inv_mpu6050/inv_mpu_core.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c b/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> index 096e545..4de5374 100644
> --- a/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> +++ b/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> @@ -431,6 +431,23 @@ static int inv_mpu6050_write_gyro_scale(struct inv_mpu6050_state *st, int val)
> return -EINVAL;
> }
>
> +static int inv_write_raw_get_fmt(struct iio_dev *indio_dev,
> + struct iio_chan_spec const *chan, long mask) {
> + switch (mask) {
> + case IIO_CHAN_INFO_SCALE:
> + switch (chan->type) {
> + case IIO_ANGL_VEL:
> + return IIO_VAL_INT_PLUS_NANO;
> + default:
> + return IIO_VAL_INT_PLUS_MICRO;
> + }
> + default:
> + return IIO_VAL_INT_PLUS_MICRO;
> + }
> +
> + return -EINVAL;
> +}
> static int inv_mpu6050_write_accel_scale(struct inv_mpu6050_state *st, int val) {
> int result, i;
> @@ -702,6 +719,7 @@ static const struct iio_info mpu_info = {
> .driver_module = THIS_MODULE,
> .read_raw = &inv_mpu6050_read_raw,
> .write_raw = &inv_mpu6050_write_raw,
> + .write_raw_get_fmt = &inv_write_raw_get_fmt,
> .attrs = &inv_attribute_group,
> .validate_trigger = inv_mpu6050_validate_trigger, };
> --
> 1.9.1
>
> --
> 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:[~2015-06-13 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 15:10 [PATCH 0/2] iio: inv-mpu: small scale fixes Adriana Reus
2015-06-12 15:10 ` [PATCH 1/2] iio: inv-mpu: Export scale_available attributes Adriana Reus
2015-06-13 18:01 ` Jonathan Cameron
2015-06-12 15:10 ` [PATCH 2/2] iio: inv-mpu: Specify the expected format/precision for write channels Adriana Reus
2015-06-11 17:31 ` Ge Gao
2015-06-13 18:00 ` 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=557C6FB2.3010206@kernel.org \
--to=jic23@kernel.org \
--cc=GGao@invensense.com \
--cc=adriana.reus@intel.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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