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 4/5] iio: adc: ad4130: introduce chip info for future multidevice support
Date: Mon, 16 Mar 2026 17:23:50 +0200 [thread overview]
Message-ID: <abgghuhw01q9u90c@ashevche-desk.local> (raw)
In-Reply-To: <4ab83983026db04695e0a36a7103efbfb82f7a76.1773311639.git.Jonathan.Santos@analog.com>
On Mon, Mar 16, 2026 at 08:45:36AM -0300, Jonathan Santos wrote:
> Introduce a chip_info structure to abstract device-specific parameters
> and prepare the driver for supporting multiple AD4130 family variants.
...
> +struct ad4130_chip_info {
> + const char *name;
> + unsigned int max_analog_pins;
> + const struct iio_info *info;
> + const unsigned int *reg_size;
> + const unsigned int reg_size_length;
On (some) 64-bit architectures it might have unneeded gaps. Does `pahole` agree
with this layout?
> +};
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-03-16 15:23 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 [this message]
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
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=abgghuhw01q9u90c@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®