From: Astrid Rost <astridr@axis.com>
To: Mark Brown <broonie@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Astrid Rost <astrid.rost@axis.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
<kernel@axis.com>,
alsa-devel-mejlinglistan <alsa-devel@alsa-project.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: sound: ts3a227e: add control of debounce times
Date: Fri, 9 Sep 2022 09:16:49 +0200 [thread overview]
Message-ID: <b42e7fe4-9e1b-fdda-44f2-aa87b06425c8@axis.com> (raw)
In-Reply-To: <Yxn9o1MVMPnFO3PM@sirena.org.uk>
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
next prev parent reply other threads:[~2022-09-09 7:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 13:58 [PATCH] dt-bindings: sound: ts3a227e: add control of debounce times Astrid Rost
2022-09-08 12:20 ` Krzysztof Kozlowski
2022-09-08 14:35 ` Mark Brown
2022-09-09 7:16 ` Astrid Rost [this message]
2022-09-09 7:25 ` Krzysztof Kozlowski
2022-09-09 7:23 ` Krzysztof Kozlowski
2022-09-09 8:21 ` Krzysztof Kozlowski
2022-09-09 18:47 ` Mark Brown
2022-09-12 7:26 ` Astrid Rost
2022-09-13 7:16 ` Astrid Rost
2022-09-13 9:13 ` Krzysztof Kozlowski
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=b42e7fe4-9e1b-fdda-44f2-aa87b06425c8@axis.com \
--to=astridr@axis.com \
--cc=alsa-devel@alsa-project.org \
--cc=astrid.rost@axis.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@axis.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).