From: "Nuno Sá" <noname.nuno@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>, 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 v9 6/7] iio: adc: ad9467: convert to backend framework
Date: Tue, 06 Feb 2024 17:51:29 +0100 [thread overview]
Message-ID: <f6ed72343be50c358db8e7e36d9afa875f788425.camel@gmail.com> (raw)
In-Reply-To: <CAHp75VeWV0+hqCoUb4YvfObnEAv0AaYJmXgpxJLfve+mBwhkyQ@mail.gmail.com>
On Tue, 2024-02-06 at 16:20 +0200, Andy Shevchenko wrote:
> On Tue, Feb 6, 2024 at 12:08 PM Nuno Sa via B4 Relay
> <devnull+nuno.sa.analog.com@kernel.org> wrote:
> >
> > From: Nuno Sa <nuno.sa@analog.com>
> >
> > 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.
> >
> > Giving the lack of features (and devices supported) in the ad9467 driver
>
> Given
>
> > 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 in transitioning
>
> support transitioning
>
> > to the backend framework.
>
> ...
>
> > - .max_rate = 250000000UL,
>
> > - .max_rate = 500000000UL,
>
> > - .max_rate = 125000000UL,
>
> ...
>
> > +static int ad9467_update_scan_mode(struct iio_dev *indio_dev,
> > + const unsigned long *scan_mask)
> > +{
> > + struct ad9467_state *st = iio_priv(indio_dev);
> > + unsigned int c;
> > + int ret;
> > +
> > + for (c = 0; c < st->info->num_channels; c++) {
> > + if (test_bit(c, scan_mask))
> > + ret = iio_backend_chan_enable(st->back, c);
> > + else
> > + ret = iio_backend_chan_disable(st->back, c);
>
> > +
>
> Unneeded blank line.
>
> > + if (ret)
> > + return ret;
> > + }
> > +
> > + return 0;
> > +}
>
> ....
>
> > + st->back = devm_iio_backend_get(&st->spi->dev, NULL);
> > + /* If not found, don't error out as we might have legacy DT property */
> > + if (!IS_ERR(st->back))
> > + return 0;
> > + if (PTR_ERR(st->back) != -ENOENT)
> > + return PTR_ERR(st->back);
>
> This looks hackish...
>
This was suggested by Jonathan so I'm keen in leaving it as-is
- Nuno Sá
next prev parent reply other threads:[~2024-02-06 16:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 10:08 [PATCH v9 0/7] iio: add new backend framework Nuno Sa via B4 Relay
2024-02-06 10:08 ` [PATCH v9 1/7] dt-bindings: adc: ad9467: add new io-backend property Nuno Sa via B4 Relay
2024-02-06 10:08 ` [PATCH v9 2/7] dt-bindings: adc: axi-adc: update bindings for backend framework Nuno Sa via B4 Relay
2024-02-06 10:08 ` [PATCH v9 3/7] of: property: add device link support for io-backends Nuno Sa via B4 Relay
2024-02-06 10:08 ` [PATCH v9 4/7] iio: buffer-dmaengine: export buffer alloc and free functions Nuno Sa via B4 Relay
2024-02-06 10:08 ` [PATCH v9 5/7] iio: add the IIO backend framework Nuno Sa via B4 Relay
2024-02-06 14:27 ` Andy Shevchenko
2024-02-07 9:16 ` Nuno Sá
2024-02-06 10:08 ` [PATCH v9 6/7] iio: adc: ad9467: convert to " Nuno Sa via B4 Relay
2024-02-06 14:20 ` Andy Shevchenko
2024-02-06 14:20 ` Andy Shevchenko
2024-02-06 16:52 ` Nuno Sá
2024-02-06 17:50 ` Andy Shevchenko
2024-02-07 12:08 ` Nuno Sá
2024-02-06 16:51 ` Nuno Sá [this message]
2024-02-06 17:51 ` Andy Shevchenko
2024-02-07 9:23 ` Nuno Sá
2024-02-10 16:31 ` Jonathan Cameron
2024-02-06 10:08 ` [PATCH v9 7/7] iio: adc: adi-axi-adc: move " Nuno Sa via B4 Relay
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=f6ed72343be50c358db8e7e36d9afa875f788425.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy.shevchenko@gmail.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