linux-kernel - Re: [PATCH v2 3/4] dt-bindings: iio: adc: ad4080: add AD4880 support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <79c21d77-32c0-401a-94e2-ba4349a7a616@kernel.org>
Date: Mon, 9 Feb 2026 18:13:04 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Nuno Sá <noname.nuno@...il.com>,
 Antoniu Miclaus <antoniu.miclaus@...log.com>
Cc: Lars-Peter Clausen <lars@...afoo.de>,
 Michael Hennerich <Michael.Hennerich@...log.com>,
 Jonathan Cameron <jic23@...nel.org>, David Lechner <dlechner@...libre.com>,
 Nuno Sá <nuno.sa@...log.com>,
 Andy Shevchenko <andy@...nel.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Olivier Moysan <olivier.moysan@...s.st.com>,
 Mark Brown <broonie@...nel.org>, linux-iio@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-spi@...r.kernel.org
Subject: Re: [PATCH v2 3/4] dt-bindings: iio: adc: ad4080: add AD4880 support

On 09/02/2026 17:43, Nuno Sá wrote:
> On Sun, 2026-02-08 at 10:20 +0100, Krzysztof Kozlowski wrote:
>> On 08/02/2026 10:16, Nuno Sá wrote:
>>>>>  
>>>>>    io-backends:
>>>>> -    maxItems: 1
>>>>> +    minItems: 1
>>>>> +    maxItems: 2
>>>>
>>>> Instead list the items with minItems, so the order is defined.
>>>>
>>>
>>> Also looks like we now need 'io-backend-names'.
>>
>> No. Just define the order here.
>>
> 
> Things are still not really defined on the code side (I know bindings don't care about the driver
> side) but io-backend-names is a standard property and we might actually end up using it so that

And names do not change that at all. Actually they might make it worse,
because they allow drivers to fetch item by name which people think
means "order is flexible".

> we know how to map the backend to a given channel. Unless what you're saying is that in here, -names
> doesn't really makes sense given that we just want n io-backends for n adc channels and having 
> -names as "adc1", "adc2", "adcn" is arguably useless.

Names like adcX indeed would not make much sense.

Best regards,
Krzysztof