From: "Nuno Sá" <noname.nuno@gmail.com>
To: David Lechner <dlechner@baylibre.com>,
"Ceclan, Dumitru" <mitrutzceclan@gmail.com>,
dumitru.ceclan@analog.com
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 5/6] iio: adc: ad7173: Add support for AD411x devices
Date: Thu, 30 May 2024 08:19:57 +0200 [thread overview]
Message-ID: <d3c2496deb6a1764d06a63592b416d30d43fcc47.camel@gmail.com> (raw)
In-Reply-To: <30192c2a-5275-41ac-bc20-aa5f436846a3@baylibre.com>
On Wed, 2024-05-29 at 15:59 -0500, David Lechner wrote:
> On 5/29/24 9:03 AM, Ceclan, Dumitru wrote:
> > On 29/05/2024 15:46, Nuno Sá wrote:
> > > On Mon, 2024-05-27 at 20:02 +0300, Dumitru Ceclan via B4 Relay wrote:
> > > > From: Dumitru Ceclan <dumitru.ceclan@analog.com>
> >
> > ...
> >
> > > > static const struct ad7173_device_info ad7173_device_info[] = {
> > > > + [ID_AD4111] = {
> > > > + .name = "ad4111",
> > > > + .id = AD7173_AD4111_AD4112_AD4114_ID,
> > > > + .num_voltage_inputs_with_divider = 8,
> > > > + .num_channels = 16,
> > > > + .num_configs = 8,
> > > > + .num_voltage_inputs = 8,
> > > > + .num_gpios = 2,
> > > > + .higher_gpio_bits = true,
> > > > + .has_temp = true,
> > > > + .has_vcom_input = true,
> > > > + .has_input_buf = true,
> > > > + .has_current_inputs = true,
> > > > + .has_int_ref = true,
> > > > + .clock = 2 * HZ_PER_MHZ,
> > > > + .sinc5_data_rates = ad7173_sinc5_data_rates,
> > > > + .num_sinc5_data_rates = ARRAY_SIZE(ad7173_sinc5_data_rates),
> > > > + },
> > >
> > > At some point it would be nice to drop the ad7173_device_info array...
> > >
> > What are good alternatives to this?
>
> Drivers like ad7091r8 have individual static struct ad7091r_init_info
> instead of putting them all in an array. I like doing it that
> way because it makes less code to read compared to having the
> array.
>
> It would let us get rid of enum ad7173_ids, have one level less
> indent on each static const struct ad7173_device_info and
>
> { .compatible = "adi,ad7172-2", .data = &ad7173_device_info },
>
> would now fit on one line since we no longer need the array
> index.
>
Exactly... But up to you to do it now or defer it to a later patch.
- Nuno Sá
next prev parent reply other threads:[~2024-05-30 6:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 17:02 [PATCH v3 0/6] Add support for AD411x Dumitru Ceclan via B4 Relay
2024-05-27 17:02 ` [PATCH v3 1/6] dt-bindings: adc: ad7173: add support for ad411x Dumitru Ceclan via B4 Relay
2024-05-27 17:48 ` Conor Dooley
2024-05-28 12:16 ` Ceclan, Dumitru
2024-05-28 17:52 ` Conor Dooley
2024-05-29 13:38 ` Ceclan, Dumitru
2024-05-29 16:04 ` Conor Dooley
2024-05-30 7:50 ` Nuno Sá
2024-05-30 11:55 ` Ceclan, Dumitru
2024-05-29 22:04 ` David Lechner
2024-05-30 7:12 ` Nuno Sá
2024-05-27 17:02 ` [PATCH v3 2/6] iio: adc: ad7173: refactor channel configuration parsing Dumitru Ceclan via B4 Relay
2024-05-29 12:24 ` Nuno Sá
2024-05-27 17:02 ` [PATCH v3 3/6] iio: adc: ad7173: refactor ain and vref selection Dumitru Ceclan via B4 Relay
2024-05-29 12:27 ` Nuno Sá
2024-05-29 12:49 ` Nuno Sá
2024-05-30 14:45 ` Ceclan, Dumitru
2024-05-31 7:10 ` Nuno Sá
2024-06-01 18:40 ` Jonathan Cameron
2024-05-27 17:02 ` [PATCH v3 4/6] iio: adc: ad7173: add support for special inputs Dumitru Ceclan via B4 Relay
2024-05-29 12:29 ` Nuno Sá
2024-05-27 17:02 ` [PATCH v3 5/6] iio: adc: ad7173: Add support for AD411x devices Dumitru Ceclan via B4 Relay
2024-05-29 12:46 ` Nuno Sá
2024-05-29 14:03 ` Ceclan, Dumitru
2024-05-29 20:59 ` David Lechner
2024-05-30 6:19 ` Nuno Sá [this message]
2024-06-01 18:43 ` Jonathan Cameron
2024-05-27 17:02 ` [PATCH v3 6/6] iio: adc: ad7173: Reduce device info struct size Dumitru Ceclan via B4 Relay
2024-05-29 12:23 ` Nuno Sá
2024-05-29 20:32 ` David Lechner
2024-05-30 6:17 ` Nuno Sá
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=d3c2496deb6a1764d06a63592b416d30d43fcc47.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=dumitru.ceclan@analog.com \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mitrutzceclan@gmail.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;
as well as URLs for NNTP newsgroup(s).