From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Mark Brown <broonie@kernel.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 10:21:30 +0200 [thread overview]
Message-ID: <9a72bd22-9298-65ce-a894-540f98745a7e@linaro.org> (raw)
In-Reply-To: <ac2bcca1-6997-2d17-b1d6-a5e81ced2613@linaro.org>
On 09/09/2022 09:23, Krzysztof Kozlowski wrote:
> On 08/09/2022 16:35, Mark Brown wrote:
>> On Thu, Sep 08, 2022 at 02:20:42PM +0200, Krzysztof Kozlowski wrote:
>>
>>> 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.
>
> It's more than one property here and many patch submitters are using
> this reason as well. In an effect few bindings TXT grew from 5 to 10
> properties in one year and still no conversion to YAML.
>
> I understand your concerns however I have stronger motivation to do the
> conversion is stronger for me, than for accepting new features.
Eh, that was still during drinking coffee, so it barely reminds English
sentences. Let me try one more time:
It's more than one property and many other patch submitters were using
this reason as well. As a result, few TXT bindings grew from 5 to 10
properties within one year and there was still no conversion to YAML.
I understand your concerns however I have stronger motivation to do the
conversion, than for accepting new features.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-09-09 8:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 13:58 Astrid Rost
2022-09-08 12:20 ` Krzysztof Kozlowski
2022-09-08 14:35 ` Mark Brown
2022-09-09 7:16 ` Astrid Rost
2022-09-09 7:25 ` Krzysztof Kozlowski
2022-09-09 7:23 ` Krzysztof Kozlowski
2022-09-09 8:21 ` Krzysztof Kozlowski [this message]
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=9a72bd22-9298-65ce-a894-540f98745a7e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--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=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
all inboxes | Powered by JetHome®