[PATCH] UWB support for HAL
marcel at holtmann.org
Wed Aug 1 15:45:26 PDT 2007
> >> Following the Marcel's suggestion I am splitting the patch. Here is
> >> the initial patch to identify the UWB radio controller.
> >> It still unclear for me how organize/export the UWB
> >> capabilities/categories. One adapter can support WUSB, Winet/WLP(IP)
> >> and in the future other protocols. Suggestions are welcome!
> >I think the kernel has to better export the UMC interfaces and its
> >capabilities to use.
> Why? there is no need for that. Interfaces/instances that are
> children of a single device already have the parent definitions.
> UMC should be as hidden as possible.
for good HAL integration we need an easy way to identify these
capabilities. So it would make sense to have them as own objects in the
However for WUSB we probably can simply mark the host controller and
then look for a WUSB host controller inside the USB subsystem.
If we always have the winet0 interface then it would be simple, but my
understanding is that in theory we can have multiple interfaces assigned
to different beacon groups. Somehow these need to be created and
involving user space and HAL might be a good idea.
Every parent association from sysfs is represented in HAL, so that is
not a problem.
> >> For the host controller part, which properties should be exported?
> >> (bandwidth availability, beacon/scan status, events statistics,...)
> >Don't expose to much at the start. The HAL properties are
> >considered API
> >and you wanna try to keep that small in the beginning. Extending it is
> >easy. Removing or renaming is problematic.
> And bw allocation still is not clear; can't get devices that support
> it properly yet :(
> BTW, in the future we might have to do away without /sys/class/uwb_host
> [as the class support is removed]. Bear in mind!
Shouldn't be a big problem. You simply declare it as subsystem or use
links to actual sysfs devices.
More information about the hal