diff options
author | Johan Hovold <johan+linaro@kernel.org> | 2023-11-06 12:06:54 +0100 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2023-11-06 14:47:36 +0100 |
commit | 1a229d8690a0f8951fc4aa8b76a7efab0d8de342 (patch) | |
tree | 9809053cd2158958159385af1c03f310367d4ff6 /drivers/input/keyboard/omap4-keypad.c | |
parent | 7a784bcdd7e54f0599da3b2360e472238412623e (diff) | |
download | linux-stable-1a229d8690a0f8951fc4aa8b76a7efab0d8de342.tar.gz linux-stable-1a229d8690a0f8951fc4aa8b76a7efab0d8de342.tar.bz2 linux-stable-1a229d8690a0f8951fc4aa8b76a7efab0d8de342.zip |
Revert "usb: phy: add usb phy notify port status API"
This reverts commit a08799cf17c22375752abfad3b4a2b34b3acb287.
The recently added Realtek PHY drivers depend on the new port status
notification mechanism which was built on the deprecated USB PHY
implementation and devicetree binding.
Specifically, using these PHYs would require describing the very same
PHY using both the generic "phy" property and the deprecated "usb-phy"
property which is clearly wrong.
We should not be building new functionality on top of the legacy USB PHY
implementation even if it is currently stuck in some kind of
transitional limbo.
Revert the new notification interface which is broken by design.
Fixes: a08799cf17c2 ("usb: phy: add usb phy notify port status API")
Cc: stable@vger.kernel.org # 6.6
Cc: Stanley Chang <stanley_chang@realtek.com>
Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
Link: https://lore.kernel.org/r/20231106110654.31090-4-johan+linaro@kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/input/keyboard/omap4-keypad.c')
0 files changed, 0 insertions, 0 deletions