From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Jon Hunter" <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-pwm@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: pwm: tegra: Convert to json-schema
Date: Thu, 3 Nov 2022 10:53:33 -0400 [thread overview]
Message-ID: <26249f27-dbea-c30e-a2ea-df5cb4290b3e@linaro.org> (raw)
In-Reply-To: <Y2PSgwfqZ9BfXSFw@orome>
On 03/11/2022 10:38, Thierry Reding wrote:
>>> +
>>> + clock-names:
>>> + items:
>>> + - const: pwm
>>
>> This wasn't in original binding and does not look needed. Mention
>> changes from pure conversion.
>
> At some point (looks like with the switch to 64-bit ARM) we started
> adding these for consistency because we were noticing that sometimes
> either we were missing clock entries or newer SoC generations gained
> additional clocks. Whenever that happened it would become somewhat
> cumbersome to describe this in device tree bindings and/or driver
> code, so consistently adding a clock-names property preventively
> even if only a single clock was used in the first iteration seemed a
> prudent thing to do.
Adding undocumented properties "preventively" is not the correct
approach. Either you document them, or you do not add them.
The property with one item and name matching the function is not really
a good approach, not helpful. Drop it.
>
> So these are not technically necessary, but many device tree files will
> have these entries, so this is here for those to pass validation.
Drop it from DTS then.
>
> Note that the property doesn't show up along the "clocks" property in
> "required:" below.
>
>>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-03 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 12:01 [PATCH] dt-bindings: pwm: tegra: Convert to json-schema Thierry Reding
2022-11-03 12:35 ` Rob Herring
2022-11-03 14:03 ` Thierry Reding
2022-11-03 14:07 ` Krzysztof Kozlowski
2022-11-03 14:14 ` Krzysztof Kozlowski
2022-11-03 14:38 ` Thierry Reding
2022-11-03 14:53 ` Krzysztof Kozlowski [this message]
2022-11-07 19:58 ` Uwe Kleine-König
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=26249f27-dbea-c30e-a2ea-df5cb4290b3e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).