From: Tomas Melin <tomas.melin@vaisala.com>
To: "Nuno Sá" <noname.nuno@gmail.com>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sa" <nuno.sa@analog.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Andy Shevchenko" <andy@kernel.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] iio: adc: ad9467: make iio backend optional
Date: Fri, 19 Dec 2025 13:25:17 +0200 [thread overview]
Message-ID: <df70028b-49a5-4004-a534-e1451d581dda@vaisala.com> (raw)
In-Reply-To: <055f9c79ab40a8a72e69b7c9cfa2a64292377f5e.camel@gmail.com>
Hi,
On 18/12/2025 15:41, Nuno Sá wrote:
> On Wed, 2025-12-17 at 13:44 +0200, Tomas Melin wrote:
>> [resend, I think there was some problem with my first reply]
>>
>> Hi,
>>
>> On 17/12/2025 11:26, Nuno Sá wrote:
>>> On Tue, 2025-12-16 at 15:39 +0000, Tomas Melin wrote:
>
> The above is indeed cumbersome. I guess dummy is not what we would need but something
> like a fixed-backend that would implement all the ops in a dummy way. But that does not
> make much sense and doesn't really scale.
>
> I think my main complain is also that then we should add a devm_backend_get_optional() to make
> the intent clear but unfortunately this driver is not the best candidate for that.
>
> Anyways, I still don't love the idea of just ignoring it (given that some HW is indeed present)
> but yeah. Not going to nack it either.
Good that you still see the optional backend as feasible. I will tune
the implementation in next version according to discussion in our other
thread and other possible feeback that comes up. I'm confident we can
find a solution that will work out nicely.
Thanks,
Tomas
>
> - Nuno Sá
>
next prev parent reply other threads:[~2025-12-19 11:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 11:40 [PATCH 0/2] iio: adc: ad9467: Enable operation without iio-backend Tomas Melin
2025-12-16 11:40 ` [PATCH 1/2] iio: adc: ad9467: include two's complement in default mode Tomas Melin
2025-12-18 13:43 ` Nuno Sá
2025-12-20 3:28 ` kernel test robot
2025-12-20 5:13 ` kernel test robot
2025-12-21 19:54 ` Jonathan Cameron
2025-12-16 11:40 ` [PATCH 2/2] iio: adc: ad9467: make iio backend optional Tomas Melin
2025-12-16 12:56 ` Nuno Sá
2025-12-16 15:39 ` Tomas Melin
2025-12-16 21:27 ` David Lechner
2025-12-17 5:38 ` Tomas Melin
2025-12-17 9:26 ` Nuno Sá
2025-12-17 10:39 ` Tomas Melin
2025-12-17 11:44 ` Tomas Melin
2025-12-18 13:41 ` Nuno Sá
2025-12-19 11:25 ` Tomas Melin [this message]
2025-12-18 13:49 ` Nuno Sá
2025-12-19 11:16 ` Tomas Melin
2025-12-19 14:46 ` Nuno Sá
2025-12-21 20:00 ` Jonathan Cameron
2026-01-05 11:06 ` Tomas Melin
2026-01-05 14:57 ` Nuno Sá
2026-01-11 11:41 ` Jonathan Cameron
2026-01-12 13:21 ` Nuno Sá
2026-01-13 7:47 ` Tomas Melin
2026-01-13 10:00 ` Jonathan Cameron
2026-01-13 10:52 ` Nuno Sá
2026-01-13 11:49 ` Tomas Melin
2026-01-13 12:44 ` Nuno Sá
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=df70028b-49a5-4004-a534-e1451d581dda@vaisala.com \
--to=tomas.melin@vaisala.com \
--cc=Michael.Hennerich@analog.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=noname.nuno@gmail.com \
--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