[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b42e7fe4-9e1b-fdda-44f2-aa87b06425c8@axis.com>
Date: Fri, 9 Sep 2022 09:16:49 +0200
From: Astrid Rost <astridr@...s.com>
To: Mark Brown <broonie@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
CC: Astrid Rost <astrid.rost@...s.com>,
Liam Girdwood <lgirdwood@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
<kernel@...s.com>,
alsa-devel-mejlinglistan <alsa-devel@...a-project.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] dt-bindings: sound: ts3a227e: add control of debounce
times
Hello,
> Use standard property units "-ms".
I made it in exactly the same way as it is done for the "ti,micbias:".
- ti,micbias: Intended MICBIAS voltage (datasheet section 9.6.7).
Select 0/1/2/3/4/5/6/7 to specify MICBIAS voltage
2.1V/2.2V/2.3V/2.4V/2.5V/2.6V/2.7V/2.8V
Default value is "1" (2.2V).
?> Anyway new properties cannot be accepted. This has to be converted to DT
?> schema (YAML).
> Doing a whole binding conversion feels like a bit of a steep requirement
> when people are just adding a simple property, it's a lot of stop energy
> to figure out the tooling, do the conversion and deal with all the
> bikeshedding that the tools don't catch. It's definitely nice if people
> want to look at that, for more complex binding changes it gets more
> reasonable but for trivial properties it's disproportionate.
Thanks, I am not really sure how yaml works. But I can have a look.
Astrid
Powered by blists - more mailing lists