Re: gs_start_io() and gs_close()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 On 08/26/10 04:21, Jim Sung wrote:
> I'm debugging a problem with the USB gadget serial on the Marvell PXA168

CC'ed LAKML

> platform, which led to the following observations:
>
> - The way gs_start_io() is implemented, each time it is invoked,
>   port->read_pool and port->write_pool will grow by QUEUE_SIZE, which
>   seems wrong.
>
>   For now, I just added a list_empty() check in gs_start_io() on the two
>   lists.
>
> - "struct gs_port" does not appear to have provision to notify the USB
>   device controller to release any resource (particularly for rx) in
>   gs_close().
>
>   To fix the problem, I have a hard coded call into the USB device
>   controller right now, but that is ugly.
>
> The particular kernel I'm working with is 2.6.28, but I took a look at
> 2.6.35-rc6, and I don't see any change in these areas.
>
> Jim
>
>
> --
> 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
>

-- 
Regards,
Igor.

--
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


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux