linux-kernel - Re: [PATCH v2 1/7] dt-bindings: sound: sophgo: add CV1800B I2S/TDM controller binding

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: <5248fe03-7e77-4c5d-ad05-e182b3068e66@kernel.org>
Date: Sun, 18 Jan 2026 17:14:04 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Chen Wang <unicorn_wang@...look.com>,
 Inochi Amaoto <inochiama@...il.com>, Jaroslav Kysela <perex@...ex.cz>,
 Takashi Iwai <tiwai@...e.com>, Paul Walmsley <pjw@...nel.org>,
 Palmer Dabbelt <palmer@...belt.com>, Albert Ou <aou@...s.berkeley.edu>,
 Alexandre Ghiti <alex@...ti.fr>, linux-sound@...r.kernel.org,
 devicetree@...r.kernel.org, sophgo@...ts.linux.dev,
 linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org
Subject: Re: [PATCH v2 1/7] dt-bindings: sound: sophgo: add CV1800B I2S/TDM
 controller binding

On 18/01/2026 13:18, Anton D. Stavinskii wrote:
>>
>> Again, messed constraints.
>>
>>> +    items:
>>> +      enum: [rx, tx]
>>
>> No, it has to be a specific/fixed list.
> 
> Here is the question. Can you please help to understand how to describe
> this properly. The idea is that TDM module is usable even without
> specified dmas. Each TDM can work as clock source, only rx only tx or
> both. I can force to use both channels but the user probably will want 
> to not consume all the channels for if it is not needed. DMA can provide
> channels for something else like SPI/I2C/UART etc. I'm asking because
> I'm afraid I will do some mess again here.

If any combination is valid in hardware, then:

minItems: 1
items:
  - enum: [rx, tx]
  - const: tx

Best regards,
Krzysztof