From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Stephan Gerhold <stephan@gerhold.net>
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
robh+dt@kernel.org, krzk+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
shawn.guo@linaro.org, jun.nie@linaro.org, benl@squareup.com,
jwillcox@squareup.com, jgates@squareup.com, mchen@squareup.com,
zac@squareup.com
Subject: Re: [PATCH v1 4/4] arm64: dts: Add msm8939 Sony Xperia M4 Aqua
Date: Fri, 27 May 2022 01:03:50 +0300 [thread overview]
Message-ID: <ad7106bb-ed7d-8d6f-0b3a-3e2dfeee0168@linaro.org> (raw)
In-Reply-To: <552547c1-36c3-8d7e-0fd5-1b22fd184b4b@linaro.org>
On 20/04/2022 01:03, Bryan O'Donoghue wrote:
> On 19/04/2022 20:27, Stephan Gerhold wrote:
>> tulip seems to have qcom,usbid-gpio = <&msm_gpio 110 0>; downstream.
>> Have you tried setting it up using linux,extcon-usb-gpio?
>> See e.g. msm8916-longcheer-l8910, it has a similar setup (it also uses
>> smb1360 for charging actually).
>>
>> The advantage is that you don't need the manual role switching using
>> "usb-role-switch", USB OTG adapters should be detected automatically.
>
> My understanding is "no new extcon" - certainly as driver
> implementations I assume that also extends to dts..
I think, if the driver supports only extcon interface, you have to use
it (leaving aside a good nice option of rewriting qcom,ci-hdrc/ulpi to
also support USB role switching mechanisms).
--
With best wishes
Dmitry
next prev parent reply other threads:[~2022-05-26 22:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 1:08 [PATCH v1 0/4] Add MSM8939 SoC support with two devices Bryan O'Donoghue
2022-04-19 1:09 ` [PATCH v1 1/4] dt-bindings: arm: qcom: Document MSM8939 SoC binding Bryan O'Donoghue
2022-04-19 7:13 ` Krzysztof Kozlowski
2022-04-19 12:12 ` Rob Herring
2022-04-19 1:09 ` [PATCH v1 2/4] arm64: dts: Add msm8939 SoC Bryan O'Donoghue
2022-04-19 7:33 ` Krzysztof Kozlowski
2022-04-19 8:30 ` Bryan O'Donoghue
2022-04-19 8:44 ` Krzysztof Kozlowski
2022-04-20 9:31 ` Jun Nie
2022-04-20 9:38 ` Krzysztof Kozlowski
2022-04-20 9:57 ` Jun Nie
2022-04-20 10:00 ` Jun Nie
2022-04-20 10:10 ` Krzysztof Kozlowski
2022-04-20 10:09 ` Krzysztof Kozlowski
2022-04-19 17:21 ` Vincent Knecht
2022-04-19 22:01 ` Bryan O'Donoghue
2022-05-26 13:32 ` Bryan O'Donoghue
2022-04-19 18:31 ` Stephan Gerhold
2022-04-20 10:12 ` Jun Nie
2022-04-19 18:47 ` Vincent Knecht
2022-04-19 21:11 ` Bjorn Andersson
2022-04-20 5:34 ` Stephan Gerhold
2022-04-19 1:09 ` [PATCH v1 3/4] arm64: dts: Add aqp8039-t2 board Bryan O'Donoghue
2022-04-19 7:35 ` Krzysztof Kozlowski
2022-04-19 19:20 ` Stephan Gerhold
2022-04-19 21:43 ` Bryan O'Donoghue
2022-04-19 21:39 ` Bjorn Andersson
2022-04-19 21:52 ` Bryan O'Donoghue
2022-04-19 1:09 ` [PATCH v1 4/4] arm64: dts: Add msm8939 Sony Xperia M4 Aqua Bryan O'Donoghue
2022-04-19 19:27 ` Stephan Gerhold
2022-04-19 22:03 ` Bryan O'Donoghue
2022-04-20 5:36 ` Stephan Gerhold
2022-05-26 22:03 ` Dmitry Baryshkov [this message]
2022-04-19 21:51 ` 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=ad7106bb-ed7d-8d6f-0b3a-3e2dfeee0168@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=benl@squareup.com \
--cc=bjorn.andersson@linaro.org \
--cc=bryan.odonoghue@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jgates@squareup.com \
--cc=jun.nie@linaro.org \
--cc=jwillcox@squareup.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=mchen@squareup.com \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@linaro.org \
--cc=stephan@gerhold.net \
--cc=zac@squareup.com \
/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).