From: Jonathan Cameron <jic23@kernel.org>
To: <alexandru.tachici@analog.com>
Cc: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/8] iio: adc: ad7124: Add update_scan_mode
Date: Sat, 19 Mar 2022 15:45:43 +0000 [thread overview]
Message-ID: <20220319154543.0ae8993e@jic23-huawei> (raw)
In-Reply-To: <20220318162722.51215-3-alexandru.tachici@analog.com>
On Fri, 18 Mar 2022 18:27:16 +0200
<alexandru.tachici@analog.com> wrote:
> From: Alexandru Tachici <alexandru.tachici@analog.com>
>
> The callback .set_channel cannot be used to enable
> and disable multiple channels at once as they are
> presented in the active_scan_mask.
Trivial: Aim to wrap commit messages around 70ish chars
and whatever you pick be consistent.
Patch looks fine to me otherwise so if nothing else comes up, I
may rewrap these patch descriptions whilst applying.
Jonathan
>
> By adding an update_scan_mode callback, every time the
> continuous mode is activated, channels will be enabled/disabled
> accordingly.
>
> Signed-off-by: Alexandru Tachici <alexandru.tachici@analog.com>
> ---
> drivers/iio/adc/ad7124.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/drivers/iio/adc/ad7124.c b/drivers/iio/adc/ad7124.c
> index 7249db2c4422..428ec3e257d7 100644
> --- a/drivers/iio/adc/ad7124.c
> +++ b/drivers/iio/adc/ad7124.c
> @@ -669,11 +669,32 @@ static const struct attribute_group ad7124_attrs_group = {
> .attrs = ad7124_attributes,
> };
>
> +static int ad7124_update_scan_mode(struct iio_dev *indio_dev,
> + const unsigned long *scan_mask)
> +{
> + struct ad7124_state *st = iio_priv(indio_dev);
> + bool bit_set;
> + int ret;
> + int i;
> +
> + for (i = 0; i < st->num_channels; i++) {
> + bit_set = test_bit(i, scan_mask);
> + ret = ad7124_spi_write_mask(st, AD7124_CHANNEL(i),
> + AD7124_CHANNEL_EN_MSK,
> + AD7124_CHANNEL_EN(bit_set),
> + 2);
> + if (ret < 0)
> + return ret;
> + }
> + return 0;
> +}
> +
> 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,
> + .update_scan_mode = ad7124_update_scan_mode,
> .attrs = &ad7124_attrs_group,
> };
>
next prev parent reply other threads:[~2022-03-19 15:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 16:27 [PATCH v2 0/8] iio: adc: ad_sigma_delta: Add sequencer support alexandru.tachici
2022-03-18 16:27 ` [PATCH v2 1/8] iio: adc: ad7124: Remove shift from scan_type alexandru.tachici
2022-03-19 15:38 ` Jonathan Cameron
2022-03-18 16:27 ` [PATCH v2 2/8] iio: adc: ad7124: Add update_scan_mode alexandru.tachici
2022-03-19 15:45 ` Jonathan Cameron [this message]
2022-03-18 16:27 ` [PATCH v2 3/8] iio: adc: ad7192: " alexandru.tachici
2022-03-18 16:27 ` [PATCH v2 4/8] iio: adc: ad_sigma_delta: Add sequencer support alexandru.tachici
2022-03-19 16:03 ` Jonathan Cameron
2022-03-18 16:27 ` [PATCH v2 5/8] iio: adc: ad7124: add " alexandru.tachici
2022-03-19 16:09 ` Jonathan Cameron
2022-03-18 16:27 ` [PATCH v2 6/8] iio: adc: ad7192: " alexandru.tachici
2022-03-19 16:11 ` Jonathan Cameron
2022-03-18 16:27 ` [PATCH v2 7/8] iio: adc: ad7124: add disable_all() callback alexandru.tachici
2022-03-19 16:10 ` Jonathan Cameron
2022-03-18 16:27 ` [PATCH v2 8/8] iio: adc: ad7192: " alexandru.tachici
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=20220319154543.0ae8993e@jic23-huawei \
--to=jic23@kernel.org \
--cc=alexandru.tachici@analog.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