public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	"Andy Shevchenko" <andy@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"David Jander" <david@protonic.nl>
Subject: Re: [PATCH v1 5/8] iio: dac: ds4424: add Rfs-based scale and per-variant limits
Date: Mon, 19 Jan 2026 21:11:23 +0200	[thread overview]
Message-ID: <aW6B22-nMF1EfGmE@smile.fi.intel.com> (raw)
In-Reply-To: <20260119182424.1660601-6-o.rempel@pengutronix.de>

On Mon, Jan 19, 2026 at 07:24:21PM +0100, Oleksij Rempel wrote:
> Parse optional maxim,rfs-ohms values to derive the per-channel output
> current scale (mA per step) for the IIO current ABI.
> 
> Select per-variant parameters to match the shared register map while
> handling different data widths and full-scale current calculations.
> 
> Behavior changes:
> - If maxim,rfs-ohms is present, IIO_CHAN_INFO_SCALE becomes available
>   and reports mA/step derived from Rfs.
> - If maxim,rfs-ohms is missing, SCALE is not exposed to keep older DTs
>   working without requiring updates.
> - RAW writes are now limited to the representable sign-magnitude range
>   of the detected variant to avoid silent truncation (e.g. +/-31 on
>   DS440x).

...

> +struct ds4424_chip_info {
> +	u8 result_mask;
> +	int vref_mv;
> +	int scale_denom;

Wondering if `pahole` is fine with the proposed layout.
Otherwise I would move u8 to the end.

> +};

...

> +static const struct ds4424_chip_info ds4424_info = {
> +	.result_mask = 0x7F,

GENMASK() ?
(Note, we also have GENMASK_U8() IIRC)

> +	.vref_mv = 976,
> +	.scale_denom = 16,
> +};

...

> +/* DS4402 is handled like DS4404 (same resolution and scale formula). */
> +static const struct ds4424_chip_info ds4404_info = {
> +	.result_mask = 0x1F,

Ditto.

> +	.vref_mv = 1230,
> +	.scale_denom = 4,
> +};

...

> -		if (val <= S8_MIN || val > S8_MAX)
> +		/*
> +		 * The hardware uses sign-magnitude representation (not
> +		 * two's complement). Therefore, the range is symmetric:
> +		 * [-max_val, +max_val].
> +		 */
> +		if (val < -max_val || val > max_val)
>  			return -EINVAL;

Right, cool, but I still think even in the fix it would be good to fix that and
here it will be quite logical and clear change. Maybe even introduce a comment
in the fix-patch and just update limits here.

...

> +static int ds4424_setup_channels(struct i2c_client *client,
> +				 struct ds4424_data *data,
> +				 struct iio_dev *indio_dev)
> +{
> +	struct iio_chan_spec channels[DS4424_MAX_DAC_CHANNELS];
> +	size_t channels_size;
> +	int i;
> +
> +	channels_size = indio_dev->num_channels * sizeof(*channels);

Sounds like devm_kmemdup_array() to me...

> +	memcpy(channels, ds4424_channels, channels_size);

> +	/* Enable scale only when rfs is available. */
> +	if (data->has_rfs) {
> +		for (i = 0; i < indio_dev->num_channels; i++)
> +			channels[i].info_mask_separate |=
> +				BIT(IIO_CHAN_INFO_SCALE);
> +	}

Can be done after kmemdup(), right?

> +	indio_dev->channels = devm_kmemdup(&client->dev, channels,
> +					   channels_size, GFP_KERNEL);
> +	if (!indio_dev->channels)
> +		return -ENOMEM;
> +
> +	return 0;
> +}

...

> +static int ds4424_parse_rfs(struct i2c_client *client,
> +			    struct ds4424_data *data,
> +			    struct iio_dev *indio_dev)
> +{

	struct device *dev = &client->dev;

> +	int count, i, ret;
> +
> +	if (!device_property_present(&client->dev, "maxim,rfs-ohms")) {
> +		dev_info_once(&client->dev, "maxim,rfs-ohms missing, scale not supported\n");
> +		return 0;
> +	}
> +
> +	count = device_property_count_u32(&client->dev, "maxim,rfs-ohms");
> +	if (count != indio_dev->num_channels) {
> +		dev_err(&client->dev,
> +			"maxim,rfs-ohms must have %u entries\n",
> +			indio_dev->num_channels);
> +		return -EINVAL;
> +	}
> +
> +	ret = device_property_read_u32_array(&client->dev,
> +					     "maxim,rfs-ohms",
> +					     data->rfs_ohms,
> +					     indio_dev->num_channels);
> +	if (ret) {
> +		dev_err(&client->dev,
> +			"Failed to read maxim,rfs-ohms property\n");
> +		return ret;
> +	}
> +
> +	for (i = 0; i < indio_dev->num_channels; i++) {
> +		if (!data->rfs_ohms[i]) {

> +			dev_err(&client->dev,
> +				"maxim,rfs-ohms entry %d is zero\n",
> +				i);

> +			return -EINVAL;

This is only for probe stage, right?

Then

			return dev_err_probe();

?

> +		}
> +	}
> +
> +	data->has_rfs = true;
> +	return 0;
> +}

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-01-19 19:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19 18:24 [PATCH v1 0/8] iio: dac: ds4424: add DS4402/DS4404 support and scale Oleksij Rempel
2026-01-19 18:24 ` [PATCH v1 1/8] dt-bindings: iio: dac: maxim,ds4424: add ds4402/ds4404 Oleksij Rempel
2026-01-19 18:28   ` Conor Dooley
2026-01-19 18:24 ` [PATCH v1 2/8] dt-bindings: iio: dac: maxim,ds4424: add maxim,rfs-ohms property Oleksij Rempel
2026-01-19 18:27   ` Conor Dooley
2026-01-23  9:28     ` Jonathan Cameron
2026-01-23 10:03       ` Oleksij Rempel
2026-01-25 10:22         ` Jonathan Cameron
2026-01-26  9:54           ` Oleksij Rempel
2026-01-20 10:39   ` Krzysztof Kozlowski
2026-01-19 18:24 ` [PATCH v1 3/8] iio: dac: ds4424: add DS4402/DS4404 device IDs Oleksij Rempel
2026-01-19 18:24 ` [PATCH v1 4/8] iio: dac: ds4424: reject -128 RAW value Oleksij Rempel
2026-01-19 19:03   ` Andy Shevchenko
2026-01-23  9:33     ` Jonathan Cameron
2026-01-26  9:52       ` Oleksij Rempel
2026-01-19 18:24 ` [PATCH v1 5/8] iio: dac: ds4424: add Rfs-based scale and per-variant limits Oleksij Rempel
2026-01-19 19:11   ` Andy Shevchenko [this message]
2026-01-19 18:24 ` [PATCH v1 6/8] iio: dac: ds4424: clear outputs on probe Oleksij Rempel
2026-01-19 19:12   ` Andy Shevchenko
2026-01-23  9:38   ` Jonathan Cameron
2026-01-23  9:59     ` Oleksij Rempel
2026-01-19 18:24 ` [PATCH v1 7/8] iio: dac: ds4424: ratelimit read errors and use device context Oleksij Rempel
2026-01-19 19:14   ` Andy Shevchenko
2026-01-19 18:24 ` [PATCH v1 8/8] iio: dac: ds4424: document output sign and probe verification Oleksij Rempel

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=aW6B22-nMF1EfGmE@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=david@protonic.nl \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=o.rempel@pengutronix.de \
    --cc=robh@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