From: "Uwe Kleine-König" <uwe@kleine-koenig.org>
To: Rob Herring <robh+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Aditya Prayoga <aditya@kobol.io>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: [PATCH v2 0/2] arm64: Add basic support for Kobol's Helios64
Date: Mon, 12 Oct 2020 22:43:15 +0200 [thread overview]
Message-ID: <20201012204317.1581752-1-uwe@kleine-koenig.org> (raw)
Hello,
this is v2 of the series. Compared to the (implicit) v1 sent with
Message-Id: 20200925214003.27186-1-uwe@kleine-koenig.org I removed most
OPPs to make the the machine run stable. I guess this can be better
fixed by fine tuning the regulator setup, but I don't have the equipment
to find the actual problem. Also I added a copyright hint, a temperature
sensor and a link to the vendor wiki. The first patch got an Ack in the
first round that I added, too.
Best regards
Uwe
Uwe Kleine-König (2):
dt-bindings: vendor-prefixes: Add kobol prefix
arm64: dts: rockchip: Add basic support for Kobol's Helios64
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
arch/arm64/boot/dts/rockchip/Makefile | 1 +
.../dts/rockchip/rk3399-kobol-helios64.dts | 382 ++++++++++++++++++
3 files changed, 385 insertions(+)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-kobol-helios64.dts
--
2.28.0
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2020-10-12 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 20:43 Uwe Kleine-König [this message]
2020-10-12 20:43 ` [PATCH v2 1/2] dt-bindings: vendor-prefixes: Add kobol prefix Uwe Kleine-König
2020-10-12 20:43 ` [PATCH v2 2/2] arm64: dts: rockchip: Add basic support for Kobol's Helios64 Uwe Kleine-König
2020-10-12 22:52 ` Johan Jonker
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=20201012204317.1581752-1-uwe@kleine-koenig.org \
--to=uwe@kleine-koenig.org \
--cc=aditya@kobol.io \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).