devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Nuno Sa <nuno.sa@analog.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	 Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	 Jonathan Cameron <jic23@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	 Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Frank Rowand <frowand.list@gmail.com>,
	Olivier Moysan <olivier.moysan@foss.st.com>
Subject: Re: [PATCH v10 6/7] iio: adc: ad9467: convert to backend framework
Date: Fri, 9 Feb 2024 18:37:21 +0200	[thread overview]
Message-ID: <CAHp75Vd0qcJiw7EPsSjLAG1G8RFymFuRif7FY2YVTBPK9M2KJQ@mail.gmail.com> (raw)
In-Reply-To: <20240209-iio-backend-v10-6-3ed842064318@analog.com>

On Fri, Feb 9, 2024 at 5:26 PM Nuno Sa <nuno.sa@analog.com> wrote:
>
> Convert the driver to use the new IIO backend framework. The device
> functionality is expected to be the same (meaning no added or removed
> features).
>
> Also note this patch effectively breaks ABI and that's needed so we can
> properly support this device and add needed features making use of the
> new IIO framework.
>
> Given the lack of features (and devices supported) in the ad9467 driver
> compared with the ADI out of tree version, we don't expect any user of
> the upstream driver so no one should notice the ABI breakage. However,
> if someone is affected by this, ADI will happily support transitioning
> to the backend framework.

...

>  struct ad9467_chip_info {
> -       struct adi_axi_adc_chip_info    axi_adc_info;
> -       unsigned int                    default_output_mode;
> -       unsigned int                    vref_mask;
> +       const char              *name;
> +       unsigned int            id;
> +       const struct            iio_chan_spec *channels;
> +       unsigned int            num_channels;
> +       const unsigned int      (*scale_table)[2];
> +       int                     num_scales;
> +       unsigned long           max_rate;
> +       unsigned int            default_output_mode;
> +       unsigned int            vref_mask;
>  };

Seems like you haven't checked this layout with `pahole`.

...

> +static int ad9467_iio_backend_get(struct ad9467_state *st)
> +{
> +       struct device *dev = &st->spi->dev;
> +       struct device_node *__back;
> +
> +       st->back = devm_iio_backend_get(&st->spi->dev, NULL);

Simply 'dev' as the first parameter?

...

> +       /* If not found, don't error out as we might have legacy DT property */

This seems related to ENOENT, correct?

> +       if (!IS_ERR(st->back))
> +               return 0;

And the above is about something else (found?) case, right?

> +       if (PTR_ERR(st->back) != -ENOENT)
> +               return PTR_ERR(st->back);

--
With Best Regards,
Andy Shevchenko

  reply	other threads:[~2024-02-09 16:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 15:28 [PATCH v10 0/7] iio: add new backend framework Nuno Sa
2024-02-09 15:28 ` [PATCH v10 1/7] dt-bindings: adc: ad9467: add new io-backend property Nuno Sa
2024-02-09 15:28 ` [PATCH v10 2/7] dt-bindings: adc: axi-adc: update bindings for backend framework Nuno Sa
2024-02-09 15:28 ` [PATCH v10 3/7] of: property: add device link support for io-backends Nuno Sa
2024-02-09 15:28 ` [PATCH v10 4/7] iio: buffer-dmaengine: export buffer alloc and free functions Nuno Sa
2024-02-09 15:28 ` [PATCH v10 5/7] iio: add the IIO backend framework Nuno Sa
2024-02-09 16:19   ` Andy Shevchenko
2024-02-09 16:30   ` Andy Shevchenko
2024-02-10 16:41     ` Jonathan Cameron
2024-02-10 16:45       ` Andy Shevchenko
2024-02-09 15:28 ` [PATCH v10 6/7] iio: adc: ad9467: convert to " Nuno Sa
2024-02-09 16:37   ` Andy Shevchenko [this message]
2024-02-10 20:58     ` Nuno Sá
2024-02-09 15:28 ` [PATCH v10 7/7] iio: adc: adi-axi-adc: move " Nuno Sa
2024-02-09 16:45   ` Andy Shevchenko
2024-02-10 20:58     ` Nuno Sá
2024-02-09 16:46 ` [PATCH v10 0/7] iio: add new " Andy Shevchenko

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=CAHp75Vd0qcJiw7EPsSjLAG1G8RFymFuRif7FY2YVTBPK9M2KJQ@mail.gmail.com \
    --to=andy.shevchenko@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=jic23@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=olivier.moysan@foss.st.com \
    --cc=robh+dt@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).