All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Rodrigo Alencar via B4 Relay"
	<devnull+rodrigo.alencar.analog.com@kernel.org>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 12/12] iio: dac: ad5686: add gain control support
Date: Tue, 16 Jun 2026 08:34:06 +0000	[thread overview]
Message-ID: <20260616083406.987B21F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260616-ad5686-new-features-v3-12-f829fb7e9262@analog.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The GAIN GPIO is unconditionally requested as driven low, causing a potential DAC output glitch during probe.
--

commit 2f56ef5391a1b46c707191ed6f4562758e4e5acc
Author: Rodrigo Alencar <rodrigo.alencar@analog.com>

iio: dac: ad5686: add gain control support

This commit adds gain control support to the AD5686 DAC driver. It handles
gain multiplication either via an external hardware GAIN pin or through
internal control register bits, initializing the default scale based on
device properties.

> diff --git a/drivers/iio/dac/ad5686.c b/drivers/iio/dac/ad5686.c
> index 6ae788f665b4d..c186213a46f6d 100644
> --- a/drivers/iio/dac/ad5686.c
> +++ b/drivers/iio/dac/ad5686.c
[ ... ]
> @@ -579,6 +681,14 @@ int ad5686_probe(struct device *dev,
>  		return dev_err_probe(dev, PTR_ERR(st->ldac_gpio),
>  				     "Failed to get LDAC GPIO\n");
>  
> +	st->gain_gpio = devm_gpiod_get_optional(dev, "gain", GPIOD_OUT_LOW);
> +	if (IS_ERR(st->gain_gpio))
> +		return dev_err_probe(dev, PTR_ERR(st->gain_gpio),
> +				     "Failed to get GAIN GPIO\n");
> +
> +	st->double_scale = device_property_read_bool(dev, "adi,range-double");

[Severity: Medium]
Could this cause an unwanted glitch on the analog output during probe?

If the system is warm-booted and the DAC is already outputting voltage with
a 2x gain, unconditionally forcing the gain pin low here will abruptly halve
the output voltage before the device is reset or the pin is corrected later in
the probe sequence.

Would it be safer to read the adi,range-double property before requesting the
GPIO, so that the pin can be initialized to its correct target state without
the temporary drop to 1x gain?

> +	ad5686_init_scale_avail(st);
> +
>  	reset_control_assert(rstc);
>  	fsleep(1); /* reset pulse: comfortably bigger than the spec */
>  	reset_control_deassert(rstc);

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260616-ad5686-new-features-v3-0-f829fb7e9262@analog.com?part=12

  reply	other threads:[~2026-06-16  8:34 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16  8:21 [PATCH v3 00/12] New features for the AD5686 IIO driver Rodrigo Alencar via B4 Relay
2026-06-16  8:21 ` Rodrigo Alencar
2026-06-16  8:21 ` [PATCH v3 01/12] dt-bindings: iio: dac: ad5696: add reset/ldac/gain support Rodrigo Alencar via B4 Relay
2026-06-16  8:21   ` Rodrigo Alencar
2026-06-16  8:32   ` sashiko-bot
2026-06-16 12:48   ` Rob Herring
2026-06-16  8:21 ` [PATCH v3 02/12] dt-bindings: iio: dac: ad5696: rework on power supplies Rodrigo Alencar via B4 Relay
2026-06-16  8:21   ` Rodrigo Alencar
2026-06-16 12:50   ` Rob Herring
2026-06-16  8:21 ` [PATCH v3 03/12] dt-bindings: iio: dac: ad5686: add reset/ldac/gain support Rodrigo Alencar via B4 Relay
2026-06-16  8:21   ` Rodrigo Alencar
2026-06-16  8:35   ` sashiko-bot
2026-06-16  8:21 ` [PATCH v3 04/12] dt-bindings: iio: dac: ad5686: rework on power supplies Rodrigo Alencar via B4 Relay
2026-06-16  8:21   ` Rodrigo Alencar
2026-06-16  8:33   ` sashiko-bot
2026-06-16  8:21 ` [PATCH v3 05/12] iio: dac: ad5686: add support for missing " Rodrigo Alencar via B4 Relay
2026-06-16  8:21   ` Rodrigo Alencar
2026-06-16  9:33   ` Joshua Crofts
2026-06-16 10:29     ` Andy Shevchenko
2026-06-16  8:21 ` [PATCH v3 06/12] iio: dac: ad5686: consume optional reset signal Rodrigo Alencar via B4 Relay
2026-06-16  8:21   ` Rodrigo Alencar
2026-06-16  8:30   ` sashiko-bot
2026-06-16 10:30   ` Andy Shevchenko
2026-06-16  8:21 ` [PATCH v3 07/12] iio: dac: ad5686: add ldac gpio Rodrigo Alencar via B4 Relay
2026-06-16  8:21   ` Rodrigo Alencar
2026-06-16 10:32   ` Andy Shevchenko
2026-06-16  8:21 ` [PATCH v3 08/12] iio: dac: ad5686: introduce sync operation Rodrigo Alencar via B4 Relay
2026-06-16  8:21   ` Rodrigo Alencar
2026-06-16  8:21 ` [PATCH v3 09/12] iio: dac: ad5686: implement new sync() op for the spi bus Rodrigo Alencar via B4 Relay
2026-06-16  8:21   ` Rodrigo Alencar
2026-06-16 10:35   ` Andy Shevchenko
2026-06-16  8:21 ` [PATCH v3 10/12] iio: dac: ad5686: add triggered buffer support Rodrigo Alencar via B4 Relay
2026-06-16  8:21   ` Rodrigo Alencar
2026-06-16 10:42   ` Andy Shevchenko
2026-06-16  8:21 ` [PATCH v3 11/12] iio: dac: ad5686: read_raw/write_raw: use guard(mutex)() Rodrigo Alencar via B4 Relay
2026-06-16  8:21   ` Rodrigo Alencar
2026-06-16 10:43   ` Andy Shevchenko
2026-06-16 10:50     ` Rodrigo Alencar
2026-06-16 10:52       ` Andy Shevchenko
2026-06-16 11:00         ` Rodrigo Alencar
2026-06-16  8:21 ` [PATCH v3 12/12] iio: dac: ad5686: add gain control support Rodrigo Alencar via B4 Relay
2026-06-16  8:21   ` Rodrigo Alencar
2026-06-16  8:34   ` sashiko-bot [this message]
2026-06-16 10:47   ` Andy Shevchenko

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=20260616083406.987B21F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=devnull+rodrigo.alencar.analog.com@kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.