From: Johan Hovold <johan@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Johan Hovold <johan+linaro@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Marek <jonathan@marek.ca>,
Stephan Gerhold <stephan.gerhold@linaro.org>,
Abel Vesa <abel.vesa@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [PATCH v2 0/2] arm64: dts: qcom: x1e80100: fix USB OTG regressions
Date: Mon, 9 Dec 2024 16:30:36 +0100 [thread overview]
Message-ID: <Z1cNHOqlRk2Cxwvd@hovoldconsulting.com> (raw)
In-Reply-To: <iw2c4fceyppf2w2gueevsqsz2z7hatbqo33vufx3veatprczu5@u4k3j2igy6ee>
On Mon, Dec 09, 2024 at 03:23:05PM +0200, Dmitry Baryshkov wrote:
> On Mon, Dec 09, 2024 at 12:19:03PM +0100, Johan Hovold wrote:
> > A recent change enabling OTG mode on the Lenovo ThinkPad T14s USB-C
> > ports can break SuperSpeed device hotplugging.
> >
> > Abel noticed that the corresponding commit for the CRD also triggers a
> > hard reset during resume from suspend.
> >
> > With retimer (and orientation detection) support not even merged yet,
> > let's revert at least until we have stable host mode in mainline.
> >
> > Note that Stephan and Dmitry have already identified other problems with
> > the offending commits here:
> >
> > https://lore.kernel.org/all/ZxZO6Prrm2ITUZMQ@linaro.org/
> > https://lore.kernel.org/all/hw2pdof4ajadjsjrb44f2q4cz4yh5qcqz5d3l7gjt2koycqs3k@xx5xvd26uyef
> > Changes in v2
> > - revert also the corresponding patch for the CRD which breaks suspend
>
> As you are reverting two commits, please revert the third one too, it
> breaks pmic-glink.
Can you be more specific?
I was gonna say that pmic_glink works since hotplug and orientation
detection still works, but I tested now with DP altmode and that is
indeed broken unless I revert the third commit (f042bc234c2e ("arm64:
dts: qcom: x1e80100: enable OTG on USB-C controllers")).
Was that what you had in mind? Can you explain why that breaks?
I'll respin with a v3, but please answer the above first.
> > Johan Hovold (2):
> > Revert "arm64: dts: qcom: x1e78100-t14s: enable otg on usb-c ports"
> > Revert "arm64: dts: qcom: x1e80100-crd: enable otg on usb ports"
Johan
next prev parent reply other threads:[~2024-12-09 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 11:19 [PATCH v2 0/2] arm64: dts: qcom: x1e80100: fix USB OTG regressions Johan Hovold
2024-12-09 11:19 ` [PATCH v2 1/2] Revert "arm64: dts: qcom: x1e78100-t14s: enable otg on usb-c ports" Johan Hovold
2024-12-09 11:19 ` [PATCH v2 2/2] Revert "arm64: dts: qcom: x1e80100-crd: enable otg on usb ports" Johan Hovold
2024-12-09 13:23 ` [PATCH v2 0/2] arm64: dts: qcom: x1e80100: fix USB OTG regressions Dmitry Baryshkov
2024-12-09 15:30 ` Johan Hovold [this message]
2024-12-09 16:00 ` Dmitry Baryshkov
2024-12-10 10:45 ` Johan Hovold
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=Z1cNHOqlRk2Cxwvd@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=jonathan@marek.ca \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=robh@kernel.org \
--cc=stephan.gerhold@linaro.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