Hi Krzysztof,
> ...
> > +
> > +static const struct of_device_id usbphy_rtk_dt_match[] = {
> > + { .compatible = "realtek,rtd1295-usb2phy", .data =
> &rtd1295_phy_cfg },
> > + { .compatible = "realtek,rtd1312c-usb2phy", .data =
> &rtd1312c_phy_cfg },
> > + { .compatible = "realtek,rtd1315e-usb2phy", .data =
> &rtd1315e_phy_cfg },
> > + { .compatible = "realtek,rtd1319-usb2phy", .data =
> &rtd1319_phy_cfg },
> > + { .compatible = "realtek,rtd1319d-usb2phy", .data =
> &rtd1319d_phy_cfg },
> > + { .compatible = "realtek,rtd1395-usb2phy", .data =
> &rtd1395_phy_cfg },
> > + { .compatible = "realtek,rtd1395-usb2phy-2port", .data =
> &rtd1395_phy_cfg_2port },
> > + { .compatible = "realtek,rtd1619-usb2phy", .data =
> &rtd1619_phy_cfg },
> > + { .compatible = "realtek,rtd1619b-usb2phy", .data =
> > +&rtd1619b_phy_cfg },
>
> Why is this sent separately from the bindings?
The binding is ready on 612ad27a30455 (dt-bindings: phy: realtek: Add Realtek DHC RTD SoC USB 2.0 PHY)
This patch is resubmit base on 7a784bcdd7e5 (Revert "phy: realtek: usb: Add driver for the Realtek SoC USB 2.0 PHY")
to avoid using legacy USB PHY framework.
> > + {},
> > +};
> > +MODULE_DEVICE_TABLE(of, usbphy_rtk_dt_match);
> > +
> > +static struct platform_driver rtk_usb2phy_driver = {
> > + .probe = rtk_usb2phy_probe,
> > + .remove_new = rtk_usb2phy_remove,
> > + .driver = {
> > + .name = "rtk-usb2phy",
> > + .of_match_table = usbphy_rtk_dt_match,
> > + },
> > +};
> > +
> > +module_platform_driver(rtk_usb2phy_driver);
> > +
> > +MODULE_LICENSE("GPL");
> > +MODULE_ALIAS("platform: rtk-usb2phy");
>
> You should not need MODULE_ALIAS() in normal cases. If you need it, usually it
> means your device ID table is wrong (e.g. misses either entries or
> MODULE_DEVICE_TABLE()). MODULE_ALIAS() is not a substitute for
> incomplete ID table.
>
I will remove this.
Thanks,
Stanley
