From: Sricharan R <sricharan@codeaurora.org>
To: andy.gross@linaro.org, david.brown@linaro.org,
robh+dt@kernel.org, linux-arm-msm@vger.kernel.org,
linux-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: sricharan@codeaurora.org
Subject: [PATCH 0/5] arm: dts: qcom: Few updates for ipq8064
Date: Fri, 3 Aug 2018 19:40:14 +0530 [thread overview]
Message-ID: <1533305419-29152-1-git-send-email-sricharan@codeaurora.org> (raw)
Adding pcie,sdcc nodes and a new board file ipq8064-ap161
Sricharan R (5):
arm: dts: qcom: Add pcie nodes for ipq8064
arm: dts: qcom: Add sdcc nodes for ipq8064
arm: dts: qcom: Move common nodes to ipq8064-v.1.0.dtsi
arm: dts: qcom: Add ipq8064-ap161.dts
arm: dts: qcom: Add led and gpio-button nodes to ipq8064 boards
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/qcom-ipq8064-ap148.dts | 83 +--------
arch/arm/boot/dts/qcom-ipq8064-ap161.dts | 7 +
arch/arm/boot/dts/qcom-ipq8064-v1.0.dtsi | 125 ++++++++++++++
arch/arm/boot/dts/qcom-ipq8064.dtsi | 286 +++++++++++++++++++++++++++++++
5 files changed, 426 insertions(+), 76 deletions(-)
create mode 100644 arch/arm/boot/dts/qcom-ipq8064-ap161.dts
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
next reply other threads:[~2018-08-03 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 14:10 Sricharan R [this message]
2018-08-03 14:10 ` [PATCH 1/5] arm: dts: qcom: Add pcie nodes for ipq8064 Sricharan R
2018-08-03 14:10 ` [PATCH 2/5] arm: dts: qcom: Add sdcc " Sricharan R
2018-08-03 14:10 ` [PATCH 3/5] arm: dts: qcom: Move common nodes to ipq8064-v.1.0.dtsi Sricharan R
2018-08-03 14:10 ` [PATCH 4/5] arm: dts: qcom: Add ipq8064-ap161.dts Sricharan R
2018-08-06 20:35 ` Rob Herring
2018-08-07 2:22 ` Sricharan R
2018-08-03 14:10 ` [PATCH 5/5] arm: dts: qcom: Add led and gpio-button nodes to ipq8064 boards Sricharan R
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=1533305419-29152-1-git-send-email-sricharan@codeaurora.org \
--to=sricharan@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=robh+dt@kernel.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).