Re: [PATCH] MUSB HSET driver

[David Brownell <david-b@pacbell.net>]

> >A much cleaner approach is to just do this in userspace with
> >usbfs ... issuing control requests to the hub ports.  That
> >will work with *ANY* high speed controller.
> 
> I think Felipe Balbi will be looking into that aspect.
> 
> But how will that work for HSET tests with OPT card with OMAP as host.

The same way.  Those newish "key by VID/PID" test modes don't
do anything different ... they just change the user interface
for the test, so the (embedded) host requirements are even less.


> We still need to write a class driver that issues the TEST command
> to hub based on VID/PID sent by OPT. And that is what I am proposing. 
> Comments please.

Just look at the device IDs through usbfs, and use that to
decide what root hub USB_PORT_FEAT_TEST to set.  If you need
any ULPI stuff to implement those features, that should be
part of the root hub code.  (I can imagine that different
integrations of the hdrc core might have slightly different
requirements there, implying a platform hook...)

That is, you shouldn't need a kernel driver to do that stuff.

- Dave