mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dragan Simic" <dsimic@manjaro.org>
To: "Jonas Karlman" <jonas@kwiboo.se>
Cc: "Diederik de Haas" <diederik@cknow-tech.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Heiko Stuebner" <heiko@sntech.de>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	"Johan Jonker" <jbx6244@gmail.com>
Subject: Re: [PATCH v2] arm64: dts: rockchip: Harmonize regulator formatting for Pine64 rk3566  devices
Date: Mon, 27 Oct 2025 19:19:36 +0100	[thread overview]
Message-ID: <7dc31259-c172-de0e-554c-2563014b9c2c@manjaro.org> (raw)
In-Reply-To: <60a1046c-437e-400a-8e2c-391cd471c358@kwiboo.se>

Hello Jonas and Heiko,

On Monday, October 27, 2025 19:06 CET, Jonas Karlman <jonas@kwiboo.se> wrote:
> On 10/27/2025 4:39 PM, Diederik de Haas wrote:
> > The regulator node properties in Pine64 rk3566 devices were formatted
> > rather inconsistently. To name a few:
> > - 'name' was sometimes put at the top of the list, while at other times
> >   it was (mostly) sorted in alphabetical order
> 
> Personally I prefer to list the regulator-name as the first property, I
> think it makes it visually easier/quicker to identify a regulator with
> the name prop at top.
> 
> I typically try to use the following prop ordering for regulators on
> board DTs I submit (and review):
> 
> - regulator-name as the first prop (to quickly identify the regulator)
> - regulator-min-* before regulator-max-* (natural order)
> - regulator-* in alphabetical/natural order
> 
> Maybe this preference just comes from a long history of always putting
> id/primary key/unique identifiers at top or beginning of data tables,
> classes, structs etc ;-)

Oh, I actually agree with your and Heiko's preferences when
it comes to the ordering, regardless of that being personal
preference, tribal knowledge or just common sense. :)

However, that's quite conflicting with the current official
rules for writing DT files, which don't recognize such exceptions
at all.  Perhaps we should attempt to incorporate such preferences
into the official rules, because such non-standard ordering does
make DTs more readable?  Following the rules is good, unless it
makes the end results worse, IMHO.


      reply	other threads:[~2025-10-27 18:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27 15:39 Diederik de Haas
2025-10-27 18:06 ` Jonas Karlman
2025-10-27 18:19   ` Dragan Simic [this message]

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=7dc31259-c172-de0e-554c-2563014b9c2c@manjaro.org \
    --to=dsimic@manjaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=diederik@cknow-tech.com \
    --cc=heiko@sntech.de \
    --cc=jbx6244@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh@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®