diff options
| author | Krishna Kurapati <quic_kriskura@quicinc.com> | 2023-12-27 14:49:51 +0530 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-01-04 16:04:50 +0100 |
| commit | aefdcd89d72bd92e68fe0a8182ed98b4a6b91efa (patch) | |
| tree | e17c6e270f1b20d33d4c539abd56810e676d3e78 /drivers/vfio/vfio_iommu_spapr_tce.c | |
| parent | 53c6d854be4e93fa21b80bd40e3a666c3961e82c (diff) | |
usb: dwc3: qcom: Rename hs_phy_irq to qusb2_phy_irq
For wakeup to work, driver needs to enable interrupts that depict what is
happening on the DP/DM lines. On QUSB targets, this is identified by
qusb2_phy whereas on SoCs using Femto PHY, separate {dp,dm}_hs_phy_irq's
are used instead.
The implementation incorrectly names qusb2_phy interrupts as "hs_phy_irq".
Clean this up so that driver would be using only qusb2/(dp & dm) for wakeup
purposes.
For devices running older kernels, this won't break any functionality
because the interrupt configurations in QUSB2 PHY based SoCs is done
by configuring QUSB2PHY_INTR_CTRL register in PHY address space and it was
never armed properly right from the start.
Signed-off-by: Krishna Kurapati <quic_kriskura@quicinc.com>
Acked-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Link: https://lore.kernel.org/r/20231227091951.685-3-quic_kriskura@quicinc.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/vfio/vfio_iommu_spapr_tce.c')
0 files changed, 0 insertions, 0 deletions