Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
Cc: linux-iio@vger.kernel.org,
	Marcelo Schmitt <marcelo.schmitt@analog.com>,
	robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v8 2/5] iio: adc: ltc2378: Add support for LTC2378-20 and similar ADCs
Date: Sun, 26 Jul 2026 20:07:38 +0100	[thread overview]
Message-ID: <20260726200738.0410749e@jic23-huawei> (raw)
In-Reply-To: <amN5Sw-EsciZCF1V@debian-BULLSEYE-live-builder-AMD64>

On Fri, 24 Jul 2026 11:40:11 -0300
Marcelo Schmitt <marcelo.schmitt1@gmail.com> wrote:

> On 07/23, sashiko-bot@kernel.org wrote:
> > Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> > - [Medium] The IIO scale factor exported for the LTC2338-18 is incorrect due to an unaccounted internal resistor divider (missing 2.5x multiplier).
> > --
> > 
> > --- Patch [2]: [PATCH v8 2/5] iio: adc: ltc2378: Add support for LTC2378-20 and similar ADCs ---
> > commit 79bd7cc98e49057401d7fb8d26685b9092c4787e
> > Author: Marcelo Schmitt <marcelo.schmitt@analog.com>
> > 
> > iio: adc: ltc2378: Add support for LTC2378-20 and similar ADCs
> > 
> > Support for LTC2378-20 and similar analog-to-digital converters.
> >   
> > > diff --git a/drivers/iio/adc/ltc2378.c b/drivers/iio/adc/ltc2378.c
> > > new file mode 100644
> > > index 0000000000000..107388f870626
> > > --- /dev/null
> > > +++ b/drivers/iio/adc/ltc2378.c  
> > [ ... ]  
> > > +static const struct ltc2378_chip_info ltc2338_18_chip_info = {
> > > +	.name = "ltc2338-18",
> > > +	.internal_ref_uV = 2048000,
> > > +	.chan = LTC2378_DIFF_CHANNEL(18),
> > > +};  
> > 
> > [Severity: Medium]
> > Does this chip info need a field to indicate the scale multiplier?
> > 
> > The LTC2338-18 has an internal resistor divider which acts as a 2.5x multiplier,
> > but this struct doesn't currently contain a way to specify it.  
> 
> I guess it makes sense. Might split support for this specific part into a
> separate patch to avoid it holding on the rest of the series in v9.

Works for me. 

J
> 


  reply	other threads:[~2026-07-26 19:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 19:51 [PATCH v8 0/5] iio: adc: Add support for LTC2378 and similar ADCs Marcelo Schmitt
2026-07-23 19:52 ` [PATCH v8 1/5] dt-bindings: iio: adc: Add ltc2378 Marcelo Schmitt
2026-07-23 19:52 ` [PATCH v8 2/5] iio: adc: ltc2378: Add support for LTC2378-20 and similar ADCs Marcelo Schmitt
     [not found]   ` <20260723200452.082871F00A3D@smtp.kernel.org>
2026-07-24 14:40     ` Marcelo Schmitt
2026-07-26 19:07       ` Jonathan Cameron [this message]
2026-07-23 19:52 ` [PATCH v8 3/5] iio: adc: ltc2378: Enable high-speed data capture Marcelo Schmitt
     [not found]   ` <20260723201317.B76B21F000E9@smtp.kernel.org>
2026-07-24 14:48     ` Marcelo Schmitt
2026-07-23 19:53 ` [PATCH v8 4/5] iio: adc: ltc2378: Enable triggered buffer " Marcelo Schmitt
2026-07-23 19:53 ` [PATCH v8 5/5] iio: ABI: Encourage differential voltage ABI usage Marcelo Schmitt
2026-07-26 19:12   ` 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=20260726200738.0410749e@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=marcelo.schmitt1@gmail.com \
    --cc=marcelo.schmitt@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