From: "Ivan T. Ivanov" <ivan.ivanov@linaro.org>
To: Kumar Gala <galak@codeaurora.org>, Andy Gross <agross@codeaurora.org>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Stanimir Varbanov <stanimir.varbanov@linaro.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Olof Johansson <olof@lixom.net>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org
Subject: [PATCH 0/7] arm64: dts: qcom: msm8916 fixes and updates
Date: Thu, 4 Jun 2015 12:18:59 +0300 [thread overview]
Message-ID: <1433409546-23995-1-git-send-email-ivan.ivanov@linaro.org> (raw)
Following patches add configuration nodes for SPI, I2C, USB and SDHC devices
found in msm8916 and related pinctrl definitions. Also several GPIO have been
incorrectly assigned and are fixed now. LED control devices for apq 8016-sbc
board are added.
Regards,
Ivan
Ivan T. Ivanov (6):
arm64: dts: qcom: Extend msm8916 pinctrl device coverage
arm64: dts: qcom: Add msm8916 BLSP device nodes
arm64: dts: qcom: Add msm8916 USB configuration nodes
arm64: dts: qcom: apq8016-sbc: Don't hog client driver pins
arm64: dts: qcom: Fix apq8016-sbc board USB related pin definitions
arm64: dts: qcom: Add apq8016-sbc board LED's related device nodes
Srinivas Kandagatla (1):
arm64: dts: qcom: Add msm8916 sdhci configuration nodes
.../arm64/boot/dts/qcom/apq8016-sbc-pmic-pins.dtsi | 34 +-
arch/arm64/boot/dts/qcom/apq8016-sbc-soc-pins.dtsi | 14 +-
arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi | 51 +++
arch/arm64/boot/dts/qcom/msm8916-pins.dtsi | 430 +++++++++++++++++++++
arch/arm64/boot/dts/qcom/msm8916.dtsi | 227 +++++++++--
5 files changed, 708 insertions(+), 48 deletions(-)
create mode 100644 arch/arm64/boot/dts/qcom/msm8916-pins.dtsi
--
1.9.1
next reply other threads:[~2015-06-04 9:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 9:18 Ivan T. Ivanov [this message]
2015-06-04 9:19 ` [PATCH 1/7] arm64: dts: qcom: Extend msm8916 pinctrl device coverage Ivan T. Ivanov
[not found] ` <1433409546-23995-1-git-send-email-ivan.ivanov-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-06-04 9:19 ` [PATCH 2/7] arm64: dts: qcom: Add msm8916 BLSP device nodes Ivan T. Ivanov
2015-06-04 9:19 ` [PATCH 3/7] arm64: dts: qcom: Add msm8916 sdhci configuration nodes Ivan T. Ivanov
2015-06-04 9:19 ` [PATCH 4/7] arm64: dts: qcom: Add msm8916 USB " Ivan T. Ivanov
2015-06-04 9:19 ` [PATCH 5/7] arm64: dts: qcom: apq8016-sbc: Don't hog client driver pins Ivan T. Ivanov
2015-06-04 9:19 ` [PATCH 6/7] arm64: dts: qcom: Fix apq8016-sbc board USB related pin definitions Ivan T. Ivanov
2015-06-04 9:19 ` [PATCH 7/7] arm64: dts: qcom: Add apq8016-sbc board LED's related device nodes Ivan T. Ivanov
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=1433409546-23995-1-git-send-email-ivan.ivanov@linaro.org \
--to=ivan.ivanov@linaro.org \
--cc=agross@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=stanimir.varbanov@linaro.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).