From: ezequiel@collabora.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/2] arm64: rockchip: support RK3399 Ficus board
Date: Fri, 6 Jul 2018 12:08:16 -0300 [thread overview]
Message-ID: <20180706150818.5631-1-ezequiel@collabora.com> (raw)
Fourth round for the RK3399 Ficus support.
Changes from v3:
* Fixed a regulator node name, as noted by Rob.
* Fixed wrong alphabetical order in vendors prefix patch, also noted by Rob.
Changes from v2:
* Dropped rk3399.dtsi changes and rebased on top of Randy's patch.
* Removed double empty line.
* Coalesced schematics comment
Changes from v1:
* Dropoed USB support as it's not working.
* Added schematics.
* Splitted rk3399.dtsi from new ficus.dts file.
* Added new vendor.
* Cleaned regulators syntax and stlye.
Series based on: 600b359d2b98 ("arm64: dts: rockchip: add some common pin-settings to rk3399").
Ezequiel Garcia (2):
dt-bindings: Add vendor prefix for Vamrs Ltd.
arm64: dts: rockchip: add 96boards RK3399 Ficus board
.../devicetree/bindings/arm/rockchip.txt | 5 +
.../devicetree/bindings/vendor-prefixes.txt | 1 +
arch/arm64/boot/dts/rockchip/Makefile | 1 +
arch/arm64/boot/dts/rockchip/rk3399-ficus.dts | 514 ++++++++++++++++++
4 files changed, 521 insertions(+)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-ficus.dts
--
2.18.0.rc2
next reply other threads:[~2018-07-06 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 15:08 Ezequiel Garcia [this message]
2018-07-06 15:08 ` [PATCH v4 1/2] dt-bindings: Add vendor prefix for Vamrs Ltd Ezequiel Garcia
2018-07-11 15:04 ` Rob Herring
2018-07-06 15:08 ` [PATCH v4 2/2] arm64: dts: rockchip: add 96boards RK3399 Ficus board Ezequiel Garcia
2018-07-12 9:31 ` [PATCH v4 0/2] arm64: rockchip: support " Heiko Stübner
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=20180706150818.5631-1-ezequiel@collabora.com \
--to=ezequiel@collabora.com \
--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