Hi, On Wed, Nov 07, 2012 at 07:23:49PM +0100, Sebastian Andrzej Siewior wrote: > The setup request can be sent to an interface/endpoint or to the device > itself. If it is sent to an interface then we forward it to the function > that is mapped to that interface. The same is true if an endpoint is the > target of the setup request. > If the device is the target of a setup request then we forward it to the > ->setup() callback of the currently active configuration. > In case of the sourcesink function the requests are function specific > but are sent to the device. > This patch introduces a setup wraper at configuration level which > forwards the requests to the function. This allows to keep the function > specific code within the function and we need just a hint at config > level to forward the request. > The here introduces global variable will be moved into the gadget (which > combines the two functions) in a later patch. > The alternative would to attempt to deliver the request to each function > as long as they return ENOTSUPP. SourceSink is currently the only gadget > using ->setup() at config level. you need some rework on this commit log. Looks like there are a few missing words here and there ;-) -- balbi
Attachment:
signature.asc
Description: Digital signature
