Devicetree
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Carlos Jones Jr <carlosjr.jones@analog.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"Liam Beguin" <liambeguin@gmail.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Tobias Sperling" <tobias.sperling@softing.com>,
	"Jorge Marques" <jorge.marques@analog.com>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Kyle Hsieh" <kylehsieh1995@gmail.com>
Subject: Re: [PATCH v2 0/4] Add support for LTC2305
Date: Wed, 25 Mar 2026 20:19:31 +0000	[thread overview]
Message-ID: <20260325201931.26ca84c1@jic23-huawei> (raw)
In-Reply-To: <20260324071331.842-1-carlosjr.jones@analog.com>

On Tue, 24 Mar 2026 15:13:27 +0800
Carlos Jones Jr <carlosjr.jones@analog.com> wrote:

> The LTC2305 is a 2-channel, 12-bit, fast ADC with an I2C interface,
> compatible with the LTC2309 (which has 8 channels).
> 
> This patch adds support for the LTC2305 by introducing a chip_info
> structure to handle the different channel configurations between the two
> variants. The LTC2305 exposes 2 single-ended channels and 2 differential
> combinations.
> 
> Also updates the device tree bindings to include the lltc,ltc2305
> compatible string and documents it in the Kconfig.
> ---

Whilst checking for what comments were in v1, I realized we have
two different people looking at the same thing within a few
weeks of each other. +cc Kyle. 

https://lore.kernel.org/all/20260325-add_ltc2305_driver-v5-0-e0d29daa54f9@gmail.com/#r

I guess this is just a case of neither noticing on the list?
Too many similar part names, so I missed it until now.

Currently I have Kyle's patches queued up.  All else being equal
that seems fair as Kyle started on this last year whereas 
Carlos' work on this is much more recent. 

I'm seeing some small differences. Please could you work together on this.
Ideally send any additional changes on top of Kyle's series.

Thanks,

Jonathan

> Changes in v2:
> - Changed usleep_range() to fsleep()
> - Added missing #include <linux/array_size.h> header
> - Removed explicit .read_delay_us = 0 initialization (implicit zero)
> - Added __counted_by_ptr() annotation to channels pointer
> - Modified ltc2309 struct to store only read_delay_us value instead
>   of full chip_info pointer, reducing memory overhead
> - Alphabetically ordered device entries in ID tables (ltc2305
>   before ltc2309)
> - Reformatted Kconfig help text with explicit bulleted list of
>   supported devices instead of vague "and similar" language
> - Added device names to chip_info structure for proper sysfs
>   identification
> - Split changes into proper preparatory patches before adding
>   new device support
> - Link to v1: https://lore.kernel.org/all/20260320140819.191700-1-carlosjr.jones@analog.com/
> 
> Note:
> The ltc2309_chip_info structure has a 4-byte hole due to alignment
> requirements for the __counted_by_ptr() annotation. The count field
> must precede the pointer field for the bounds checking to work correctly.
> The total structure size remains 32 bytes either way due to required
> padding, so the memory overhead is minimal (8 bytes total for both chip
> variants).
> ---
> Carlos Jones Jr (4):
>   iio: adc: ltc2309: Introduce chip_info structure
>   iio: adc: ltc2309: Use i2c_get_match_data() helper
>   dt-bindings: iio: adc: ltc2497: Add LTC2305 compatible
>   iio: adc: ltc2309: Add LTC2305 support
> 
>  .../bindings/iio/adc/lltc,ltc2497.yaml        |  9 ++-
>  drivers/iio/adc/Kconfig                       |  8 ++-
>  drivers/iio/adc/ltc2309.c                     | 59 ++++++++++++++++---
>  3 files changed, 65 insertions(+), 11 deletions(-)
> 


  parent reply	other threads:[~2026-03-25 20:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24  7:13 [PATCH v2 0/4] Add support for LTC2305 Carlos Jones Jr
2026-03-24  7:13 ` [PATCH v2 1/4] iio: adc: ltc2309: Introduce chip_info structure Carlos Jones Jr
2026-03-24 12:24   ` Andy Shevchenko
2026-03-25  0:01     ` Jones, Carlos jr
2026-03-24  7:13 ` [PATCH v2 2/4] iio: adc: ltc2309: Use i2c_get_match_data() helper Carlos Jones Jr
2026-03-24 12:35   ` Andy Shevchenko
2026-03-24  7:13 ` [PATCH v2 3/4] dt-bindings: iio: adc: ltc2497: Add LTC2305 compatible Carlos Jones Jr
2026-03-24 12:36   ` Krzysztof Kozlowski
2026-03-24  7:13 ` [PATCH v2 4/4] iio: adc: ltc2309: Add LTC2305 support Carlos Jones Jr
2026-03-24 12:39   ` Andy Shevchenko
2026-03-25 20:19 ` Jonathan Cameron [this message]
2026-03-26  2:21   ` [PATCH v2 0/4] Add support for LTC2305 Jones, Carlos jr
2026-03-26  8:17     ` Jonathan Cameron

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=20260325201931.26ca84c1@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=carlosjr.jones@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jorge.marques@analog.com \
    --cc=krzk+dt@kernel.org \
    --cc=kylehsieh1995@gmail.com \
    --cc=lars@metafoo.de \
    --cc=liambeguin@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=robh@kernel.org \
    --cc=tobias.sperling@softing.com \
    /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