From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] arm64: dts: rockchip: add Gru Scarlet devicetrees
Date: Mon, 5 Nov 2018 16:06:18 -0600 [thread overview]
Message-ID: <20181105220618.GA20928@bogus> (raw)
In-Reply-To: <20181101123639.15560-2-heiko@sntech.de>
On Thu, 1 Nov 2018 13:36:39 +0100, Heiko Stuebner wrote:
> Gru-Scarlet is a tablet device using ChomeOS, dual-dsi display
> and Wacom touchscreen with stylus.
>
> There exist two variants in the market using different displays
> that are differentiated via their sku-id.
> The bootloader on them also determines the correct devicetree to
> load via the sku-id.
>
> So add a common scarlet dtsi and two minimal board devicetrees
> for the two display variants.
>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> ---
> changes in v2:
> - drop coreboot param override
> - rebase against current master state so it will apply against 4.20-rc1
>
> .../devicetree/bindings/arm/rockchip.txt | 34 +
> arch/arm64/boot/dts/rockchip/Makefile | 2 +
> .../dts/rockchip/rk3399-gru-scarlet-inx.dts | 33 +
> .../dts/rockchip/rk3399-gru-scarlet-kd.dts | 33 +
> .../boot/dts/rockchip/rk3399-gru-scarlet.dtsi | 594 ++++++++++++++++++
> 5 files changed, 696 insertions(+)
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-gru-scarlet-inx.dts
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-gru-scarlet-kd.dts
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-gru-scarlet.dtsi
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-11-05 22:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 12:36 [PATCH v2 1/2] arm64: dts: rockchip: add missing address and size cells for rk3399 mipi dsi Heiko Stuebner
2018-11-01 12:36 ` [PATCH v2 2/2] arm64: dts: rockchip: add Gru Scarlet devicetrees Heiko Stuebner
2018-11-05 22:06 ` Rob Herring [this message]
2018-11-06 11:31 ` Heiko Stuebner
2018-11-08 1:13 ` Brian Norris
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=20181105220618.GA20928@bogus \
--to=robh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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