From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Rodrigo Alencar <455.rodrigo.alencar@gmail.com>
Cc: rodrigo.alencar@analog.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
Stefan Popa <stefan.popa@analog.com>,
Jonathan Cameron <jic23@cam.ac.uk>,
Greg Kroah-Hartman <gregkh@suse.de>,
Michael Auchter <michael.auchter@ni.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
David Lechner <dlechner@baylibre.com>,
Andy Shevchenko <andy@kernel.org>
Subject: Re: [PATCH v6 03/12] iio: dac: ad5686: acquire lock when doing powerdown control
Date: Tue, 5 May 2026 18:21:57 +0300 [thread overview]
Message-ID: <afoLFebe4fgNxXUV@ashevche-desk.local> (raw)
In-Reply-To: <a2tm4z5urvnurh3z2ntbm7rddv6eg236gbkvtz5cididtc2rv5@skk5x6kykaij>
On Tue, May 05, 2026 at 03:06:31PM +0100, Rodrigo Alencar wrote:
> On 26/05/05 03:58PM, Andy Shevchenko wrote:
> > On Tue, May 05, 2026 at 01:35:04PM +0100, Rodrigo Alencar via B4 Relay wrote:
...
> > > static ssize_t ad5686_read_dac_powerdown(struct iio_dev *indio_dev,
> > > {
> > > struct ad5686_state *st = iio_priv(indio_dev);
> > >
> > > + guard(mutex)(&st->lock);
> > > +
> > > return sysfs_emit(buf, "%d\n", !!(st->pwr_down_mask &
> > > (0x3 << (chan->channel * 2))));
> >
> > Why not use ad5686_get_powerdown_mode() instead?
>
> powerdown mode != powerdown mask. The powerdown mask controls the on-off
> behavior, while the mode controls the possible values for when it is off.
Ah, unfortunate naming collision (easy to mix up them).
> > > }
...
> > > static ssize_t ad5686_write_dac_powerdown(struct iio_dev *indio_dev,
> > > if (ret)
> > > return ret;
> > >
> > > + guard(mutex)(&st->lock);
> > > +
> > > if (readin)
> > > st->pwr_down_mask |= (0x3 << (chan->channel * 2));
> > > else
> >
> > Similar question here...
>
> I suppose the above applies here as well.
Yep, thanks for clarification!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-05-05 15:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 12:35 [PATCH v6 00/12] Fixes and cleanups for the AD5686 IIO driver Rodrigo Alencar via B4 Relay
2026-05-05 12:35 ` [PATCH v6 01/12] iio: dac: ad5686: fix ref bit initialization for single-channel parts Rodrigo Alencar via B4 Relay
2026-05-05 12:35 ` [PATCH v6 02/12] iio: dac: ad5686: fix input raw value check Rodrigo Alencar via B4 Relay
2026-05-05 12:35 ` [PATCH v6 03/12] iio: dac: ad5686: acquire lock when doing powerdown control Rodrigo Alencar via B4 Relay
2026-05-05 12:58 ` Andy Shevchenko
2026-05-05 14:06 ` Rodrigo Alencar
2026-05-05 15:21 ` Andy Shevchenko [this message]
2026-05-05 12:35 ` [PATCH v6 04/12] iio: dac: ad5686: fix powerdown control on dual-channel devices Rodrigo Alencar via B4 Relay
2026-05-05 12:35 ` [PATCH v6 05/12] iio: dac: ad5686: refactor include headers Rodrigo Alencar via B4 Relay
2026-05-05 12:35 ` [PATCH v6 06/12] iio: dac: ad5686: remove redundant register definition Rodrigo Alencar via B4 Relay
2026-05-05 12:35 ` [PATCH v6 07/12] iio: dac: ad5686: drop enum id Rodrigo Alencar via B4 Relay
2026-05-05 12:35 ` [PATCH v6 08/12] iio: dac: ad5686: add of_match table to the spi driver Rodrigo Alencar via B4 Relay
2026-05-05 12:35 ` [PATCH v6 09/12] iio: dac: ad5686: add helpers to handle powerdown masks Rodrigo Alencar via B4 Relay
2026-05-05 13:17 ` Andy Shevchenko
2026-05-05 14:13 ` Rodrigo Alencar
2026-05-05 15:27 ` Andy Shevchenko
2026-05-05 15:50 ` Rodrigo Alencar
2026-05-05 16:31 ` Rodrigo Alencar
2026-05-05 12:35 ` [PATCH v6 10/12] iio: dac: ad5686: add control_sync() for single-channel devices Rodrigo Alencar via B4 Relay
2026-05-05 12:35 ` [PATCH v6 11/12] iio: dac: ad5686: cleanup doc header of local structs Rodrigo Alencar via B4 Relay
2026-05-05 12:35 ` [PATCH v6 12/12] iio: dac: ad5686: create bus ops struct Rodrigo Alencar via B4 Relay
2026-05-05 12:59 ` [PATCH v6 00/12] Fixes and cleanups for the AD5686 IIO driver Andy Shevchenko
2026-05-05 14:29 ` Rodrigo Alencar
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=afoLFebe4fgNxXUV@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=455.rodrigo.alencar@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=gregkh@suse.de \
--cc=jic23@cam.ac.uk \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.auchter@ni.com \
--cc=rodrigo.alencar@analog.com \
--cc=stefan.popa@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