From: yendapally.reddy@broadcom.com (Yendapally Reddy Dhananjaya Reddy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] pinmux support for Broadcom NS2 SoC
Date: Thu, 3 Mar 2016 06:41:40 -0500 [thread overview]
Message-ID: <1457005303-26829-1-git-send-email-yendapally.reddy@broadcom.com> (raw)
This patchset contains the pinmux support for the Broadcom's
Northstar 2 (NS2) SoC.
The first patch provides the documentation details and the
second patch contains the driver details. The third patch contains
the enable method.
This patchset has been tested on NS2 bcm958712K board.
This patchset is based on v4.5.0-rc3 and is available from github
repo: https://github.com/Broadcom/arm64-linux.git
branch: ns2-pinmux-v1
Yendapally Reddy Dhananjaya Reddy (3):
pinctrl: Broadcom Northstar2 pinctrl device tree bindings
pinctrl: ns2: add pinmux driver support for Broadcom NS2 SoC
ARM: dts: enable pinctrl for Broadcom NS2 SoC
.../bindings/pinctrl/brcm,ns2-pinmux.txt | 102 ++
arch/arm64/boot/dts/broadcom/ns2-svk.dts | 9 +
arch/arm64/boot/dts/broadcom/ns2.dtsi | 7 +
drivers/pinctrl/bcm/Kconfig | 13 +
drivers/pinctrl/bcm/Makefile | 1 +
drivers/pinctrl/bcm/pinctrl-ns2-mux.c | 1122 ++++++++++++++++++++
6 files changed, 1254 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,ns2-pinmux.txt
create mode 100644 drivers/pinctrl/bcm/pinctrl-ns2-mux.c
--
2.1.0
next reply other threads:[~2016-03-03 11:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 11:41 Yendapally Reddy Dhananjaya Reddy [this message]
2016-03-03 11:41 ` [PATCH 1/3] pinctrl: Broadcom Northstar2 pinctrl device tree bindings Yendapally Reddy Dhananjaya Reddy
2016-03-05 4:29 ` Rob Herring
2016-03-09 10:58 ` Linus Walleij
2016-03-03 11:41 ` [PATCH 2/3] pinctrl: ns2: add pinmux driver support for Broadcom NS2 SoC Yendapally Reddy Dhananjaya Reddy
2016-03-09 11:04 ` Linus Walleij
2016-03-09 17:50 ` Stephen Warren
2016-03-03 11:41 ` [PATCH 3/3] ARM: dts: enable pinctrl " Yendapally Reddy Dhananjaya Reddy
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=1457005303-26829-1-git-send-email-yendapally.reddy@broadcom.com \
--to=yendapally.reddy@broadcom.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;
as well as URLs for NNTP newsgroup(s).