# \[PATCH, RFC 16/22\] USB: UHCI: clarify Kconfig dependencies

- From: Arnd Bergmann \<arnd@arndb.de\>
- Date: 2013-05-02 19:13:10 
- List: linux-arm-kernel
- Page: https://ratatoskr.run/linux-arm-kernel/2013/05/4043102
- Thread: https://ratatoskr.run/linux-arm-kernel/2013/05/4042941/t.md

```text
On Thursday 02 May 2013, Alan Stern wrote:
> On Thu, 2 May 2013, Arnd Bergmann wrote:
> 
> > > What do you think of my patch as compared to yours? 
> > 
> > I think in the end it comes down to the question where you want to
> > head with your driver. The way I did my version was going towards
> > making it similar to EHCI, with stand-alone bus glue drivers
> > and a core that is just a library module but does not register
> > a device_driver by itself.
> > 
> > Given that there are just three bus glues from UHCI, and at most
> > two of them enabled at the same time, I don't see a direct need
> > for UHCI to go down the same route as EHCI. If you want to just
> > leave this driver alone, your patch is simpler and has the same
> > effect in the end. Otherwise I think my patch avoids changing it
> > all again once the driver gets reworked.
> 
> Okay then, I'll submit my patch to Greg after the merge window closes.

Ok, thanks!

	Arnd
```
