From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Jonathan Santos <Jonathan.Santos@analog.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, lars@metafoo.de,
Michael.Hennerich@analog.com, cosmin.tanislav@analog.com,
jic23@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
andy@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Subject: Re: [PATCH v2 5/5] iio: adc: ad4130: add new supported parts
Date: Mon, 16 Mar 2026 18:10:02 +0200 [thread overview]
Message-ID: <abgrWnV8G47W2_Mi@ashevche-desk.local> (raw)
In-Reply-To: <9295ce0b3376481bf8530d1c53bb77a70e8761d1.1773311639.git.Jonathan.Santos@analog.com>
On Mon, Mar 16, 2026 at 08:45:45AM -0300, Jonathan Santos wrote:
> Add support for AD4129-4/8, AD4130-4, and AD4131-4/8 variants.
>
> The AD4129 series supports the same FIFO interface as the AD4130 but with
> reduced resolution (16-bit). The AD4131 series lacks FIFO support, so
> triggered buffer functionality is introduced.
>
> The 4-channel variants feature fewer analog inputs, GPIOs, and sparse pin
> mappings for VBIAS, analog inputs, and excitation currents. The driver now
> handles these differences with chip-specific configurations, including pin
> mappings and GPIO counts.
...
> +/* Map logical pins to register value */
> +static const u8 ad4130_4_pin_map[] = {
> + 0x00, /* AIN0/VBIAS_0 */
> + 0x01, /* AIN1/VBIAS_1 */
> + 0x04, /* AIN2/VBIAS_2 */
> + 0x05, /* AIN3/VBIAS_3 */
> + 0x0A, /* AIN4/VBIAS_4 */
> + 0x0B, /* AIN5/VBIAS_5 */
> + 0x0E, /* AIN6/VBIAS_6 */
> + 0x0F, /* AIN7/VBIAS_7 */
> +};
> +
> +/* Pin mapping for AIN0..AIN15, VBIAS_0..VBIAS_15 */
Perhaps making the above also consistent with this?
/* Pin mapping for AIN0..AIN7, VBIAS_0..VBIAS_7 */
static const u8 ad4130_4_pin_map[] = {
0x00, 0x01, 0x04, 0x05, 0x0A, 0x0B, 0x0E, 0x0F, /* 0 - 7 */
};
> +static const u8 ad4130_8_pin_map[] = {
> + 0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, /* 0 - 7 */
> + 0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, /* 8 - 15 */
> +};
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-03-16 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 11:44 [PATCH v2 0/5] Add support for AD4129-4/8, AD4130-4, and AD4131-4/8 Jonathan Santos
2026-03-16 11:45 ` [PATCH v2 1/5] dt-bindings: iio: adc: ad4130: Document interrupts property Jonathan Santos
2026-03-17 7:22 ` Krzysztof Kozlowski
2026-03-16 11:45 ` [PATCH v2 2/5] dt-bindings: iio: adc: ad4130: Add new supported parts Jonathan Santos
2026-03-16 11:45 ` [PATCH v2 3/5] iio: adc: ad4130: Add SPI device ID table Jonathan Santos
2026-03-16 15:21 ` Andy Shevchenko
2026-03-16 11:45 ` [PATCH v2 4/5] iio: adc: ad4130: introduce chip info for future multidevice support Jonathan Santos
2026-03-16 15:23 ` Andy Shevchenko
2026-03-16 11:45 ` [PATCH v2 5/5] iio: adc: ad4130: add new supported parts Jonathan Santos
2026-03-16 16:10 ` Andy Shevchenko [this message]
2026-03-21 19:08 ` Jonathan Cameron
2026-03-16 16:11 ` [PATCH v2 0/5] Add support for AD4129-4/8, AD4130-4, and AD4131-4/8 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=abgrWnV8G47W2_Mi@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=Jonathan.Santos@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cosmin.tanislav@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--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
all inboxes | Powered by JetHome®