Hello, > > I am developing a driver, which I would like to implement using > > FunctionFS, for using the Android Open Accessory protocol on > > non-Android devices. These accessories send some non-standard control > > requests which are described here: > > https://source.android.com/devices/accessories/aoa.html > > oh cool. I was thinking about Android Accessory a couple weeks ago. I'm > not sure yet if functionfs is the best way to go here. Maybe we should > actually have a proper function (f_android_accessory.c??) so it's easier > to handle this. > > Also, maybe we should add some Android folks to the loop here. Adding > android's accessory function author here. > > Mike, I'm looking at [1]. Do you have any interest in getting that > upstream? Also, taking the opportunity to raise another question: I > noticed android's MTP is pretty darn slow, I'm assuming the limitation > is functionfs itself. Do you wanna see how we can make that faster? This is actually not for a f_accessory replacement. The control requests are sent when the device is in any other gadget mode, for sending metadata and to trigger switching to Open Accessory Gadget Mode. The Accessory mode itself can be handled very easily with f_serial (or a very simple FunctionFS driver). So I wonder why f_accessory exists. Regards Felix -- 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
