From: Leonid Segal <leonid.s@variscite.com>
To: robh+dt@kernel.org, mark.rutland@arm.com, devicetree@vger.kernel.org
Cc: david.brown@linaro.org, andy.gross@linaro.org,
catalin.marinas@arm.com, will.deacon@arm.com,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Leonid Segal <leonid.s@variscite.com>
Subject: [PATCH 0/1] arm64: dts: Add Variscite DART-SD410 Evaluation board dts
Date: Wed, 2 Aug 2017 12:46:13 +0300 [thread overview]
Message-ID: <20170802094614.25679-1-leonid.s@variscite.com> (raw)
Add initial device tree support for Variscite DART-SD410 Evalueation board.
This board is also known as VAR-SD410CustomBoard.
checkpatch.pl gives warnings for some lines that are over 80 characters,
but I decided not to change them since similar lines in other dts files.
Patch has been tested on 96Boards Dragonboard410c and Variscite SD410Customboard
Both Linaro Linux 17.06 release
https://discuss.96boards.org/t/linaro-linux-17-06-releases/2217
Signed-off-by: Leonid Segal <leonid.s@variscite.com>
---
arch/arm64/boot/dts/qcom/Makefile | 1 +
.../boot/dts/qcom/apq8016-var-dart-pmic-pins.dtsi | 53 +++
.../boot/dts/qcom/apq8016-var-dart-soc-pins.dtsi | 88 ++++
arch/arm64/boot/dts/qcom/apq8016-var-dart.dts | 21 +
arch/arm64/boot/dts/qcom/apq8016-var-dart.dtsi | 525 +++++++++++++++++++++
5 files changed, 688 insertions(+)
create mode 100644 arch/arm64/boot/dts/qcom/apq8016-var-dart-pmic-pins.dtsi
create mode 100644 arch/arm64/boot/dts/qcom/apq8016-var-dart-soc-pins.dtsi
create mode 100644 arch/arm64/boot/dts/qcom/apq8016-var-dart.dts
create mode 100644 arch/arm64/boot/dts/qcom/apq8016-var-dart.dtsi
--
2.13.0
next reply other threads:[~2017-08-02 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 9:46 Leonid Segal [this message]
2017-08-02 9:46 ` [PATCH 1/1] " Leonid Segal
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=20170802094614.25679-1-leonid.s@variscite.com \
--to=leonid.s@variscite.com \
--cc=andy.gross@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.com \
/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
all inboxes | Powered by JetHome®