On Thu, 9 Oct 2014, Robert Baldyga wrote:
> In fact this patch solves in some way the problem 'who should handle
> requests addressed to device?'.
In theory, such requests should be handled by the top-level gadget
driver (i.e., composite.c or equivalent). By definition, function
drivers handle
On 10/09/2014 01:59 PM, Andrzej Pietrasiewicz wrote:
> W dniu 08.10.2014 o 15:06, Felipe Balbi pisze:
>> Hi,
>>
>> On Wed, Oct 08, 2014 at 01:32:31PM +0200, Andrzej Pietrasiewicz wrote:
>>> Some not-so-well-behaving USB hosts with a popular proprietary operating
>>> system sometimes issue per-devic
W dniu 08.10.2014 o 15:06, Felipe Balbi pisze:
Hi,
On Wed, Oct 08, 2014 at 01:32:31PM +0200, Andrzej Pietrasiewicz wrote:
Some not-so-well-behaving USB hosts with a popular proprietary operating
system sometimes issue per-device requests even though they mean requests
for a particular function,
Hi,
On Wed, Oct 08, 2014 at 01:32:31PM +0200, Andrzej Pietrasiewicz wrote:
> Some not-so-well-behaving USB hosts with a popular proprietary operating
> system sometimes issue per-device requests even though they mean requests
> for a particular function, e.g. for ptp (picture transfer protocol).
Some not-so-well-behaving USB hosts with a popular proprietary operating
system sometimes issue per-device requests even though they mean requests
for a particular function, e.g. for ptp (picture transfer protocol).
This patch adds optional "for_device" function in usb_configuration so that
it can
