On Friday, October 19, 2012 5:27 PM Felipe Balbi wrote: <snip> > > I think what we want here is a possibility to configure multiple > > functions in one gadget (under one udc, in other words). > > eventually, but not until we do the ground work/housekeeping to get there. > We definitely don't want to hack something together which nobody will in > the future. > > > So the "something" I mentioned earlier should be the place where the > > usb_composite_driver is defined and probed. And I called this kind of > > entity a "gadget". Any better name? > > > > Does this sound reasonable to you? Or do you think about something > > completely different? > > Sorry but you seem to be way off :-s. I continue to say that we don't want > any "temporary" solutions, we want to take all steps necessary towards our > goal of deleting all g_* files and keeping only the functions in kernel. > This means that will not accept a gadget driver which is built based on > configfs, while that does the whole "configfs-based binding" it does it in > the wrong way and I will not let that go into the kernel. <snip> That's OK. Perhaps I should have been more explicit about this: by RFC I mean something not intended for merging yet but rather a proof of concept or the like. However, I am confused taken this: http://marc.info/?l=linux-usb&m=132431126927355&w=2 into account. I thought we are somewhere around "make composite one file again and forget the #include" so working on "start implementing the gadget configfs interface" makes sense to me. Given the above, the following questions arise: 0) What is the right way of doing "configfs-based binding"? 1) What kind of ground work/housekeeping are required before configfs works can be considered? Can configfs works be done in parallel? 2) If only f_* files remain, where will they be used? Now they are used by their gadget counterparts, e.g. f_sourcesink and f_loopback are used by zero.c. In other words, if f_* files deal with the usb functions level and only they remain, then what takes care of usb configurations and usb devices? Thanks, AP -- 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
