On 05/14/2014 06:33 PM, Andrew Bresticker wrote: > Board-specific USB configuration data is stored in FUSE_SKU_CALIB_0. > Export a function to read it so the PHY can be properly configured. This patch seems conceptually fine to me. Presumably once Peter's fuse driver is fleshed out, it can expose the exact same semantic interface to drivers. I suppose one could argue that we should create/use an explicit fuse subsystem with a standard API that drivers can call into, rather than a custom API. We can get the appropriate handle to use for that API from a phandle (plus fuse IDs?) in a DT property (in the XHCI device node, pointing at the fuse device node) much like any other cross-device resource reference. I'm not too bothered whether the code actually does that in the first instance, although we should make sure we add that DT property (containing all required fuse ID information) so that the code /can/ work that way if we want it to in the future. -- 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
