From: Erik Beck <xunil@tahomasoft.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: Erik Beck <xunil@tahomasoft.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2 v2]: New board support,LinkStar-H68k-1432v1 (RK3568)
Date: Mon, 21 Jul 2025 16:11:34 -0400 [thread overview]
Message-ID: <20250721201137.233166-1-xunil@tahomasoft.com> (raw)
Signed-off-by: Erik Beck <xunil@tahomasoft.com>
This patch series, revision two, provides initial support for the
Seeed LinkStar H68K 1432v1 board, featuring a Rockchip rk3568 SoC.
Changes were made relative to patch set version one to address
comments provided by Heiko Stuebner <heiko@sntech.de> (Fri, 18 Jul
2025 15:13:22 +0200).
Those changes are:
* Splits the single commit into two, one for the yaml binding, and the
other for the board devicetree plus Makefile addition;
* Adds other recipients needed from get_maintainer.pl --nol and --nom;
* Uses git send-email to send the patches, to avoid adding line breaks
from the MUA;
* Changes comment style to conform with style guide;
* Removes several unneeded comments from the devicetree;
* Changes LED naming scheme with more standard nomenclature;
* Changes naming of regulators, prepending 'regulator', such as:
- from: vcc12v_dcin: vcc12v-dcin {}
- to: vcc12v_dcin: regulator-vcc12v-dcin {}
* Removes unneeded tx_delay/rx_delay from rgmii-id
Thank you for your time and effort reviewing these proposed patches.
Regards,
Erik
Patch File Summary:
.../devicetree/bindings/arm/rockchip.yaml | 5 +
arch/arm64/boot/dts/rockchip/Makefile | 1 +
.../dts/rockchip/rk3568-linkstar-h68k-1432v1.dts | 740 +++++++++++++++++++++
3 files changed, 746 insertions(+)
next reply other threads:[~2025-07-21 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 20:11 Erik Beck [this message]
2025-07-21 20:11 Erik Beck
2025-07-21 20:12 Erik Beck
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=20250721201137.233166-1-xunil@tahomasoft.com \
--to=xunil@tahomasoft.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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®