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 v6 05/12] iio: dac: ds4424: use device match data for chip info
Date: Tue, 10 Feb 2026 16:50:26 +0200 [thread overview]
Message-ID: <aYtFsmO7h5ucSyVq@smile.fi.intel.com> (raw)
In-Reply-To: <20260210135110.2027073-6-o.rempel@pengutronix.de>
On Tue, Feb 10, 2026 at 02:51:03PM +0100, Oleksij Rempel wrote:
> Refactor the driver to use device match data instead of checking ID enums
> in a switch statement.
>
> Define a `ds4424_chip_info` structure to hold variant-specific attributes
> (currently just the channel count) and attach it directly to the I2C and
> OF device ID tables.
>
> This simplifies the probe function and makes it easier to add support for
> new variants like DS4402/DS4404.
Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-10 14:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 13:50 [PATCH v6 00/12] iio: dac: ds4424: add DS4402/DS4404 support and scale Oleksij Rempel
2026-02-10 13:50 ` [PATCH v6 01/12] iio: dac: ds4424: refactor raw access to use bitwise operations Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 02/12] iio: dac: ds4424: ratelimit read errors and use device context Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 03/12] iio: dac: ds4424: sort headers alphabetically Oleksij Rempel
2026-03-22 12:43 ` Jonathan Cameron
2026-02-10 13:51 ` [PATCH v6 04/12] iio: dac: ds4424: rename iio_info struct to avoid ambiguity Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 05/12] iio: dac: ds4424: use device match data for chip info Oleksij Rempel
2026-02-10 14:50 ` Andy Shevchenko [this message]
2026-02-10 13:51 ` [PATCH v6 06/12] iio: dac: ds4424: use fsleep() instead of usleep_range() Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 07/12] dt-bindings: iio: dac: maxim,ds4424: add ds4402/ds4404 Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 08/12] iio: dac: ds4424: add DS4402/DS4404 device IDs Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 09/12] iio: dac: ds4424: support per-variant output range limits Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 10/12] iio: dac: ds4424: convert to regmap Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 11/12] dt-bindings: iio: dac: maxim,ds4424: add maxim,rfs-ohms property Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 12/12] iio: dac: ds4424: add Rfs-based scale and per-variant limits Oleksij Rempel
2026-02-26 8:42 ` [PATCH v6 00/12] iio: dac: ds4424: add DS4402/DS4404 support and scale Oleksij Rempel
2026-02-26 10:08 ` Jonathan Cameron
2026-03-22 12:45 ` Jonathan Cameron
2026-03-22 17:22 ` 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=aYtFsmO7h5ucSyVq@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 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.