[PATCH v4 0/2] Modify interrupt handling for eUSB2 Phy targets
From: Krishna Kurapati
Date: Thu Jul 09 2026 - 05:11:24 EST
eUSB2 targets handle wakeup interrupts differently depending on device
speed when operating in host mode.
According to the eUSB2 specification, remote wakeup signaling in host
mode is detected via different data-line assertions based on the
connected device speed.
When a low-speed device is connected, the host repeater drives eD+ to
logic '1' upon detecting a K-state on the USB lines during remote wakeup
(eUSB2 specification, Section 5.5.14).
When a full-speed or high-speed device is connected, the host repeater
drives eD- to logic '1' upon detecting a K-state on the USB line during
remote wakeup (eUSB2 specification, Sections 5.5.15 and 5.5.18).
Since the eUSB2 PHY's "DP" and "DM" interrupt lines monitor the eD+ and
eD- line states, configure the wakeup interrupts accordingly
Add new property to dt-binding indicating that the USB controller on SoC
has eUSB2 Phys or not.
Signed-off-by: Krishna Kurapati <krishna.kurapati@xxxxxxxxxxxxxxxx>
---
Changes in v4:
- Moved to using binding approach as suggested by Thinh
Link to v3:
https://lore.kernel.org/all/20260511094422.3561509-1-krishna.kurapati@xxxxxxxxxxxxxxxx/
Changes in v3:
- Removed multiple glymur-dwc3-mp pdata entries
- Replaced use of ternary operators with if-else
Link to v2:
https://lore.kernel.org/all/20260505194242.1947891-1-krishna.kurapati@xxxxxxxxxxxxxxxx/
Changes in v2:
- Updated commit message
- added supported eUSB2 targets
Link to v1:
https://lore.kernel.org/all/20260502095616.666938-1-krishna.kurapati@xxxxxxxxxxxxxxxx/
---
Krishna Kurapati (2):
dt-bindings: qcom,snps-dwc3: Add property indicating presence of eUSB2 phy
usb: dwc3: qcom: Modify interrupt handling for eUSB2 Phy targets
.../devicetree/bindings/usb/qcom,snps-dwc3.yaml | 7 ++++
drivers/usb/dwc3/dwc3-qcom.c | 40 ++++++++++++++++------
2 files changed, 37 insertions(+), 10 deletions(-)
---
base-commit: 62481c92444386d46b3c4a9c3dbcd4917f07d138
change-id: 20260709-eusb2-interrupt-handling-v5-da49ab5d5a84
Best regards,
--
Krishna Kurapati <krishna.kurapati@xxxxxxxxxxxxxxxx>