public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	linux-rockchip@lists.infradead.org
Subject: arm/rockchip.yaml - many separate entries instead of enums
Date: Tue, 29 Mar 2022 19:05:24 +0200	[thread overview]
Message-ID: <ce367384-3d44-b7a9-06cd-1ca1f2ddf7e9@kernel.org> (raw)

Hi Heiko,

I found that Documentation/devicetree/bindings/arm/rockchip.yaml uses
pattern of one board per item in oneOf.

This leads to quite big file, with many entries, although gives nice
description for each board.

I find enum-based pattern, like FSL [1], much more readable and compact.
What do you think? I could re-organize the arm/rockchip.yaml, but I
don't want to mess with your preference.

[1]
https://elixir.bootlin.com/linux/latest/source/Documentation/devicetree/bindings/arm/fsl.yaml#L191

Best regards,
Krzysztof

             reply	other threads:[~2022-03-29 17:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 17:05 Krzysztof Kozlowski [this message]
2022-03-29 20:54 ` arm/rockchip.yaml - many separate entries instead of enums Heiko Stübner
2022-03-30  7:16   ` 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=ce367384-3d44-b7a9-06cd-1ca1f2ddf7e9@kernel.org \
    --to=krzk@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=linux-rockchip@lists.infradead.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