From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Krishna Kurapati <quic_kriskura@quicinc.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, quic_ppratap@quicinc.com,
quic_jackp@quicinc.com
Subject: Re: [PATCH v4 2/2] arm64: dts: qcom: Enable USB controllers for QCS8300
Date: Mon, 25 Nov 2024 16:55:19 +0100 [thread overview]
Message-ID: <71ff8a13-843a-434c-b5ac-3ad6171eb7bb@oss.qualcomm.com> (raw)
In-Reply-To: <20241114055152.1562116-3-quic_kriskura@quicinc.com>
On 14.11.2024 6:51 AM, Krishna Kurapati wrote:
subject:
"arm64: dts: qcom: qcs8300-ride: Enable USB controllers"
> Enable primary USB controller on QCS8300 Ride platform. The primary USB
> controller is made "peripheral", as this is intended to be connected to
> a host for debugging use cases.
>
> For using the controller in host mode, changing the dr_mode and adding
> appropriate pinctrl nodes to provide vbus would be sufficient.
>
> Signed-off-by: Krishna Kurapati <quic_kriskura@quicinc.com>
> ---
With that:
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2024-11-25 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 5:51 [PATCH v4 0/2] Add Devicetree support for USB controllers on QCS8300 Krishna Kurapati
2024-11-14 5:51 ` [PATCH v4 1/2] arm64: dts: qcom: Add support for usb nodes " Krishna Kurapati
2024-11-14 15:29 ` Konrad Dybcio
2024-11-14 5:51 ` [PATCH v4 2/2] arm64: dts: qcom: Enable USB controllers for QCS8300 Krishna Kurapati
2024-11-25 15:55 ` Konrad Dybcio [this message]
2025-01-08 4:54 ` [PATCH v4 0/2] Add Devicetree support for USB controllers on QCS8300 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=71ff8a13-843a-434c-b5ac-3ad6171eb7bb@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_jackp@quicinc.com \
--cc=quic_kriskura@quicinc.com \
--cc=quic_ppratap@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