Vivek Gautam wrote: > > Moving register and structure definitions to header file, > and keeping the generic functions to be used across > multiple PHYs in common file "samsung-usbphy.c". > Also renaming the usb 2.0 phy driver to "samsung-usb2.c" Just in my opinion, Samsung-usb2phy is more clear?...In addition, I looked at using SAMSUNG_USB2PHY as a statement. > > Signed-off-by: Vivek Gautam <gautam.vivek@xxxxxxxxxxx> > --- > > Changes from v3: > - Using separate config SAMSUNG_USB2PHY dependent on > SAMSUNG_USBPHY for samsung-usb2 type PHY controller. > > drivers/usb/phy/Kconfig | 14 +- > drivers/usb/phy/Makefile | 1 + > drivers/usb/phy/samsung-usb2.c | 511 +++++++++++++++++++++++++++ > drivers/usb/phy/samsung-usbphy.c | 714 +------------------------------------- > drivers/usb/phy/samsung-usbphy.h | 247 +++++++++++++ > 5 files changed, 778 insertions(+), 709 deletions(-) > create mode 100644 drivers/usb/phy/samsung-usb2.c > create mode 100644 drivers/usb/phy/samsung-usbphy.h > > diff --git a/drivers/usb/phy/Kconfig b/drivers/usb/phy/Kconfig > index fae4d08..cc0d230 100644 > --- a/drivers/usb/phy/Kconfig > +++ b/drivers/usb/phy/Kconfig > @@ -48,8 +48,18 @@ config USB_RCAR_PHY > > config SAMSUNG_USBPHY > bool "Samsung USB PHY controller Driver" > - depends on USB_S3C_HSOTG || USB_EHCI_S5P || > USB_OHCI_EXYNOS So this can be selected without any dependency? > select USB_OTG_UTILS > help > - Enable this to support Samsung USB phy controller for samsung > + Enable this to support Samsung USB phy controllers for Samsung > SoCs. Hmm, according to above comments, this should be enabled under Samsung SoC? > + > +if SAMSUNG_USBPHY Why is this needed here? > + > +config SAMSUNG_USB2PHY > + bool "Samsung USB 2.0 PHY controller Driver" > + depends on USB_S3C_HSOTG || USB_EHCI_S5P || > USB_OHCI_EXYNOS > + help > + Enable this to support Samsung USB 2.0 (High Speed) phy controller > + for Samsung SoCs. > + > +endif > diff --git a/drivers/usb/phy/Makefile b/drivers/usb/phy/Makefile > index ec304f6..7ba9862 100644 > --- a/drivers/usb/phy/Makefile > +++ b/drivers/usb/phy/Makefile > @@ -10,3 +10,4 @@ obj-$(CONFIG_MV_U3D_PHY) += > mv_u3d_phy.o > obj-$(CONFIG_USB_EHCI_TEGRA) += tegra_usb_phy.o > obj-$(CONFIG_USB_RCAR_PHY) += rcar-phy.o > obj-$(CONFIG_SAMSUNG_USBPHY) += samsung-usbphy.o > +obj-$(CONFIG_SAMSUNG_USB2PHY) += samsung-usb2.o > diff --git a/drivers/usb/phy/samsung-usb2.c b/drivers/usb/phy/samsung- > usb2.c > new file mode 100644 > index 0000000..9a9d1d0 > --- /dev/null > +++ b/drivers/usb/phy/samsung-usb2.c > @@ -0,0 +1,511 @@ > +/* linux/drivers/usb/phy/samsung-usb2.c > + * > + * Copyright (c) 2012 Samsung Electronics Co., Ltd. > + * http://www.samsung.com > + * > + * Author: Praveen Paneri <p.paneri@xxxxxxxxxxx> > + * > + * Samsung USB2.0 PHY transceiver; talks to S3C HS OTG controller, EHCI-S5P > and > + * OHCI-EXYNOS controllers. > + * > + * This program is free software; you can redistribute it and/or modify > + * it under the terms of the GNU General Public License version 2 as > + * published by the Free Software Foundation. > + * > + * This program is distributed in the hope that it will be useful, > + * but WITHOUT ANY WARRANTY; without even the implied warranty of > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > + * GNU General Public License for more details. > + */ > + > +#include <linux/module.h> > +#include <linux/platform_device.h> > +#include <linux/clk.h> > +#include <linux/delay.h> > +#include <linux/device.h> > +#include <linux/err.h> > +#include <linux/io.h> > +#include <linux/of.h> > +#include <linux/usb/otg.h> > +#include <linux/usb/samsung_usb_phy.h> > +#include <linux/platform_data/samsung-usbphy.h> > + > +#include "samsung-usbphy.h" > + > +int samsung_usbphy_set_host(struct usb_otg *otg, struct usb_bus *host) For naming, if you want to support usb 2.0 phy here, the name of fuction should be changed to more clear name such as usb2phy or whatever. As I'm understanding, the samsung-usbphy.c can be used for common stuff and this is for only usb 2.0 phy. [...] > +#ifdef CONFIG_OF > +static const struct of_device_id samsung_usbphy_dt_match[] = { > + { > + .compatible = "samsung,s3c64xx-usbphy", > + .data = &usbphy_s3c64xx, > + }, { > + .compatible = "samsung,exynos4210-usbphy", > + .data = &usbphy_exynos4, > + }, { > + .compatible = "samsung,exynos5250-usbphy", > + .data = &usbphy_exynos5 > + }, > + {}, > +}; > +MODULE_DEVICE_TABLE(of, samsung_usbphy_dt_match); > +#endif > + > +static struct platform_device_id samsung_usbphy_driver_ids[] = { > + { > + .name = "s3c64xx-usbphy", > + .driver_data = (unsigned long)&usbphy_s3c64xx, > + }, { > + .name = "exynos4210-usbphy", > + .driver_data = (unsigned long)&usbphy_exynos4, > + }, { > + .name = "exynos5250-usbphy", > + .driver_data = (unsigned long)&usbphy_exynos5, > + }, > + {}, > +}; > + > +MODULE_DEVICE_TABLE(platform, samsung_usbphy_driver_ids); > + > +static struct platform_driver samsung_usbphy_driver = { > + .probe = samsung_usbphy_probe, > + .remove = samsung_usbphy_remove, > + .id_table = samsung_usbphy_driver_ids, > + .driver = { > + .name = "samsung-usbphy", > + .owner = THIS_MODULE, > + .of_match_table = > of_match_ptr(samsung_usbphy_dt_match), > + }, > +}; > + > +module_platform_driver(samsung_usbphy_driver); > + > +MODULE_DESCRIPTION("Samsung USB phy controller"); USB 2.0 Phy? > +MODULE_AUTHOR("Praveen Paneri <p.paneri@xxxxxxxxxxx>"); > +MODULE_LICENSE("GPL"); > +MODULE_ALIAS("platform:samsung-usbphy"); Is this for samsung-usbphy or samsung-usb2/samsung-usb2phy? [...] I know why you create separated phy file samsung-usbphy.c and samsung-usb2.c here, but I think for that, would be better if you could consider the name and so on. Thanks. - Kukjin -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |