linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Peter Meerwald <pmeerw@pmeerw.net>, linux-iio@vger.kernel.org
Subject: Re: [PATCH v3 01/10] staging:iio:hmc5843: Use SCALE instead of magn_range
Date: Tue, 15 Oct 2013 23:14:22 +0100	[thread overview]
Message-ID: <525DBE3E.3010005@kernel.org> (raw)
In-Reply-To: <1381786498-25954-2-git-send-email-pmeerw@pmeerw.net>

On 10/14/13 22:34, Peter Meerwald wrote:
> v2:
> * use SCALE instead of CALIBSCALE to control the range/gain
>   of measurements
>
Only a couple of tiny little comments.  The function *_check_scale
does rather more than checking the scale is valid.  Perhaps
the name could reflect that?

Also, would it make more sense to move the shift into that function
rather than having it directly afterwards?  (I don't really mind
about this though!)
> Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>
Looking very nice.

...

hmc5843_get_scale_index?
or with the shift already applied
hmc5843_get_scale_regval
> +static int hmc5843_check_scale(struct hmc5843_data *data, int val, int val2)
> +{
> +	int i;
>
> -	if (range > HMC5843_RANGE_GAIN_MAX) {
> -		count = -EINVAL;
> -		goto exit;
> -	}
> +	if (val != 0)
> +		return -EINVAL;
>
> -	data->range = range;
> -	range = range << HMC5843_RANGE_GAIN_OFFSET;
> -	if (i2c_smbus_write_byte_data(data->client, this_attr->address, range))
> -		count = -EINVAL;
> +	for (i = 0; i < HMC5843_RANGE_GAINS; i++)
> +		if (val2 == data->variant->regval_to_nanoscale[i])
> +			return i;
>
> -exit:
> -	mutex_unlock(&data->lock);
> -	return count;
> +	return -EINVAL;
>  }
...
>

  reply	other threads:[~2013-10-15 21:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14 21:34 [PATCH v3 00/10] hmc5843 cleanup Peter Meerwald
2013-10-14 21:34 ` [PATCH v3 01/10] staging:iio:hmc5843: Use SCALE instead of magn_range Peter Meerwald
2013-10-15 22:14   ` Jonathan Cameron [this message]
2013-10-14 21:34 ` [PATCH v3 02/10] staging:iio:hmc5843: Always read all channels values otherwise no updates Peter Meerwald
2013-10-15  5:39   ` Lars-Peter Clausen
2013-10-14 21:34 ` [PATCH v3 03/10] staging:iio:hmc5843: Add trigger handling Peter Meerwald
2013-10-14 21:34 ` [PATCH v3 04/10] staging:iio:hmc5843: Remove ability to change operating mode Peter Meerwald
2013-10-14 21:34 ` [PATCH v3 05/10] staging:iio:hmc5843: Rename _configure() to _set_mode() Peter Meerwald
2013-10-14 21:34 ` [PATCH v3 06/10] staging:iio:hmc5843: Reorganize _set_meas_conf() Peter Meerwald
2013-10-14 21:34 ` [PATCH v3 07/10] staging:iio:hmc5843: Rename _set_rate() to _set_samp_freq() Peter Meerwald
2013-10-14 21:34 ` [PATCH v3 08/10] staging:iio:hmc5843: Introduce _set_range_gain() Peter Meerwald
2013-10-14 21:34 ` [PATCH v3 09/10] staging:iio:hmc5843: Check initialization and chip identifier Peter Meerwald
2013-10-14 21:34 ` [PATCH v3 10/10] staging:iio:hmc5843: Trivial cleanups Peter Meerwald

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=525DBE3E.3010005@kernel.org \
    --to=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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).