From: Chen-Yu Tsai <wenst@chromium.org>
To: Rob Herring <robh+dt@kernel.org>, Heiko Stuebner <heiko@sntech.de>
Cc: Chen-Yu Tsai <wenst@chromium.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] arm64: dts: rockchip: Add Scarlet Dumo Variant
Date: Thu, 12 Aug 2021 17:47:51 +0800 [thread overview]
Message-ID: <20210812094753.2359087-1-wenst@chromium.org> (raw)
Hi,
A variant of the Chrome OS Gru-Scarlet device is missing in upstream.
This variant, dumo, is the same as the Innolux display panel variant,
but requires a specific calibration variant for its WiFi module.
I'm not sure if it's better to inherit from gru-scarlet-innolux. I kept
them separate from now, like in downstream ChromeOS kernel v4.4.
The series is based on linux-next-20210812. Please have a look.
Regards
ChenYu
Chen-Yu Tsai (2):
dt-bindings: arm: rockchip: Add gru-scarlet-dumo board
arm64: dts: rockchip: rk3399: Add gru-scarlet-dumo board
.../devicetree/bindings/arm/rockchip.yaml | 28 +++++++++++++
arch/arm64/boot/dts/rockchip/Makefile | 1 +
.../dts/rockchip/rk3399-gru-scarlet-dumo.dts | 41 +++++++++++++++++++
3 files changed, 70 insertions(+)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-gru-scarlet-dumo.dts
--
2.32.0.605.g8dce9f2422-goog
next reply other threads:[~2021-08-12 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 9:47 Chen-Yu Tsai [this message]
2021-08-12 9:47 ` [PATCH 1/2] dt-bindings: arm: rockchip: Add gru-scarlet-dumo board Chen-Yu Tsai
2021-08-12 9:47 ` [PATCH 2/2] arm64: dts: rockchip: rk3399: " Chen-Yu Tsai
2021-08-13 8:51 ` [PATCH 0/2] arm64: dts: rockchip: Add Scarlet Dumo Variant Heiko Stuebner
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=20210812094753.2359087-1-wenst@chromium.org \
--to=wenst@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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).