[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <69c4bf5a-e081-4660-a4ef-a92e9b081b41@baylibre.com>
Date: Mon, 19 Jan 2026 09:00:06 -0600
From: David Lechner <dlechner@...libre.com>
To: Tomas Melin <tomas.melin@...sala.com>, Nuno Sá
<noname.nuno@...il.com>, Michael Hennerich <Michael.Hennerich@...log.com>,
Nuno Sa <nuno.sa@...log.com>, Lars-Peter Clausen <lars@...afoo.de>,
Jonathan Cameron <jic23@...nel.org>, Andy Shevchenko <andy@...nel.org>,
Olivier Moysan <olivier.moysan@...s.st.com>
Cc: linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/4] iio: industrialio-backend: support backend
capabilities
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. ;-)
Powered by blists - more mailing lists