From: Corentin Labbe <clabbe@baylibre.com>
To: mark.rutland@arm.com, maxime.ripard@bootlin.com,
robh+dt@kernel.org, wens@csie.org, jernej.skrabec@siol.net
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com,
Corentin Labbe <clabbe@baylibre.com>
Subject: [PATCH v2 0/2] ARM64: dts: allwinner: Add devicetree for pine H64 modelA evaluation board
Date: Tue, 29 Oct 2019 19:17:41 +0000 [thread overview]
Message-ID: <1572376663-22023-1-git-send-email-clabbe@baylibre.com> (raw)
Hello
Pineh64 have two existing model (A and B) with some hardware difference and
so need two different DT file.
But the current situation has only one file for both.
This serie fix this situation by being more clear on which DT file is
needed for both model.
Regards
Changes since v1:
- Added the first patch for stating which model support the
sun50i-h6-pine-h64.dts
Corentin Labbe (2):
ARM64: dts: sun50i-h6-pine-h64: state that the DT supports the modelB
ARM64: dts: allwinner: add pineh64 model A
.../devicetree/bindings/arm/sunxi.yaml | 9 +++++--
arch/arm64/boot/dts/allwinner/Makefile | 1 +
.../allwinner/sun50i-h6-pine-h64-modelA.dts | 26 +++++++++++++++++++
.../boot/dts/allwinner/sun50i-h6-pine-h64.dts | 4 +--
4 files changed, 36 insertions(+), 4 deletions(-)
create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64-modelA.dts
--
2.21.0
next reply other threads:[~2019-10-29 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 19:17 Corentin Labbe [this message]
2019-10-29 19:17 ` [PATCH v2 1/2] ARM64: dts: sun50i-h6-pine-h64: state that the DT supports the modelB Corentin Labbe
2019-10-29 19:17 ` [PATCH v2 2/2] ARM64: dts: allwinner: add pineh64 model A Corentin Labbe
2019-10-29 19:27 ` Jernej Škrabec
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=1572376663-22023-1-git-send-email-clabbe@baylibre.com \
--to=clabbe@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@siol.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).