On Thu, 20 Jun 2013, Greg KH wrote: > > I'm not exactly sure what the implications of combining the modules are so > > I don't know if that would fix it or not. > > > > It is true that an HWA will always have an associated radio controller > > interface but the inverse is not always true. A UWB radio controller can > > be paired with any number of different protocol interfaces that run on top > > of UWB. I think HWA_RC is a bit of a misnomer for the radio control > > module. It should really be something like uwb_usb_rc since it is > > basically a USB interface to the UWB bandwidth reservation functionality. > > > > The best approach is probably to further decouple the HC and RC interfaces > > instead of tying them closer together. They are meant to be independent > > and there are only a few areas where the HC driver uses the RC handle. > > That functionality could be moved to userspace since the HWA already needs > > input from userspace to start the WUSB channel. Instead of the HWA_HC > > querying the RC directly for its channel characteristics, userspace could > > query the RC and send that info to the HC device. Doing that will > > probably break the ABI though. Is that allowed? > > It sounds like that is much more work than needed, and yes, it would > break anyone's systems that actually are using this hardware (which is > probably pretty rare...) So I wouldn't recommend doing that, sorry. Would it be okay for the HWA_RC to delay querying the RC until userspace tells it to start up the WUSB channel? If the RC interface isn't available at that time, the start-up could simply fail. Alan Stern -- 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
