All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Manni <stefano.manni@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
	dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: ad799x: add reference supply for ad7994
Date: Wed, 06 Aug 2025 11:03:45 +0200	[thread overview]
Message-ID: <9IEK0T.R3JGMPI97ET21@gmail.com> (raw)
In-Reply-To: <CAHp75VfCL88GMSRYnJ+wh85Yj_RrBztSLWOvQJTapVdgFerMyg@mail.gmail.com>

Hi Andy,

On mar, ago 5 2025 at 15:13:06 +02:00:00, Andy Shevchenko 
<andy.shevchenko@gmail.com> wrote:
> On Tue, Aug 5, 2025 at 2:28 PM Stefano Manni 
> <stefano.manni@gmail.com> wrote:
>> 
>>  AD7994 supports the external reference voltage on pin REFIN.
> 
> ...
> 
>>  -               if ((st->id == ad7991) || (st->id == ad7995) || 
>> (st->id == ad7999)) {
>>  +               if ((st->id == ad7991) || (st->id == ad7995) || 
>> (st->id == ad7999)
>>  +                       (st->id == ad7994)) {
> 
> Instead of making this conditional longer and uglier, it is better to
> add a boolean field to chip_info and just check it instead. This will
> remove the churn when any new chip will require the same change in the
> future.
> 
> So, please make it two patches:
> - introducing a field in chip_info and use it for the existing cases
> - add this field to be true for the ad7994 case.
> 
> Is it doable?
> 

Yes, it is. A patch series is coming.

> --
> With Best Regards,
> Andy Shevchenko



  parent reply	other threads:[~2025-08-06  7:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-05 14:24 [PATCH] iio: adc: ad799x: add reference supply for ad7994 Stefano Manni
2025-08-05 13:13 ` Andy Shevchenko
2025-08-05 16:13   ` Nuno Sá
2025-08-06  9:03   ` Stefano Manni [this message]
2025-08-06 15:22 ` kernel test robot

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=9IEK0T.R3JGMPI97ET21@gmail.com \
    --to=stefano.manni@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.