mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Suman, Viorel" <viorel.suman@intel.com>
To: "Reus, Adriana" <adriana.reus@intel.com>,
	"jic23@kernel.org" <jic23@kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>,
	"Reus, Adriana" <adriana.reus@intel.com>
Subject: RE: [PATCH] iio:inv-mpu6050: Fix inconsistency for the scale channel
Date: Wed, 4 Mar 2015 13:57:23 +0000	[thread overview]
Message-ID: <2FFB68359810C64CBFB43927F67FC93F48873F58@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <1424702451-1299-1-git-send-email-adriana.reus@intel.com>


> -----Original Message-----
> From: linux-iio-owner@vger.kernel.org [mailto:linux-iio-
> owner@vger.kernel.org] On Behalf Of Adriana Reus
> Sent: Monday, February 23, 2015 4:41 PM
> To: jic23@kernel.org; linux-iio@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org; Pandruvada, Srinivas; Reus, Adriana
> Subject: [PATCH] iio:inv-mpu6050: Fix inconsistency for the scale channel
> 
> Fix inconsistency in the semantics of the scale attribute.
> For scale the write_raw function was considering the scale table index and
> writing the appropriate value into the range register, while for read_raw it
> was outputting the actual scale.
> Fix this behaviour and adhere to the iio ABI specification.
> 
> Signed-off-by: Adriana Reus <adriana.reus@intel.com>

Reviewed-by: Viorel Suman <viorel.suman@intel.com>

> ---
>  drivers/iio/imu/inv_mpu6050/inv_mpu_core.c | 56 ++++++++++++++++--
> ------------
>  1 file changed, 30 insertions(+), 26 deletions(-)
> 
> diff --git a/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> b/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> index 9be9b20..4cf056d 100644
> --- a/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> +++ b/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> @@ -401,42 +401,46 @@ error_read_raw:
>  	}
>  }
> 
> -static int inv_mpu6050_write_fsr(struct inv_mpu6050_state *st, int fsr)
> +static int inv_mpu6050_write_gyro_scale(struct inv_mpu6050_state *st,
> +int val)
>  {
> -	int result;
> +	int result, i;
>  	u8 d;
> 
> -	if (fsr < 0 || fsr > INV_MPU6050_MAX_GYRO_FS_PARAM)
> -		return -EINVAL;
> -	if (fsr == st->chip_config.fsr)
> -		return 0;
> +	for (i = 0; i < ARRAY_SIZE(gyro_scale_6050); ++i) {
> +		if (gyro_scale_6050[i] == val) {
> +			d = (i <<
> INV_MPU6050_GYRO_CONFIG_FSR_SHIFT);
> +			result = inv_mpu6050_write_reg(st,
> +					st->reg->gyro_config, d);
> +			if (result)
> +				return result;
> 
> -	d = (fsr << INV_MPU6050_GYRO_CONFIG_FSR_SHIFT);
> -	result = inv_mpu6050_write_reg(st, st->reg->gyro_config, d);
> -	if (result)
> -		return result;
> -	st->chip_config.fsr = fsr;
> +			st->chip_config.fsr = i;
> +			return 0;
> +		}
> +	}
> 
> -	return 0;
> +	return -EINVAL;
>  }
> 
> -static int inv_mpu6050_write_accel_fs(struct inv_mpu6050_state *st, int
> fs)
> +static int inv_mpu6050_write_accel_scale(struct inv_mpu6050_state *st,
> +int val)
>  {
> -	int result;
> +	int result, i;
>  	u8 d;
> 
> -	if (fs < 0 || fs > INV_MPU6050_MAX_ACCL_FS_PARAM)
> -		return -EINVAL;
> -	if (fs == st->chip_config.accl_fs)
> -		return 0;
> +	for (i = 0; i < ARRAY_SIZE(accel_scale); ++i) {
> +		if (accel_scale[i] == val) {
> +			d = (i << INV_MPU6050_ACCL_CONFIG_FSR_SHIFT);
> +			result = inv_mpu6050_write_reg(st,
> +					st->reg->accl_config, d);
> +			if (result)
> +				return result;
> 
> -	d = (fs << INV_MPU6050_ACCL_CONFIG_FSR_SHIFT);
> -	result = inv_mpu6050_write_reg(st, st->reg->accl_config, d);
> -	if (result)
> -		return result;
> -	st->chip_config.accl_fs = fs;
> +			st->chip_config.accl_fs = i;
> +			return 0;
> +		}
> +	}
> 
> -	return 0;
> +	return -EINVAL;
>  }
> 
>  static int inv_mpu6050_write_raw(struct iio_dev *indio_dev, @@ -463,10
> +467,10 @@ static int inv_mpu6050_write_raw(struct iio_dev *indio_dev,
>  	case IIO_CHAN_INFO_SCALE:
>  		switch (chan->type) {
>  		case IIO_ANGL_VEL:
> -			result = inv_mpu6050_write_fsr(st, val);
> +			result = inv_mpu6050_write_gyro_scale(st, val2);
>  			break;
>  		case IIO_ACCEL:
> -			result = inv_mpu6050_write_accel_fs(st, val);
> +			result = inv_mpu6050_write_accel_scale(st, val2);
>  			break;
>  		default:
>  			result = -EINVAL;
> --
> 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

  reply	other threads:[~2015-03-04 13:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 14:40 Adriana Reus
2015-03-04 13:57 ` Suman, Viorel [this message]
2015-03-08 11:06   ` 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=2FFB68359810C64CBFB43927F67FC93F48873F58@IRSMSX102.ger.corp.intel.com \
    --to=viorel.suman@intel.com \
    --cc=adriana.reus@intel.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivas.pandruvada@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®