linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] usb: dwc3: qcom: Remove extcon functionality from glue
Date: Sun, 20 Jul 2025 13:40:19 +0200	[thread overview]
Message-ID: <2025072021-rounding-oversized-5b4b@gregkh> (raw)
In-Reply-To: <20250718053856.2859946-1-krishna.kurapati@oss.qualcomm.com>

On Fri, Jul 18, 2025 at 11:08:56AM +0530, Krishna Kurapati wrote:
> Deprecate usage of extcon functionality from the glue driver.

It's not "deprecate", it is "delete".  "deprecate" means that you don't
want future users of this, you are flat out deleting it entirely.

> Now
> that the glue driver is a flattened implementation, all existing
> DTs would eventually move to new bindings.

When is this happening?

> While doing so let them
> make use of role-switch/ typec frameworks to provide role data
> rather than using extcon. None of the existing in-kernel extcon users
> have moved to using new bindings yet, so this change doesn't affect
> any existing users.

I don't understand, who does this affect?

> On upstream, summary of targets/platforms using extcon is as follows:

What is "upstream" here?  In-tree?  We only have one development place :)

> 1. MSM8916 and MSM8939 use Chipidea controller, hence the changes have no
> effect on them.
> 
> 2. Of the other extcon users, most of them use "linux,extcon-usb-gpio"
> driver which relies on id/vbus gpios to inform role changes. This can be
> transitioned to role switch based driver (usb-conn-gpio) while flattening
> those platforms to move away from extcon and rely on role switching.

"most" do, but not all.

> 3. The one target that uses dwc3 controller and extcon and is not based
> on reading gpios is "arch/arm64/boot/dts/qcom/msm8996-xiaomi-common.dtsi".
> This platform uses TI's Type-C Port controller chip to provide extcon. If
> usb on this platform is being flattened, then effort should be put in to
> define a usb-c-connector device in DT and make use of role switch in
> TUSB320L driver.

I really still do not understand what is happening here.

Does this break existing in-tree users?  If yes, we can't do that.  If
no, they this is just unused code?  That's all that we should be
concerned about here.

> ---
> Changes in v4:
> Updated commit text to reflect the patch doesn't affect in-kernel users.
> Removed RB tags from v3 since commit text is changed.
> 
> Link to v3:
> https://lore.kernel.org/all/20250714044703.2091075-1-krishna.kurapati@oss.qualcomm.com/

What changed in v3?  v2?  v1?

Please properly document this.

thanks,

greg k-h

  parent reply	other threads:[~2025-07-20 11:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18  5:38 [PATCH v4] usb: dwc3: qcom: Remove extcon functionality from glue Krishna Kurapati
2025-07-18  8:52 ` Konrad Dybcio
2025-07-20 11:40 ` Greg Kroah-Hartman [this message]
2025-07-22  7:18   ` Krishna Kurapati

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=2025072021-rounding-oversized-5b4b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=krishna.kurapati@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.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 NNTP newsgroup(s).