From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Frank Li <Frank.li@nxp.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Gregor Herburger <gregor.herburger@tq-group.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux@ew.tq-group.com
Subject: Re: [PATCH 2/2] arm64: dts: ls1028a: Add mbls1028a and mbls1028a-ind devicetrees
Date: Fri, 30 May 2025 08:29:27 +0200 [thread overview]
Message-ID: <7298658.31r3eYUQgx@steina-w> (raw)
In-Reply-To: <aDctWKIvBKwF29lP@lizhi-Precision-Tower-5810>
Hi Frank,
Am Mittwoch, 28. Mai 2025, 17:35:52 CEST schrieb Frank Li:
> On Tue, May 27, 2025 at 08:03:55AM +0200, Alexander Stein wrote:
> > From: Gregor Herburger <gregor.herburger@tq-group.com>
> >
> > Add device trees for the MBLS1028A and the MBLS1028A-IND and the SoM
> > TQMLS1028A.
> >
> > Signed-off-by: Gregor Herburger <gregor.herburger@tq-group.com>
> > Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> > ---
> > arch/arm64/boot/dts/freescale/Makefile | 2 +
> > .../fsl-ls1028a-tqmls1028a-mbls1028a-ind.dts | 68 ++++
> > .../fsl-ls1028a-tqmls1028a-mbls1028a.dts | 118 +++++++
> > .../fsl-ls1028a-tqmls1028a-mbls1028a.dtsi | 291 ++++++++++++++++++
> > .../dts/freescale/fsl-ls1028a-tqmls1028a.dtsi | 117 +++++++
>
> New dts file, suggest run https://github.com/lznuaa/dt-format to nice order
Thanks for the suggestions. It does some improvements, but I also disagree
with a lot of proposed changes:
* Wrong indent of SPDX tag
* model property should come first IMHO
* {gpio,interrupt}-controller should come before #{gpio,interrupt}-cells
* gpio-hog property should come first in a hog node
* sorting gpio-hog nodes by name instead of line number seems wrong
There are some more bogus changes, so I'll skip this tool for now.
Thanks & best regards
Alexander
> Frank
> [...]
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2025-05-30 6:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 6:03 [PATCH 1/2] dt-bindings: arm: fsl: add TQ-Systems boards MBLS1028A and MBLS1028A-IND Alexander Stein
2025-05-27 6:03 ` [PATCH 2/2] arm64: dts: ls1028a: Add mbls1028a and mbls1028a-ind devicetrees Alexander Stein
2025-05-28 15:35 ` Frank Li
2025-05-30 6:29 ` Alexander Stein [this message]
2025-05-30 15:05 ` Frank Li
2025-05-30 16:17 ` Frank Li
2025-06-02 14:28 ` Alexander Stein
2025-06-02 16:00 ` Frank Li
2025-05-27 7:28 ` [PATCH 1/2] dt-bindings: arm: fsl: add TQ-Systems boards MBLS1028A and MBLS1028A-IND Rob Herring (Arm)
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=7298658.31r3eYUQgx@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=Frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregor.herburger@tq-group.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@ew.tq-group.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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