From: Caleb Connolly <caleb.connolly@linaro.org>
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>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Caleb Connolly <caleb.connolly@linaro.org>
Subject: [PATCH 0/3] arm64: dts: qcom: make dev boards prefer usb host mode
Date: Mon, 24 Jun 2024 14:23:41 +0200 [thread overview]
Message-ID: <20240624-b4-rb2-fixes-v1-0-8d763ee4e42e@linaro.org> (raw)
Many of the Qualcomm development boards feature DRD capable
type-c ports. However these boards differ from smartphones in their
usage, and it's generally preferred that they would enter host mode by
default when given the choice.
This doesn't affect connection to a host-only PC, since the controller
is still DRD capable.
The RB1/2 are a special case, since they feature an on-board USB hub and
a manual dip switch to toggle between it and the type-c port. Preferring
host mode offers a useful hint to the software if it doesn't feature a
fully DRD capable USB controller driver, it can just use the default
mode (rather than defaulting to peripheral mode unconditionally).
---
Caleb Connolly (3):
arm64: dts: qcom: sm8650: move usb-role-switch to sm8650.dtsi
arm64: dts: qcom: sm8350: move usb-role-switch to sm8350.dtsi
arm64: dts: qcom: prefer host mode on dev boards
arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts | 1 +
arch/arm64/boot/dts/qcom/qrb2210-rb1.dts | 4 ++++
arch/arm64/boot/dts/qcom/qrb4210-rb2.dts | 4 ++++
arch/arm64/boot/dts/qcom/sm8150-hdk.dts | 1 +
arch/arm64/boot/dts/qcom/sm8350-hdk.dts | 3 +--
arch/arm64/boot/dts/qcom/sm8350.dtsi | 1 +
arch/arm64/boot/dts/qcom/sm8450-hdk.dts | 1 +
arch/arm64/boot/dts/qcom/sm8550-hdk.dts | 4 ++++
arch/arm64/boot/dts/qcom/sm8550-mtp.dts | 4 ++++
arch/arm64/boot/dts/qcom/sm8550-qrd.dts | 4 ++++
arch/arm64/boot/dts/qcom/sm8650-hdk.dts | 3 +--
arch/arm64/boot/dts/qcom/sm8650-mtp.dts | 3 +--
arch/arm64/boot/dts/qcom/sm8650-qrd.dts | 3 +--
arch/arm64/boot/dts/qcom/sm8650.dtsi | 1 +
14 files changed, 29 insertions(+), 8 deletions(-)
---
change-id: 20240624-b4-rb2-fixes-1ad33cd72f3a
base-commit: f76698bd9a8ca01d3581236082d786e9a6b72bb7
// Caleb (they/them)
next reply other threads:[~2024-06-24 12:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 12:23 Caleb Connolly [this message]
2024-06-24 12:23 ` [PATCH 1/3] arm64: dts: qcom: sm8650: move usb-role-switch to sm8650.dtsi Caleb Connolly
2024-06-24 13:10 ` Dmitry Baryshkov
2024-06-24 12:23 ` [PATCH 2/3] arm64: dts: qcom: sm8350: move usb-role-switch to sm8350.dtsi Caleb Connolly
2024-06-24 13:11 ` Dmitry Baryshkov
2024-06-24 12:23 ` [PATCH 3/3] arm64: dts: qcom: prefer host mode on dev boards Caleb Connolly
2024-06-24 12:28 ` neil.armstrong
2024-06-24 12:31 ` Dmitry Baryshkov
2024-06-24 12:33 ` neil.armstrong
2024-06-24 13:08 ` Dmitry Baryshkov
2024-06-24 12:34 ` Caleb Connolly
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=20240624-b4-rb2-fixes-v1-0-8d763ee4e42e@linaro.org \
--to=caleb.connolly@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.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=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
all inboxes | Powered by JetHome®