Basically, that almost all of the OTG state machine must be
handled outside of this code. It's a bit of a puzzle how to
partition that state machine between the drivers that need
to collaborate on it. At this point I don't think there can
be a single model that applies everywhere ... but
We'll need something like this, yes.
This one looks to need a bit of tweaking yet though ...
probably that could be done after merge.
The state can need changing after one of the drivers is unregistered;
I didn't get this comment.
using __exit not __devexit is likely wrong (especially
On Thursday 29 January 2009, Gupta, Ajay Kumar wrote:
We'll need something like this, yes.
This one looks to need a bit of tweaking yet though ...
probably that could be done after merge.
The state can need changing after one of the drivers is unregistered;
I didn't get this
On Thursday 08 January 2009, Ajay Kumar Gupta wrote:
OP transceiver is used by all the usb transceiver which are mostly
autonomous and doesn't require any programming or which are built
into the usb ip itself.NOP transceiver only allocates the memory
for struct xceiv and calls
Hi,
On Thu, Jan 08, 2009 at 04:23:08PM +0530, Ajay Kumar Gupta wrote:
NOP transceiver is used by all the usb transceiver which are mostly
autonomous and doesn't require any programming or which are built
into the usb ip itself.NOP transceiver only allocates the memory
for struct xceiv and
