From: Vivek Gautam <vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: andy.gross-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: bjorn.andersson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Vivek Gautam
<vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Subject: [PATCH 0/4] arm64: dt: msm8996: Enable support for qmp and qusb2 phy, and USB
Date: Mon, 31 Jul 2017 12:14:40 +0530 [thread overview]
Message-ID: <1501483484-2207-1-git-send-email-vivek.gautam@codeaurora.org> (raw)
Adding patches to enable qusb2 and qmp phy controller for PCIe and USB,
and to enable USB 2.0 and 3.0 support on msm8996 chipset.
Enabling the support for apq8096-db820c board.
Patch series dependencies:
1) Glink-rpm device tree support for 8996:
https://www.spinics.net/lists/linux-arm-msm/msg29046.html
2) Dt binding fix for pipe clock source:
a. https://patchwork.kernel.org/patch/9870865/
b. https://patchwork.kernel.org/patch/9870871/
3) pmi8994 gpio support:
https://lkml.org/lkml/2017/7/28/346
Tested the series on dragonboard db820c target.
Vivek Gautam (4):
arm64: dts: msm8996: Add device node for qcom qusb2 phy
arm64: dts: msm8996: Add device node for qcom qmp-phy for usb
arm64: dts: msm8996: Add device node for qcom qmp-phy for pcie
arm64: dts: msm8996: Add device node for qcom,dwc3
.../boot/dts/qcom/apq8096-db820c-pmic-pins.dtsi | 24 +++
arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 50 +++++
arch/arm64/boot/dts/qcom/msm8996.dtsi | 203 +++++++++++++++++++++
3 files changed, 277 insertions(+)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-07-31 6:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 6:44 Vivek Gautam [this message]
2017-07-31 6:44 ` [PATCH 1/4] arm64: dts: msm8996: Add device node for qcom qusb2 phy Vivek Gautam
2017-07-31 6:44 ` [PATCH 2/4] arm64: dts: msm8996: Add device node for qcom qmp-phy for usb Vivek Gautam
2017-07-31 6:44 ` [PATCH 3/4] arm64: dts: msm8996: Add device node for qcom qmp-phy for pcie Vivek Gautam
2017-07-31 6:44 ` [PATCH 4/4] arm64: dts: msm8996: Add device node for qcom,dwc3 Vivek Gautam
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=1501483484-2207-1-git-send-email-vivek.gautam@codeaurora.org \
--to=vivek.gautam-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
--cc=andy.gross-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=bjorn.andersson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.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).