From: "David Summers" <beagleboard@davidjohnsummers.uk>
To: heiko@sntech.de, robh+dt@kernel.org, mark.rutland@arm.com
Cc: linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: [PATCH] Device Tree for ASUS Tinker Board S (v2)
Date: Sun, 16 Sep 2018 19:16:33 +0100 [thread overview]
Message-ID: <20180916181636.7938-1-beagleboard@davidjohnsummers.uk> (raw)
Thanks to Heiko for comments on the first
The tinkerboard S is an ASUS device, it is similar to the tinker board
but with an eMMC chip, which needs enabling in the device tree.
This patch is split into 3 parts
1) It creates a common include file rk3288-tinker.dtsi and sets up
rk3288-tinker.dts and rk3288-tinker-s.dts to do device trees for the two boards
2) It patches the rk3288-tinker-s.dts to enable eMMC
3) It patches the rk3299-tinker-s.dts to enable WiFi and Bluetooth
I'm not sure if the wifi should be common for both boards (so in the dtsi)
But am sure its needed to enable wifi on the S variant.
I have asked for the dtb to be tested - but sending these patches anyway
to get comments back.
Regards
David Summers
signed-off: "David Summers" <beagleboard@davidjohnsummers.uk>
next reply other threads:[~2018-09-16 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 18:16 David Summers [this message]
2018-09-16 18:16 ` [PATCH 1/3] Device Tree for ASUS Tinker Board S (v2) David Summers
2018-09-16 18:16 ` [PATCH 2/3] " David Summers
[not found] ` <20180916181636.7938-1-beagleboard-8lkWs+DogrrqRUWtDFdff/XRex20P6io@public.gmane.org>
2018-09-16 18:16 ` [PATCH 3/3] " David Summers
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=20180916181636.7938-1-beagleboard@davidjohnsummers.uk \
--to=beagleboard@davidjohnsummers.uk \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--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).