[lkml]   [2012]   [Aug]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC 0/2] USB gadget - configfs
On Thu, Aug 16, 2012 at 03:47:15PM +0200, Sebastian Andrzej Siewior wrote:
> On 08/16/2012 03:17 PM, Andrzej Pietrasiewicz wrote:
> >A lun is "opened" on storing the "file" attribute of the lun, it is in
> >fsg_lun_store_file, storage_common.c. So, again, this is a configfs
> >callback.
> >
> >On storing the connect attribute, the following happens: a composite driver
> >is probed, then all the configurations are iterated over, their functions
> >being bound in turn. After the gadget is set up this way, the host notices
> >connecting a new mass storage device.
> The configuration has to remain unchanged until the "connect" attribute
> is changed (i.e. unconnected). That means the gadget can only be
> reconfigured once it is not active.

Yes, that's my understanding of the driver code. What I'm
trying to understand is the trigger for setting connect=1. See, all of
the other configfs steps you outlined make sense to me as "part of the
gadget's internal state". While I don't know what C1 and F1 are (I
assume G1 is Gadget1), I don't know that it matters.
What changes the state to "active"? That is, what triggers
setting connect=1? Is it just part of the flow of power-up, or is there
some separation between "setting myself up" and "seeing that a host
wants to talk to me"?



"The trouble with being punctual is that nobody's there to
appreciate it."
- Franklin P. Jones

 \ /
  Last update: 2012-08-17 04:21    [W:0.082 / U:1.968 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site