From: David Lechner <dlechner@baylibre.com>
To: "Tomas Melin" <tomas.melin@vaisala.com>,
"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>,
"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 v3 2/4] iio: industrialio-backend: support backend capabilities
Date: Mon, 19 Jan 2026 09:00:06 -0600 [thread overview]
Message-ID: <69c4bf5a-e081-4660-a4ef-a92e9b081b41@baylibre.com> (raw)
In-Reply-To: <1f431375-f2cb-49a7-a0bd-6c00273a3c92@vaisala.com>
On 1/19/26 7:49 AM, Tomas Melin wrote:
...
>>> int iio_backend_chan_enable(struct iio_backend *back, unsigned int chan);
>>> @@ -235,6 +251,7 @@ int iio_backend_read_raw(struct iio_backend *back,
>>> long mask);
>>> int iio_backend_extend_chan_spec(struct iio_backend *back,
>>> struct iio_chan_spec *chan);
>>> +int iio_backend_has_caps(struct iio_backend *back, u32 caps);
>>
>> Not what David suggested and I do agree with him FWIW.
> AFAIU this was exactly what was suggested. Citing:
Slight difference. Should return bool instead of int.
>
>>> bool iio_backend_has_capabilities(struct iio_backend *back, u32 flags)
>>> (caps is fine too if we want to keep it short)
>
> Using the longer format is not very practical. Can we keep it as
> iio_backend_has_caps ?
Yes, I said as much already. But I guess you are asking Nuno. ;-)
next prev parent reply other threads:[~2026-01-19 15:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 10:45 [PATCH v3 0/4] iio: adc: ad9467: Support alternative backends Tomas Melin
2026-01-14 10:45 ` [PATCH v3 1/4] iio: adc: ad9467: include two's complement in default mode Tomas Melin
2026-01-16 18:39 ` Jonathan Cameron
2026-01-14 10:45 ` [PATCH v3 2/4] iio: industrialio-backend: support backend capabilities Tomas Melin
2026-01-14 12:20 ` Nuno Sá
2026-01-19 13:49 ` Tomas Melin
2026-01-19 15:00 ` David Lechner [this message]
2026-01-20 6:45 ` Tomas Melin
2026-01-14 12:28 ` Jonathan Cameron
2026-01-15 7:48 ` Tomas Melin
2026-01-14 13:19 ` Nuno Sá
2026-01-14 10:45 ` [PATCH v3 3/4] iio: adc: adi-axi-adc: define supported iio-backend capabilities Tomas Melin
2026-01-14 10:45 ` [PATCH v3 4/4] iio: adc: ad9467: check for backend capabilities Tomas Melin
2026-01-14 12:29 ` Nuno Sá
2026-01-14 15:23 ` Tomas Melin
2026-01-15 11:54 ` Nuno Sá
2026-01-16 18:32 ` Jonathan Cameron
2026-01-19 11:55 ` Tomas Melin
2026-01-14 12:45 ` Jonathan Cameron
2026-01-14 15:24 ` Tomas Melin
2026-01-14 13:38 ` Nuno Sá
2026-01-14 13:32 ` [PATCH v3 0/4] iio: adc: ad9467: Support alternative backends Nuno Sá
2026-01-14 15:32 ` Tomas Melin
2026-01-15 12:04 ` Nuno Sá
2026-01-15 13:30 ` Tomas Melin
2026-01-16 13:31 ` Nuno Sá
2026-01-16 18:37 ` Jonathan Cameron
2026-01-18 9:21 ` Nuno Sá
2026-01-20 11:01 ` Tomas Melin
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=69c4bf5a-e081-4660-a4ef-a92e9b081b41@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--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 \
--cc=tomas.melin@vaisala.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