On 07/11/2023 09:31, Stanley Chang wrote:
> Realtek DHC (digital home center) RTD SoCs support DWC3 XHCI USB
> controller. Added the driver to drive the USB 2.0 PHY transceivers.
>
> Note: New driver,remove the port status notification on legacy USB PHY.
> Use the generic PHY to notify the usb device connect and disconnect.
> To avoid using these PHYs would require describing the very same
> PHY using both the generic "phy" property and the deprecated "usb-phy"
> property.
>
> Signed-off-by: Stanley Chang <stanley_chang@xxxxxxxxxxx>
> ---
> v1 to v2 change:
...
> +
> +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?
> + {},
> +};
> +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.
Best regards,
Krzysztof
