public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomas Melin <tomas.melin@vaisala.com>
To: "Nuno Sá" <noname.nuno@gmail.com>,
	"David Lechner" <dlechner@baylibre.com>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"Nuno Sa" <nuno.sa@analog.com>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Olivier Moysan" <olivier.moysan@foss.st.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/4] iio: industrialio-backend: support backend capabilities
Date: Tue, 3 Feb 2026 12:45:44 +0200	[thread overview]
Message-ID: <644c6549-e2e2-432f-aff9-48a37fcbb9b3@vaisala.com> (raw)
In-Reply-To: <fc350d2605ca6d95facec1a67858cb0ac22db917.camel@gmail.com>

Hi,

On 03/02/2026 12:01, Nuno Sá wrote:
> On Mon, 2026-02-02 at 15:04 +0200, Tomas Melin wrote:

>>
>> Yes, this is debatable. It's not necessarily always on, but should not
>> be enabled/touched by the frontend during probe.
>> But anyways, having a capability that says if the enable/disable feature
>> is available, is in any case useful and what I was planning on
>> leveraging in my use case.
>> Fundamentally, with the capabilites as now proposed, it is possible to
>> select what features of the ad9467 are available, in addition to the
>> basic requirements.
> 
> Yeah but this is just tweaking for your special case.

Actually goal for me is just to have the optional features of the
backend really optional. In a sense, it's tweaking for my use case but
at the same time it's making things work more generally.

That said, this always_on is not a showstopper for me. Since it seems
there is no real consensus over that capability, I can drop the
ALWAYS_ON for next version of the series.

Thanks,
Tomas


  reply	other threads:[~2026-02-03 10:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30  9:16 [PATCH v5 0/4] iio: adc: ad9467: Support alternative backends Tomas Melin
2026-01-30  9:16 ` [PATCH v5 1/4] iio: industrialio-backend: support backend capabilities Tomas Melin
2026-01-31 20:30   ` David Lechner
2026-02-02 10:28     ` Nuno Sá
2026-02-02 11:08       ` Tomas Melin
2026-02-02 12:40         ` Nuno Sá
2026-02-02 13:04           ` Tomas Melin
2026-02-02 15:50             ` David Lechner
2026-02-03  9:50               ` Tomas Melin
2026-02-04  1:07                 ` David Lechner
2026-02-04 11:15                   ` Tomas Melin
2026-02-03 10:01             ` Nuno Sá
2026-02-03 10:45               ` Tomas Melin [this message]
2026-02-02 10:58     ` Tomas Melin
2026-02-02 15:17       ` David Lechner
2026-01-30  9:17 ` [PATCH v5 2/4] iio: adc: adi-axi-adc: define supported iio-backend capabilities Tomas Melin
2026-02-02 10:33   ` Nuno Sá
2026-01-30  9:17 ` [PATCH v5 3/4] iio: dac: adi-axi-dac: " Tomas Melin
2026-02-02 10:33   ` Nuno Sá
2026-01-30  9:17 ` [PATCH v5 4/4] iio: adc: ad9467: check for backend capabilities Tomas Melin
2026-01-31 20:40   ` David Lechner
2026-02-02 11:18     ` Tomas Melin
2026-02-02 10:42   ` Nuno Sá
2026-02-02 12:03     ` Tomas Melin
2026-02-03  9:51       ` 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=644c6549-e2e2-432f-aff9-48a37fcbb9b3@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 \
    --cc=olivier.moysan@foss.st.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