> > On 8/5/2011 6:12 PM, Sascha Hauer wrote: > > Yes, that's clear to me. I just wondered what exact names we should use > > to register a phy. > > > > Consider a phy registering itself with > > > > usb_register_transceiver(recv) with recv->name = "mxc-ehci.0" > > > > (where recv->name could be passed from platform_data) > > > > Then the mxc-ehci driver could get its receiver using > > > > usb_get_transceiver(dev_name(&pdev->dev)) > > > > or with > > > > usb_get_transceiver(&pdev->dev); > > > > when we do what I suggested. This would be similar to the clocks which > > get the clocks associated to a device with clk_get(&pdev->dev, id). > > > > This would change the behaviour of usb_get_transceiver() from "give me > > the phy with this name" to "give me the transceiver associated with > this > > device". It would prevent us from inventing arbitrary phy names. > > > I like this idea. > > How does this work if both gadget and host are active. What name should > be passed to transceiver? "mxc-ehci" or "mxc-udc" > I think both of them should be passed to transceiver, as both gadget and host use this transceiver. > Thanks, > Pavan > > -- > Sent by a consultant of the Qualcomm Innovation Center, Inc. > The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. > -- > To unsubscribe from this list: send the line "unsubscribe linux-usb" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
