Commit 13e1f735 authored by Uwe Kleine-König's avatar Uwe Kleine-König Committed by Vinod Koul

phy: ti: phy-dm816x-usb: Convert to platform remove callback returning void

The .remove() callback for a platform driver returns an int which makes
many driver authors wrongly assume it's possible to do error handling by
returning an error code. However the value returned is (mostly) ignored
and this typically results in resource leaks. To improve here there is a
quest to make the remove callback return void. In the first step of this
quest all drivers are converted to .remove_new() which already returns
void.

Trivially convert this driver from always returning zero in the remove
callback to the void returning variant.
Signed-off-by: default avatarUwe Kleine-König <u.kleine-koenig@pengutronix.de>
Link: https://lore.kernel.org/r/20230307115900.2293120-28-u.kleine-koenig@pengutronix.deSigned-off-by: default avatarVinod Koul <vkoul@kernel.org>
parent 0196c847
...@@ -257,20 +257,18 @@ static int dm816x_usb_phy_probe(struct platform_device *pdev) ...@@ -257,20 +257,18 @@ static int dm816x_usb_phy_probe(struct platform_device *pdev)
return error; return error;
} }
static int dm816x_usb_phy_remove(struct platform_device *pdev) static void dm816x_usb_phy_remove(struct platform_device *pdev)
{ {
struct dm816x_usb_phy *phy = platform_get_drvdata(pdev); struct dm816x_usb_phy *phy = platform_get_drvdata(pdev);
usb_remove_phy(&phy->phy); usb_remove_phy(&phy->phy);
pm_runtime_disable(phy->dev); pm_runtime_disable(phy->dev);
clk_unprepare(phy->refclk); clk_unprepare(phy->refclk);
return 0;
} }
static struct platform_driver dm816x_usb_phy_driver = { static struct platform_driver dm816x_usb_phy_driver = {
.probe = dm816x_usb_phy_probe, .probe = dm816x_usb_phy_probe,
.remove = dm816x_usb_phy_remove, .remove_new = dm816x_usb_phy_remove,
.driver = { .driver = {
.name = "dm816x-usb-phy", .name = "dm816x-usb-phy",
.pm = &dm816x_usb_phy_pm_ops, .pm = &dm816x_usb_phy_pm_ops,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment