From: Jisheng Zhang <jszhang@marvell.com>
To: <sebastian.hesselbarth@gmail.com>, <catalin.marinas@arm.com>,
<will.deacon@arm.com>, <robh+dt@kernel.org>, <pawel.moll@arm.com>,
<mark.rutland@arm.com>, <ijc+devicetree@hellion.org.uk>,
<galak@codeaurora.org>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Jisheng Zhang <jszhang@marvell.com>
Subject: [PATCH 0/3] arm64: dts: berlin4ct: add GPIO support
Date: Fri, 18 Sep 2015 21:47:36 +0800 [thread overview]
Message-ID: <1442584059-7319-1-git-send-email-jszhang@marvell.com> (raw)
Marvell berlin4ct SoC has 6 GPIO ports powered by snps,dw-apb-gpio. patch1
enables ARCH_REQUIRE_GPIOLIB for ARCH_BERLIN. patch2 add GPIO nodes in the
SoC dtsi. The last patch add board dts file for STB reference board.
Jisheng Zhang (3):
arm64: berlin: enable ARCH_REQUIRE_GPIOLIB
arm64: dts: berlin4ct: add GPIO nodes
arm64: dts: add dts file for Marvell Berlin4CT STB board
arch/arm64/Kconfig.platforms | 1 +
arch/arm64/boot/dts/marvell/berlin4ct-stb.dts | 66 ++++++++++++++
arch/arm64/boot/dts/marvell/berlin4ct.dtsi | 120 ++++++++++++++++++++++++++
3 files changed, 187 insertions(+)
create mode 100644 arch/arm64/boot/dts/marvell/berlin4ct-stb.dts
--
2.5.1
next reply other threads:[~2015-09-18 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 13:47 Jisheng Zhang [this message]
2015-09-18 13:47 ` [PATCH 1/3] arm64: berlin: enable ARCH_REQUIRE_GPIOLIB Jisheng Zhang
2015-09-20 19:06 ` Sebastian Hesselbarth
2015-09-18 13:47 ` [PATCH 2/3] arm64: dts: berlin4ct: add GPIO nodes Jisheng Zhang
2015-09-18 13:47 ` [PATCH 3/3] arm64: dts: add dts file for Marvell Berlin4CT STB board Jisheng Zhang
2015-09-20 19:06 ` Sebastian Hesselbarth
2015-09-21 2:19 ` Jisheng Zhang
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=1442584059-7319-1-git-send-email-jszhang@marvell.com \
--to=jszhang@marvell.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--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®