From: Alexander Koskovich <AKoskovich@pm.me>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexander Koskovich <akoskovich@pm.me>
Subject: [PATCH RFC 0/2] usb: typec: qcom: Add shared USBIN VBUS detection via GPIO
Date: Sun, 08 Mar 2026 23:20:19 +0000 [thread overview]
Message-ID: <20260308-qcom-typec-shared-vbus-v1-0-7d574b91052a@pm.me> (raw)
The ASUS ROG Phone 3 has two USB-C ports whose VBUS lines are both
wired to the single USBIN input on the PM8150B PMIC. This means the
Type-C port controller cannot distinguish which port is providing
VBUS, causing one port to be unusable when the other has VBUS present
from a charger or PC.
The downstream vendor driver also appears to be touching
TYPE_C_CRUDE_SENSOR_CFG_REG for restoring CC detection after enabling
BYPASS_VSAFE0V but does not appear to be necessary with the upstream
TCPM stack?
Feedback on whether additional register configuration is needed would be
appreciated, but functionally this appears to work as is. After these
changes and configuring the property in DTS I am able to use a flash
drive on the side USB port (pm8150b_typec) while I am connected to a
charger or my PC via the bottom USB port (rt1715).
Signed-off-by: Alexander Koskovich <akoskovich@pm.me>
---
Alexander Koskovich (2):
dt-bindings: usb: qcom,pmic-typec: Document vbus-detect-gpios property
usb: typec: qcom: Add support for shared USBIN VBUS detection
.../devicetree/bindings/usb/qcom,pmic-typec.yaml | 6 +++
drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_port.c | 46 +++++++++++++++++++++-
2 files changed, 50 insertions(+), 2 deletions(-)
---
base-commit: 11439c4635edd669ae435eec308f4ab8a0804808
change-id: 20260308-qcom-typec-shared-vbus-7d37c6b2d155
Best regards,
--
Alexander Koskovich <akoskovich@pm.me>
next reply other threads:[~2026-03-08 23:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 23:20 Alexander Koskovich [this message]
2026-03-08 23:20 ` [PATCH RFC 1/2] dt-bindings: usb: qcom,pmic-typec: Document vbus-detect-gpios property Alexander Koskovich
2026-03-11 23:02 ` Bryan O'Donoghue
2026-03-16 10:15 ` Konrad Dybcio
2026-03-12 2:34 ` Dmitry Baryshkov
2026-03-12 2:59 ` Alexander Koskovich
2026-03-08 23:20 ` [PATCH RFC 2/2] usb: typec: qcom: Add support for shared USBIN VBUS detection Alexander Koskovich
2026-03-11 13:01 ` Konrad Dybcio
2026-03-11 14:39 ` Bryan O'Donoghue
2026-03-11 16:24 ` Alexander Koskovich
2026-03-11 23:05 ` Bryan O'Donoghue
2026-03-12 6:18 ` Alexander Koskovich
2026-03-11 14:50 ` [PATCH RFC 0/2] usb: typec: qcom: Add shared USBIN VBUS detection via GPIO Bryan O'Donoghue
2026-03-11 17:37 ` Alexander Koskovich
2026-03-11 23:00 ` Bryan O'Donoghue
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=20260308-qcom-typec-shared-vbus-v1-0-7d574b91052a@pm.me \
--to=akoskovich@pm.me \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®