usb: mtu3: drop CONFIG_OF

The driver can match only the devices created by the OF core
via the DT table, so the table should be always used.

Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
Link: https://lore.kernel.org/r/1616482975-17841-12-git-send-email-chunfeng.yun@mediatek.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

diff --git a/drivers/usb/mtu3/mtu3_plat.c b/drivers/usb/mtu3/mtu3_plat.c
index d44d541..7786a95 100644 (file)
--- a/drivers/usb/mtu3/mtu3_plat.c
+++ b/drivers/usb/mtu3/mtu3_plat.c
@@ -502,25 +502,20 @@ static const struct dev_pm_ops mtu3_pm_ops = {
 
 #define DEV_PM_OPS (IS_ENABLED(CONFIG_PM) ? &mtu3_pm_ops : NULL)
 
-#ifdef CONFIG_OF
-
 static const struct of_device_id mtu3_of_match[] = {
        {.compatible = "mediatek,mt8173-mtu3",},
        {.compatible = "mediatek,mtu3",},
        {},
 };
-
 MODULE_DEVICE_TABLE(of, mtu3_of_match);
 
-#endif
-
 static struct platform_driver mtu3_driver = {
        .probe = mtu3_probe,
        .remove = mtu3_remove,
        .driver = {
                .name = MTU3_DRIVER_NAME,
                .pm = DEV_PM_OPS,
-               .of_match_table = of_match_ptr(mtu3_of_match),
+               .of_match_table = mtu3_of_match,
        },
 };
 module_platform_driver(mtu3_driver);