Devicetree
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Janani Sunil <janani.sunil@analog.com>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Olivier Moysan" <olivier.moysan@foss.st.com>,
	"Philipp Zabel" <p.zabel@pengutronix.de>,
	"Linus Walleij" <linusw@kernel.org>,
	"Bartosz Golaszewski" <brgl@kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	"Michael Walle" <mwalle@kernel.org>,
	linux@analog.com, linux-iio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org,
	jananisunil.dev@gmail.com,
	"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Subject: Re: [PATCH v4 06/14] iio: adc: ad7768: Add configurable sampling modes
Date: Mon, 24 Aug 2026 09:43:33 +0300	[thread overview]
Message-ID: <aovoFUBRRpZZPILZ@ashevche-desk.local> (raw)
In-Reply-To: <20260821-ad7768-driver-v4-6-bb8fbd06d4eb@analog.com>

On Fri, Aug 21, 2026 at 04:06:59PM +0200, Janani Sunil wrote:
> Derive the available output data rates from MCLK and expose per-channel
> sampling frequency and filter controls.
> 
> Select the fastest compatible power mode for the enabled channels and
> map matching sampling frequency and filter combinations onto the two
> hardware channel profiles. Configure the data clock divider and wait for
> the selected filters to settle before capture.

...

> -static int ad7768_configure_capture(struct ad7768_state *st)
> +static int ad7768_set_power_mode(struct ad7768_state *st, unsigned int mode)
>  {
> -	unsigned int dclk_div_reg;
> -	unsigned int mode_config;
> -	unsigned int dclk_div;
> +	unsigned int mode_idx;
>  	int ret;

> +	for (mode_idx = 0; mode_idx < ARRAY_SIZE(ad7768_power_modes);
> +	     mode_idx++) {

I would dare to put these on a single line.

> +		if (ad7768_power_modes[mode_idx].mode == mode)
> +			break;
> +	}
> +
> +	if (mode_idx == ARRAY_SIZE(ad7768_power_modes))
> +		return -EINVAL;

But this whole piece looks quite similar to
ad7768_freq_supported_in_any_mode(). Can that be refactored to cover
this and that cases?

...

> -static int ad7768_update_scan_mode(struct iio_dev *indio_dev,
> -				   const unsigned long *scan_mask)
> +static bool ad7768_freq_supported(const struct ad7768_state *st,
> +				  unsigned int mode_idx, unsigned int freq)

Can you try to make the patch changes cleaner in terms what is put where,
so we will see less of such a mess in the diff? Perhaps it will require
to split series even more.

> +{
> +	for (unsigned int i = 0;
> +	     i < st->avail_freq[mode_idx].n_freqs; i++) {

A single line.

> +		if (freq == st->avail_freq[mode_idx].freq_cfg[i].freq_hz)
> +			return true;
> +	}
> +
> +	return false;
> +}

...

> +		mask = ad7768_channel_mode_mask(st, c);
> +		ret = regmap_update_bits(st->regmap, AD7768_REG_CH_MODE_SEL,
> +					 mask, mode ? mask : 0);
> +		if (ret)
> +			return ret;

assign_bits()?

...

> +	for (unsigned int mode = 0; mode < AD7768_NUM_CHANNEL_MODES;
> +	     mode++) {

One line.

> +		unsigned int filter_config;
> +
> +		if (!mode_used[mode])
> +			continue;
> +
> +		ret = ad7768_set_mode_decimation(st, mode_freq[mode], mode);
> +		if (ret)
> +			return ret;
> +
> +		filter_config = FIELD_PREP(AD7768_CH_MODE_FILTER_TYPE_MSK,
> +					   mode_filter[mode]);
> +		ret = regmap_update_bits(st->regmap, AD7768_REG_CH_MODE(mode),
> +					 AD7768_CH_MODE_FILTER_TYPE_MSK,
> +					 filter_config);
> +		if (ret)
> +			return ret;
> +
> +		max_freq = max(max_freq, mode_freq[mode]);
> +	}

...

> +	/*
> +	 * Start in fast mode; capture setup may select another
> +	 * compatible mode.
> +	 */
> +	scoped_guard(mutex, &st->lock) {
> +		ret = ad7768_set_power_mode(st,
> +					    AD7768_POWER_MODE_POWER_MODE_FAST);
> +	}

> +	if (ret)
> +		return dev_err_probe(dev, ret, "Failed to set power mode\n");

Move this inside the {}.

>  static int ad7768_reset(struct ad7768_state *st)

...

Maybe it's only me, but this is completely unreviewable change (at least
by a human being). Please, refactor, split this to 5+ patches or so and
make each of them more or less reviewable.

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2026-08-24  6:43 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21 14:06 [PATCH v4 00/14] iio: adc: Add AD7768/AD7768-4 ADC driver support Janani Sunil
2026-08-21 14:06 ` [PATCH v4 01/14] iio: adc: adi-axi-adc: Initialize state mutex Janani Sunil
2026-08-23 18:52   ` Jonathan Cameron
2026-08-23 19:05     ` Jonathan Cameron
2026-08-21 14:06 ` [PATCH v4 02/14] dt-bindings: iio: adc: Add AD7768 Janani Sunil
2026-08-21 15:57   ` David Lechner
2026-08-23  1:45     ` Jonathan Cameron
2026-08-21 14:06 ` [PATCH v4 03/14] iio: backend: Add support for CRC Janani Sunil
2026-08-21 16:02   ` David Lechner
2026-08-21 14:06 ` [PATCH v4 04/14] iio: adc: adi-axi-adc: " Janani Sunil
2026-08-21 16:03   ` David Lechner
2026-08-21 14:06 ` [PATCH v4 05/14] iio: adc: Add AD7768 and AD7768-4 core support Janani Sunil
2026-08-22 17:30   ` David Lechner
2026-08-23  8:35     ` Andy Shevchenko
2026-08-23 19:16   ` Jonathan Cameron
2026-08-21 14:06 ` [PATCH v4 06/14] iio: adc: ad7768: Add configurable sampling modes Janani Sunil
2026-08-23 19:25   ` Jonathan Cameron
2026-08-24  6:43   ` Andy Shevchenko [this message]
2026-08-21 14:07 ` [PATCH v4 07/14] iio: adc: ad7768: Add calibration controls Janani Sunil
2026-08-24  6:50   ` Andy Shevchenko
2026-08-21 14:07 ` [PATCH v4 08/14] iio: adc: ad7768: Add per-channel conversion delay Janani Sunil
2026-08-24  7:10   ` Andy Shevchenko
2026-08-21 14:07 ` [PATCH v4 09/14] iio: adc: ad7768: Add VCM regulator support Janani Sunil
2026-08-24  7:13   ` Andy Shevchenko
2026-08-21 14:07 ` [PATCH v4 10/14] iio: adc: ad7768: Register GPIO auxiliary device Janani Sunil
2026-08-21 14:07 ` [PATCH v4 11/14] gpio: regmap: Use regmap_test_bits() for single bit reads Janani Sunil
2026-08-24  7:47   ` Andy Shevchenko
2026-08-21 14:07 ` [PATCH v4 12/14] gpio: regmap: Add optional runtime PM support Janani Sunil
2026-08-24  8:05   ` Andy Shevchenko
2026-08-21 14:07 ` [PATCH v4 13/14] gpio: ad7768: Add AD7768 GPIO auxiliary driver Janani Sunil
2026-08-23 19:39   ` Jonathan Cameron
2026-08-24  8:13     ` Andy Shevchenko
2026-08-24  8:10   ` Andy Shevchenko
2026-08-21 14:07 ` [PATCH v4 14/14] Documentation: iio: Add AD7768 Documentation Janani Sunil

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=aovoFUBRRpZZPILZ@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=brgl@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=janani.sunil@analog.com \
    --cc=jananisunil.dev@gmail.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@analog.com \
    --cc=mwalle@kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=olivier.moysan@foss.st.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=u.kleine-koenig@baylibre.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