Hi,

On Thu, Jul 26, 2012 at 8:57 PM, Arnd Bergmann [off-list ref] wrote:

On Saturday 21 July 2012, Vivek Gautam wrote:

quoted

@@ -28,6 +29,11 @@ static struct exynos4_ohci_platdata

smdk5250_ohci_pdata = {

quoted

        .phy_exit = s5p_usb_phy_exit,
 };

+static struct s5p_ehci_platdata smdk5250_ehci_pdata = {
+       .phy_init = s5p_usb_phy_init,
+       .phy_exit = s5p_usb_phy_exit,
+};
+
 /*
  * The following lookup table is used to override device names when

devices

quoted

  * are registered from device tree. This is temporarily added to enable

I'm a bit confused of the purpose of setting the function pointers here
when the pointers are always to the same s5p_usb_phy_init/s5p_usb_phy_exit
identifiers, but you have different definitions of those functions
depending on which platforms you are building for.

What is the idea here? Are you going to unify the three definitions of
s5p_usb_phy_init, or is that function going away eventually when we
get to the point of building exynos/s5p/s3c64xx into the same kernel
binary?

Should we be differentiating here between the calls at runtime for

different SOCs.
In that case, yes i think we need a way here to have a solution here so
that the function call
goes differently for different soc while in runtime. I will work on this
and get back asap.

        Arnd

_______________________________________________
devicetree-discuss mailing list
devicetree-discuss at lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss

Best regards
Vivek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120728/f79ef87a/attachment.html>