Linux IIO development
 help / color / mirror / Atom feed
From: "Nuno Sá" <noname.nuno@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: David Lechner <dlechner@baylibre.com>,
	nuno.sa@analog.com,  linux-iio@vger.kernel.org,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	 Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH 4/8] iio: adc: ad9467: fix scale setting
Date: Mon, 11 Dec 2023 10:32:27 +0100	[thread overview]
Message-ID: <91aa6dde16434aaa3fbc30eeb8c944a89fca4983.camel@gmail.com> (raw)
In-Reply-To: <20231210112700.57fcdbf5@jic23-huawei>

On Sun, 2023-12-10 at 11:27 +0000, Jonathan Cameron wrote:
> On Thu, 07 Dec 2023 11:02:36 +0100
> Nuno Sá <noname.nuno@gmail.com> wrote:
> 
> > On Wed, 2023-12-06 at 17:01 -0600, David Lechner wrote:
> > > On Tue, Dec 5, 2023 at 11:06 AM Nuno Sa via B4 Relay
> > > <devnull+nuno.sa.analog.com@kernel.org> wrote:  
> > > > 
> > > > From: Nuno Sa <nuno.sa@analog.com>
> > > > 
> > > > When reading in_voltage_scale we can get something like:
> > > > 
> > > > root@analog:/sys/bus/iio/devices/iio:device2# cat in_voltage_scale
> > > > 0.038146
> > > > 
> > > > However, when reading the available options:
> > > > 
> > > > root@analog:/sys/bus/iio/devices/iio:device2# cat
> > > > in_voltage_scale_available
> > > > 2000.000000 2100.000006 2200.000007 2300.000008 2400.000009 2500.000010
> > > > 
> > > > which does not make sense. Moreover, when trying to set a new scale we
> > > > get an error because there's no call to __ad9467_get_scale() to give us
> > > > values as given when reading in_voltage_scale. Fix it by computing the
> > > > available scales during probe and properly pass the list when
> > > > .read_available() is called.
> > > > 
> > > > While at it, change to use .read_available() from iio_info. Also note
> > > > that to properly fix this, adi-axi-adc.c has to be changed accordingly.
> > > > 
> > > > Fixes: ad6797120238 ("iio: adc: ad9467: add support AD9467 ADC")
> > > > Signed-off-by: Nuno Sa <nuno.sa@analog.com>
> > > > ---
> > > >  drivers/iio/adc/ad9467.c            | 47 +++++++++++++++++++++++
> > > >  drivers/iio/adc/adi-axi-adc.c       | 74 ++++++++----------------------
> > > > -------
> > > >  include/linux/iio/adc/adi-axi-adc.h |  4 ++
> > > >  3 files changed, 66 insertions(+), 59 deletions(-)
> > > > 
> > > > diff --git a/drivers/iio/adc/ad9467.c b/drivers/iio/adc/ad9467.c
> > > > index badbef2ce9f8..3c8bd6c821a4 100644
> > > > --- a/drivers/iio/adc/ad9467.c
> > > > +++ b/drivers/iio/adc/ad9467.c
> > > > @@ -120,6 +120,7 @@ struct ad9467_state {
> > > >         struct spi_device               *spi;
> > > >         struct clk                      *clk;
> > > >         unsigned int                    output_mode;
> > > > +       unsigned int                    (*scales)[2];
> > > > 
> > > >         struct gpio_desc                *pwrdown_gpio;
> > > >         /* ensure consistent state obtained on multiple related accesses
> > > > */
> > > > @@ -216,6 +217,7 @@ static void __ad9467_get_scale(struct
> > > > adi_axi_adc_conv *conv,
> > > > int index,
> > > >         .channel = _chan,                                              
> > > > \
> > > >         .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE) |         
> > > > \
> > > >                 BIT(IIO_CHAN_INFO_SAMP_FREQ),                          
> > > > \
> > > > +       .info_mask_shared_by_type_available = BIT(IIO_CHAN_INFO_SCALE),
> > > > \
> > > >         .scan_index = _si,                                             
> > > > \
> > > >         .scan_type = {                                                 
> > > > \
> > > >                 .sign = _sign,                                         
> > > > \
> > > > @@ -370,6 +372,26 @@ static int ad9467_write_raw(struct adi_axi_adc_conv
> > > > *conv,
> > > >         }
> > > >  }
> > > > 
> > > > +static int ad9467_read_avail(struct adi_axi_adc_conv *conv,
> > > > +                            struct iio_chan_spec const *chan,
> > > > +                            const int **vals, int *type, int *length,
> > > > +                            long mask)
> > > > +{
> > > > +       const struct adi_axi_adc_chip_info *info = conv->chip_info;
> > > > +       struct ad9467_state *st = adi_axi_adc_conv_priv(conv);
> > > > +
> > > > +       switch (mask) {
> > > > +       case IIO_CHAN_INFO_SCALE:
> > > > +               *vals = (const int *)st->scales;
> > > > +               *type = IIO_VAL_INT_PLUS_MICRO;
> > > > +               /* Values are stored in a 2D matrix */
> > > > +               *length = info->num_scales * 2;  
> > > 
> > > Maybe use ARRAY_SIZE(*info->scales) here instead of hard-coding 2?  
> > 
> > Not to keen on that as the comment should already say everything about the
> > hardcoded
> > 2.
> > 
> I don't mind either way, but the comment only says it's a 2D matrix, not that
> the dimension
> is 2 * num_scales - it could easily be 14 * num_scales

Oops, totally right! For some reason I was seeing the comment as "2 columns" in
the matrix which is obviously not true (but I suspect that was the intent of the
comment)

- Nuno Sá


  reply	other threads:[~2023-12-11  9:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 17:06 [PATCH 0/8] iio: ad9467 and axi-adc cleanups Nuno Sa via B4 Relay
2023-12-05 17:06 ` [PATCH 1/8] iio: adc: ad9467: fix reset gpio handling Nuno Sa via B4 Relay
2023-12-06 18:03   ` Jonathan Cameron
2023-12-07  9:02     ` Nuno Sá
2023-12-06 22:09   ` David Lechner
2023-12-07  9:04     ` Nuno Sá
2023-12-05 17:06 ` [PATCH 2/8] iio: adc: ad9467: don't ignore error codes Nuno Sa via B4 Relay
2023-12-06 22:14   ` David Lechner
2023-12-05 17:06 ` [PATCH 3/8] iio: adc: ad9467: add mutex to struct ad9467_state Nuno Sa via B4 Relay
2023-12-06 22:27   ` David Lechner
2023-12-07  9:10     ` Nuno Sá
2023-12-05 17:06 ` [PATCH 4/8] iio: adc: ad9467: fix scale setting Nuno Sa via B4 Relay
2023-12-06 23:01   ` David Lechner
2023-12-07  9:21     ` Nuno Sá
2023-12-07 10:02     ` Nuno Sá
2023-12-10 11:27       ` Jonathan Cameron
2023-12-11  9:32         ` Nuno Sá [this message]
2023-12-05 17:06 ` [PATCH 5/8] iio: adc: ad9467: use spi_get_device_match_data() Nuno Sa via B4 Relay
2023-12-06 23:03   ` David Lechner
2023-12-05 17:06 ` [PATCH 6/8] iio: adc: ad9467: use chip_info variables instead of array Nuno Sa via B4 Relay
2023-12-06 23:10   ` David Lechner
2023-12-05 17:06 ` [PATCH 7/8] iio: adc: ad9467: use the more common !val NULL check Nuno Sa via B4 Relay
2023-12-06 23:11   ` David Lechner
2023-12-05 17:06 ` [PATCH 8/8] iio: adc: adi-axi-adc: convert to regmap Nuno Sa via B4 Relay
2023-12-06 18:05   ` Jonathan Cameron
2023-12-06 23:18   ` David Lechner

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=91aa6dde16434aaa3fbc30eeb8c944a89fca4983.camel@gmail.com \
    --to=noname.nuno@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox