From: Lars-Peter Clausen <lars@metafoo.de>
To: Mircea Caprioru <mircea.caprioru@analog.com>, jic23@kernel.org
Cc: Michael.Hennerich@analog.com, alexandru.ardelean@analog.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH V3] iio: adc: ad7124: Add direct reg access
Date: Wed, 29 Jan 2020 19:15:11 +0100 [thread overview]
Message-ID: <eb4d0972-f95c-39f7-0520-c71c8370428d@metafoo.de> (raw)
In-Reply-To: <20200129085356.28899-1-mircea.caprioru@analog.com>
[...]
>
> +static int ad7124_reg_access(struct iio_dev *indio_dev,
> + unsigned int reg,
> + unsigned int writeval,
> + unsigned int *readval)
> +{
> + struct ad7124_state *st = iio_priv(indio_dev);
> + int ret;
> +
> + if (reg >= AD7124_REG_NO)
How about ARRAY_SIZE(ad7124_reg_size)? That will make sure that the
check is always correct and does not depend on an extra constant that
might go out-of-sync with the array. It also makes it easier for
reviewers to check that the code is correct. Otherwise they'll have to
count how many entries there are in ad7124_reg_size.
> + return -EINVAL;
> +
> + if (readval)
> + ret = ad_sd_read_reg(&st->sd, reg, ad7124_reg_size[reg],
> + readval);
> + else
> + ret = ad_sd_write_reg(&st->sd, reg, ad7124_reg_size[reg],
> + writeval);
> +
> + return ret;
> +}
> +
> static IIO_CONST_ATTR(in_voltage_scale_available,
> "0.000001164 0.000002328 0.000004656 0.000009313 0.000018626 0.000037252 0.000074505 0.000149011 0.000298023");
>
> @@ -375,6 +406,7 @@ static const struct attribute_group ad7124_attrs_group = {
> static const struct iio_info ad7124_info = {
> .read_raw = ad7124_read_raw,
> .write_raw = ad7124_write_raw,
> + .debugfs_reg_access = &ad7124_reg_access,
> .validate_trigger = ad_sd_validate_trigger,
> .attrs = &ad7124_attrs_group,
> };
>
prev parent reply other threads:[~2020-01-29 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 8:53 Mircea Caprioru
2020-01-29 18:15 ` Lars-Peter Clausen [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=eb4d0972-f95c-39f7-0520-c71c8370428d@metafoo.de \
--to=lars@metafoo.de \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.ardelean@analog.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mircea.caprioru@analog.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®