From: Komal Bajaj <quic_kbajaj@quicinc.com>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Bjorn Andersson <quic_bjorande@quicinc.com>,
<quic_wcheng@quicinc.com>, <quic_ppratap@quicinc.com>,
Jack Pham <quic_jackp@quicinc.com>,
Krishna Kurapati PSSNV <quic_kriskura@quicinc.com>,
Komal Bajaj <quic_kbajaj@quicinc.com>
Subject: [PATCH v3 0/3] Add devicetree support of USB for QDU/QRU1000
Date: Thu, 2 May 2024 14:33:23 +0530 [thread overview]
Message-ID: <20240502090326.21489-1-quic_kbajaj@quicinc.com> (raw)
This series adds devicetree nodes to support interconnects and usb for qdu/qru1000.
This is based on previously sent driver series[1].
------
Changes in v3:
* As per comments on upstream[2], to get role-switch working on QDU/QRU1000, it was recommended to
use the actual TI switch driver. Since driver doesn't have the functionality to provide role-switch
based on gpio, thus reverting back USB dr_mode to peripheral and removed the remote end-point nodes
and usb-conn-gpio based role switch functionality.
* Link to v2: https://lore.kernel.org/linux-arm-msm/20240319091020.15137-1-quic_kbajaj@quicinc.com/
Changes in v2:
* Changes qmpphy node name
* Changes dr_mode to otg and added USB-B port USB role switch
* Dropped maximum-speed property from usb dwc3 node
* Link to v1: https://lore.kernel.org/linux-arm-msm/20240311120859.18489-1-quic_kbajaj@quicinc.com/
[1] https://lore.kernel.org/linux-arm-msm/20240502082017.13777-1-quic_kbajaj@quicinc.com/
[2] https://lore.kernel.org/all/CAA8EJppNZrLzT=vGS0NXnKJT_wL+bMB9jFhJ9K7b7FPgFQbcig@mail.gmail.com/
------
Komal Bajaj (3):
arm64: dts: qcom: qdu1000: Add USB3 and PHY support
arm64: dts: qcom: qdu1000-idp: enable USB nodes
arm64: dts: qcom: qru1000-idp: enable USB nodes
arch/arm64/boot/dts/qcom/qdu1000-idp.dts | 23 +++++
arch/arm64/boot/dts/qcom/qdu1000.dtsi | 120 +++++++++++++++++++++++
arch/arm64/boot/dts/qcom/qru1000-idp.dts | 23 +++++
3 files changed, 166 insertions(+)
--
2.42.0
next reply other threads:[~2024-05-02 9:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 9:03 Komal Bajaj [this message]
2024-05-02 9:03 ` [PATCH v3 1/3] arm64: dts: qcom: qdu1000: Add USB3 and PHY support Komal Bajaj
2024-05-02 9:03 ` [PATCH v3 2/3] arm64: dts: qcom: qdu1000-idp: enable USB nodes Komal Bajaj
2024-05-02 9:03 ` [PATCH v3 3/3] arm64: dts: qcom: qru1000-idp: " Komal Bajaj
2024-05-02 9:09 ` [PATCH v3 0/3] Add devicetree support of USB for QDU/QRU1000 Dmitry Baryshkov
2024-05-02 9:48 ` Krishna Kurapati PSSNV
2024-05-02 11:44 ` Dmitry Baryshkov
2024-05-08 6:11 ` Komal Bajaj
2024-05-08 8:08 ` Dmitry Baryshkov
2024-05-27 0:28 ` Bjorn Andersson
2024-05-27 1:36 ` Dmitry Baryshkov
2024-05-27 3:00 ` Bjorn Andersson
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=20240502090326.21489-1-quic_kbajaj@quicinc.com \
--to=quic_kbajaj@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_bjorande@quicinc.com \
--cc=quic_jackp@quicinc.com \
--cc=quic_kriskura@quicinc.com \
--cc=quic_ppratap@quicinc.com \
--cc=quic_wcheng@quicinc.com \
--cc=robh@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 read-only IMAP folder(s) and NNTP newsgroup(s).