From: Val Packett <val@packett.cool>
To: Michael Scott <mike.scott@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org
Cc: vkoul@kernel.org, neil.armstrong@linaro.org,
dmitry.baryshkov@oss.qualcomm.com, wesley.cheng@oss.qualcomm.com,
abelvesa@kernel.org, faisal.hassan@oss.qualcomm.com,
linux-phy@lists.infradead.org, andersson@kernel.org,
konradybcio@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
bryan.odonoghue@linaro.org, laurentiu.tudor1@dell.com,
alex.vinarskis@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] phy: qcom: qmp-combo fixes + x1-dell-thena DT maintenance
Date: Thu, 21 May 2026 01:39:12 -0300 [thread overview]
Message-ID: <1f659806-bde5-4f8b-99ef-339f680bcf65@packett.cool> (raw)
In-Reply-To: <20260521010935.1333494-1-mike.scott@oss.qualcomm.com>
On 5/20/26 10:09 PM, Michael Scott wrote:
> Four patches:
>
> * Two pre-existing bug fixes in phy-qcom-qmp-combo that are reachable
> today on any board which registers a usb_role_switch on this PHY,
> and will become reachable on more X1E boards as their Type-C
> support matures (patches 1-2).
> [..]
Thanks for digging into this!
I have successfully used automatic role-switching (even switching
between USB2 gadget and USB3+DP mostly worked fine) but I do remember
manual sysfs switching causing more issues..
Would be great to see no more dr_mode = "host" upstream. Though I
vaguely remember some objections related to booting from USB (?)
~val
next prev parent reply other threads:[~2026-05-21 4:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 1:09 Michael Scott
2026-05-21 1:09 ` [PATCH v2 1/4] phy: qcom: qmp-combo: skip USB power_off/exit after device teardown Michael Scott
2026-05-21 11:58 ` Bryan O'Donoghue
2026-05-22 15:59 ` Michael Scott
2026-05-21 1:09 ` [PATCH v2 2/4] phy: qcom: qmp-combo: track whether the cached typec_mux mode was committed to hardware Michael Scott
2026-05-21 12:00 ` Bryan O'Donoghue
2026-05-21 1:09 ` [PATCH v2 3/4] arm64: dts: qcom: x1-dell-thena: mark l12b and l15b always-on Michael Scott
2026-05-21 4:28 ` Val Packett
2026-06-16 12:22 ` Konrad Dybcio
2026-05-21 1:09 ` [PATCH v2 4/4] arm64: dts: qcom: x1-dell-thena: bump linux,cma to 256 MiB Michael Scott
2026-05-21 3:52 ` Val Packett
2026-05-22 17:42 ` Rob Clark
2026-05-21 12:04 ` Bryan O'Donoghue
2026-05-22 17:16 ` Michael Scott
2026-05-22 21:33 ` Bryan O'Donoghue
2026-07-11 18:24 ` Bjorn Andersson
2026-05-21 4:39 ` Val Packett [this message]
2026-07-11 19:49 ` (subset) [PATCH v2 0/4] phy: qcom: qmp-combo fixes + x1-dell-thena DT maintenance 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=1f659806-bde5-4f8b-99ef-339f680bcf65@packett.cool \
--to=val@packett.cool \
--cc=abelvesa@kernel.org \
--cc=alex.vinarskis@gmail.com \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=faisal.hassan@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=laurentiu.tudor1@dell.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mike.scott@oss.qualcomm.com \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=vkoul@kernel.org \
--cc=wesley.cheng@oss.qualcomm.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