On 11/21/2011 10:56 PM, Hauke Mehrtens wrote: > Hi, > > To provide ehci and ohci at the same time I came up with some solutions: > > 1. The OHCI driver also initializes the EHCI driver, when it gets load > and is an USB 2.0 device. This is how it is done in OpenWrt and I do not > like it [1]. > 2. bcma provides two devices with different identification and there are > two independ drivers working with it. When doing this the wrapper access (bcma_aread/awrite) will have effect on both not-so-independent drivers. > 3. bcma handles the usb registration directly and all code goes to > drivers/bcma/ Sound like mixing device driver functionality in a bus driver. It does not feel right to me, but bcma is already handling chipcommon, and pci(e) cores. Main question would be whether a linux device driver can provide multiple system functions. I tend to say it can. So I would suggest to have a single device driver providing OHCI and EHCI functionality. > 4. Is there some way like a platform device with a memory address which > I could register and which is then handled by the usb system? > > Are there any better approaches on how to do this? I do not think I am > the first person with such a problem. > > Hauke > Gr. AvS ps.: I polled again internally about et driver support. Keep you posted. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
