From: Jonathan Cameron <jic23@kernel.org>
To: Markus Burri <markus.burri@mt.com>
Cc: linux-kernel@vger.kernel.org,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Alisa-Dariana Roman" <alisa.roman@analog.com>,
linux-iio@vger.kernel.org, "Nuno Sá" <nuno.sa@analog.com>
Subject: Re: [PATCH v2] iio: adc: ad7192: fix channel select
Date: Sat, 25 Jan 2025 12:22:22 +0000 [thread overview]
Message-ID: <20250125122222.22e3285a@jic23-huawei> (raw)
In-Reply-To: <20250124150703.97848-1-markus.burri@mt.com>
On Fri, 24 Jan 2025 16:07:03 +0100
Markus Burri <markus.burri@mt.com> wrote:
> Channel configuration doesn't work as expected.
> For FIELD_PREP the bit mask is needed and not the bit number.
>
> Fixes: 874bbd1219c7 ("iio: adc: ad7192: Use bitfield access macros")
needs to be part of the tags block. Hence no blank line here.
I'll tidy that up whilst applying. Applied and marked for stable.
Note I'll not push out my tree until I can rebase on rc1 after
next weekend as right now it would make a mess of linux-next.
>
> Signed-off-by: Markus Burri <markus.burri@mt.com>
> Reviewed-by: Nuno Sá <nuno.sa@analog.com>
> ---
> drivers/iio/adc/ad7192.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/adc/ad7192.c b/drivers/iio/adc/ad7192.c
> index 1c87db0e0460..c4effe8429c8 100644
> --- a/drivers/iio/adc/ad7192.c
> +++ b/drivers/iio/adc/ad7192.c
> @@ -1082,7 +1082,7 @@ static int ad7192_update_scan_mode(struct iio_dev *indio_dev, const unsigned lon
>
> conf &= ~AD7192_CONF_CHAN_MASK;
> for_each_set_bit(i, scan_mask, 8)
> - conf |= FIELD_PREP(AD7192_CONF_CHAN_MASK, i);
> + conf |= FIELD_PREP(AD7192_CONF_CHAN_MASK, BIT(i));
>
> ret = ad_sd_write_reg(&st->sd, AD7192_REG_CONF, 3, conf);
> if (ret < 0)
>
> base-commit: ffd294d346d185b70e28b1a28abe367bbfe53c04
prev parent reply other threads:[~2025-01-25 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 15:07 Markus Burri
2025-01-25 12:22 ` 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=20250125122222.22e3285a@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=alisa.roman@analog.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.burri@mt.com \
--cc=nuno.sa@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®