From: Stephen Boyd <swboyd@chromium•org>
To: Bjorn Andersson <bjorn.andersson@linaro•org>
Cc: mark.rutland@arm•com, robh@kernel•org,
Jack Pham <jackp@codeaurora•org>,
devicetree@vger•kernel.org, gregkh@linuxfoundation•org,
linux-usb@vger•kernel.org, khasim.mohammed@linaro•org,
linux-kernel@vger•kernel.org, kishon@ti•com,
linux-arm-msm@vger•kernel.org, andy.gross@linaro•org,
Jorge Ramirez <jorge.ramirez-ortiz@linaro•org>,
shawn.guo@linaro•org, linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH v4 3/4] dt-bindings: Add Qualcomm USB SuperSpeed PHY bindings
Date: Fri, 06 Sep 2019 13:40:24 -0700 [thread overview]
Message-ID: <5d72c439.1c69fb81.484c6.fe28@mx.google.com> (raw)
In-Reply-To: <20190906182530.GD11938@tuxbook-pro>
Quoting Bjorn Andersson (2019-09-06 11:25:30)
> On Thu 05 Sep 22:26 PDT 2019, Stephen Boyd wrote:
>
> >
> > Yes this looks like the approach that should be taken. One question
> > though, is this a micro-b connector or a type-c connector on the board?
> > I thought it was a type-c, so then this USB gpio based connection driver
> > isn't an exact fit?
> >
>
> For this particular case it's a type c connector, but the port
> controller is operated completely passively (and there's no PD or DP
> involved), so the GPIO based approach seems like a good fit.
>
OK. Perhaps the binding needs an update then to have another compatible
string indicating type-c connector that's not able to support PD or DP?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-09-06 20:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 11:17 [PATCH v4 0/4] USB SS PHY for Qualcomm's QCS404 Jorge Ramirez-Ortiz
2019-02-07 11:17 ` [PATCH v4 1/4] dt-bindings: phy: remove qcom-dwc3-usb-phy Jorge Ramirez-Ortiz
2019-02-13 21:44 ` Rob Herring
2019-02-07 11:17 ` [PATCH v4 2/4] dt-bindings: connector: Add vbus-supply property Jorge Ramirez-Ortiz
2019-02-13 21:44 ` Rob Herring
2019-02-07 11:17 ` [PATCH v4 3/4] dt-bindings: Add Qualcomm USB SuperSpeed PHY bindings Jorge Ramirez-Ortiz
2019-02-13 21:43 ` Rob Herring
2019-02-23 16:52 ` Bjorn Andersson
2019-08-29 7:03 ` Jorge Ramirez
2019-08-30 16:01 ` Stephen Boyd
2019-08-30 16:45 ` Bjorn Andersson
2019-08-30 18:28 ` Stephen Boyd
2019-09-02 6:23 ` Jorge Ramirez
2019-09-03 17:39 ` Jack Pham
2019-09-03 21:45 ` Stephen Boyd
2019-09-03 23:34 ` Bjorn Andersson
2019-09-05 7:18 ` Jorge Ramirez
2019-09-05 17:58 ` Jack Pham
2019-09-06 5:26 ` Stephen Boyd
2019-09-06 18:25 ` Bjorn Andersson
2019-09-06 20:40 ` Stephen Boyd [this message]
2019-02-07 11:17 ` [PATCH v4 4/4] phy: qualcomm: usb: Add SuperSpeed PHY driver Jorge Ramirez-Ortiz
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=5d72c439.1c69fb81.484c6.fe28@mx.google.com \
--to=swboyd@chromium$(echo .)org \
--cc=andy.gross@linaro$(echo .)org \
--cc=bjorn.andersson@linaro$(echo .)org \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=jackp@codeaurora$(echo .)org \
--cc=jorge.ramirez-ortiz@linaro$(echo .)org \
--cc=khasim.mohammed@linaro$(echo .)org \
--cc=kishon@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-arm-msm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-usb@vger$(echo .)kernel.org \
--cc=mark.rutland@arm$(echo .)com \
--cc=robh@kernel$(echo .)org \
--cc=shawn.guo@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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