From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Kevin Hilman <khilman@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Alexander Stein <alexander.stein@mailbox.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH 1/2] arm64: dts: meson-g12: Fix clock order for amlogic,axg-tdm-iface devices
Date: Wed, 16 Aug 2023 08:23:23 +0200 [thread overview]
Message-ID: <3f437e5b-2bae-384a-0a08-216a4ec55bde@linaro.org> (raw)
In-Reply-To: <7ha5uyes3f.fsf@baylibre.com>
On 10/08/2023 19:15, Kevin Hilman wrote:
> DT maintainers,
>
> Alexander Stein <alexander.stein@mailbox.org> writes:
>
>> Binding specify order of clocks as:
>> 1. "sclk"
>> 2. "lrclk"
>> 3. "mclk"
>> Adjust clocks accordingly. Fixes warnings:
>
> I understand this patch is to fix DT warnings (and thank you Alexander
> for fixing warnings!) ... *but* the underlying requirement being
> enforced by the schema here seems completely wrong to me, and a step
> backwards.
>
> Sorry if this is a FAQ someplace, but I couldn't find an explanation for
> this. One of the main goals of introducing names in the first place was
> to get rid of ordering requirements.
Not entirely. The names was just a helper for cases when order is not
fixed, but even with the names for every regular case the order was
always strict. We always expect these to be ordered.
> Now the DT schema is enforcing
> ordering requirements, but the drivers don't need ordering, so what is
> the point of enforcing ordering requirements?
Because names are not everything. One OS implementation might still take
by indices, even if names are provided, so you cannot change the order.
Few bindings allow relaxed approach here, but these are written that way
to allow mixing order.
For few other bindings (e.g. newer Qualcomm clock controllers) we just
dropped the names entirely, because they bring little value and also
code for lookup by name is slower than by index.
Best regards,
Krzysztof
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2023-08-16 6:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 16:17 Alexander Stein
2023-08-08 16:17 ` [PATCH 2/2] arm64: dts: meson-g12: Fix compatible for amlogic,g12a-tdmin Alexander Stein
2023-08-10 17:15 ` [PATCH 1/2] arm64: dts: meson-g12: Fix clock order for amlogic,axg-tdm-iface devices Kevin Hilman
2023-08-16 6:23 ` Krzysztof Kozlowski [this message]
2023-08-17 21:53 ` Kevin Hilman
2023-08-18 8:58 ` Krzysztof Kozlowski
2023-08-18 11:39 ` Jerome Brunet
2023-08-18 15:01 ` Jerome Brunet
2023-08-19 9:51 ` Krzysztof Kozlowski
2023-09-11 9:46 ` Neil Armstrong
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=3f437e5b-2bae-384a-0a08-216a4ec55bde@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alexander.stein@mailbox.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.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®