On Tue, Jul 31, 2012 at 09:06:33AM +0800, Chen Peter-B29397 wrote: > > > > > > > <&usbmisc 0> would then mean port 0 of the usbmisc device. > > I didn't add the restriction that a usbmisc driver must have a usbmisc > > device. I'm not sure whether all SoC and future SoC can be look as > > a device. > > > > Peter, do you have any idea? > > > I have not followed this usbmisc design, I just list some facts at i.mx > USB controller: > > Sigmatel-derived SoCs (i.mx23, i.mx28) have no this register region, all phy controls > are through PHY register. > Other freescale SoCs have this usbmisc register region to control phy and tune some > signal quality. This register region is from another 0x800 or (last controller base address + 0x200) Looks good. I'll take Sascha's suggestion. Thanks Richard > > > Thanks > > Richard > > > > > > If the usbmisc property exists, you can return -EPROBE_DEFER until it > > is > > > available. If it doesn't exist, you just continue without usbmisc > > > support (i.MX28) > > > > > > Sascha > > > > > > > > > -- > > > Pengutronix e.K. | > > | > > > Industrial Linux Solutions | http://www.pengutronix.de/ > > | > > > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 > > | > > > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- > > 5555 | > > > -- 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
