On Tue, Jun 30, 2015 at 8:23 AM, Jayan John wrote:
> On Tue, Jun 30, 2015 at 6:50 AM, Peter Chen wrote:
>>
>>> On Tue, Jun 30, 2015 at 12:33 AM, Steve Calfee
>>> wrote:
>>> > On Mon, Jun 29, 2015 at 7:16 AM, Alan Stern
>>> wrote:
>>> >> On Mon, 29 Jun 2015, Peter Chen wrote:
>>> >>
>>> >>> Just
On Tue, Jun 30, 2015 at 6:50 AM, Peter Chen wrote:
>
>> On Tue, Jun 30, 2015 at 12:33 AM, Steve Calfee
>> wrote:
>> > On Mon, Jun 29, 2015 at 7:16 AM, Alan Stern
>> wrote:
>> >> On Mon, 29 Jun 2015, Peter Chen wrote:
>> >>
>> >>> Just like Steve pointed, it should be a ZLT problem, do you have
>
> On Tue, Jun 30, 2015 at 12:33 AM, Steve Calfee
> wrote:
> > On Mon, Jun 29, 2015 at 7:16 AM, Alan Stern
> wrote:
> >> On Mon, 29 Jun 2015, Peter Chen wrote:
> >>
> >>> Just like Steve pointed, it should be a ZLT problem, do you have
> >>> below patch in your tree, and the host may not send zl
>
> On Mon, Jun 29, 2015 at 7:16 AM, Alan Stern
> wrote:
> > On Mon, 29 Jun 2015, Peter Chen wrote:
> >
> >> Just like Steve pointed, it should be a ZLT problem, do you have
> >> below patch in your tree, and the host may not send zlt, but you may
> >> queue an zero-length request, the f_hid do
On Tue, Jun 30, 2015 at 12:33 AM, Steve Calfee wrote:
> On Mon, Jun 29, 2015 at 7:16 AM, Alan Stern wrote:
>> On Mon, 29 Jun 2015, Peter Chen wrote:
>>
>>> Just like Steve pointed, it should be a ZLT problem, do you have
>>> below patch in your tree, and the host may not send zlt, but you
>>> may
On Sun, Jun 28, 2015 at 12:41 AM, Jayan John wrote:
> If this is a bug in the chipidea UDC driver or hardware, how can I
> address this i.e. register an errata? I am hoping this is something
> Peter might be able to help with.
What is the kernel version you are using? Could you test it with kern
On Mon, Jun 29, 2015 at 7:16 AM, Alan Stern wrote:
> On Mon, 29 Jun 2015, Peter Chen wrote:
>
>> Just like Steve pointed, it should be a ZLT problem, do you have
>> below patch in your tree, and the host may not send zlt, but you
>> may queue an zero-length request, the f_hid does not set req->zer
On Mon, 29 Jun 2015, Peter Chen wrote:
> Just like Steve pointed, it should be a ZLT problem, do you have
> below patch in your tree, and the host may not send zlt, but you
> may queue an zero-length request, the f_hid does not set req->zero
> flag either.
>
> commit 953c66469735aed8d2ada639a72b1
On Sun, Jun 28, 2015 at 09:11:30AM +0530, Jayan John wrote:
> On Sun, Jun 28, 2015 at 5:34 AM, Alan Stern wrote:
> > On Sat, 27 Jun 2015, Jayan John wrote:
> >
> >> Thanks.
> >>
> >> Yes, the wLength value in the Setup packet is equal to 64. "Aligned"
> >> was the wrong term, multiple of 64 would
On Sun, Jun 28, 2015 at 5:34 AM, Alan Stern wrote:
> On Sat, 27 Jun 2015, Jayan John wrote:
>
>> Thanks.
>>
>> Yes, the wLength value in the Setup packet is equal to 64. "Aligned"
>> was the wrong term, multiple of 64 would be more appropriate :).
>>
>> The hid gadget driver queues a request for t
On Sat, 27 Jun 2015, Jayan John wrote:
> Thanks.
>
> Yes, the wLength value in the Setup packet is equal to 64. "Aligned"
> was the wrong term, multiple of 64 would be more appropriate :).
>
> The hid gadget driver queues a request for the transfer. Please see below
> logs..
> ...
> HID: driver
On Sat, Jun 27, 2015 at 2:21 AM, Alan Stern wrote:
> On Sat, 27 Jun 2015, Jayan John wrote:
>
>> On Fri, Jun 26, 2015 at 8:44 PM, David Laight
>> wrote:
>> > From: Steve Calfee
>> >> Sent: 26 June 2015 15:59
>> >> > On the host (Wandboard iMX6q) the test app opens /dev/hidraw0 and
>> >> > write
On Sat, 27 Jun 2015, Jayan John wrote:
> On Fri, Jun 26, 2015 at 8:44 PM, David Laight wrote:
> > From: Steve Calfee
> >> Sent: 26 June 2015 15:59
> >> > On the host (Wandboard iMX6q) the test app opens /dev/hidraw0 and
> >> > write 64 bytes with report ID (1). The HID device has no Interrupt OUT
On Fri, Jun 26, 2015 at 8:44 PM, David Laight wrote:
> From: Steve Calfee
>> Sent: 26 June 2015 15:59
>> > On the host (Wandboard iMX6q) the test app opens /dev/hidraw0 and
>> > write 64 bytes with report ID (1). The HID device has no Interrupt OUT
>> > ep, therefore uses control endpoint ep0 for
From: Steve Calfee
> Sent: 26 June 2015 15:59
> > On the host (Wandboard iMX6q) the test app opens /dev/hidraw0 and
> > write 64 bytes with report ID (1). The HID device has no Interrupt OUT
> > ep, therefore uses control endpoint ep0 for the 64 bytes transfer to
> > gadget (Wandboard iMX6q) using
On Fri, Jun 26, 2015 at 5:01 AM, Jayan John wrote:
> Thanks Alex. I appreciate you introducing me to Peter. Any help is
> appreciated.
>
> On the host (Wandboard iMX6q) the test app opens /dev/hidraw0 and
> write 64 bytes with report ID (1). The HID device has no Interrupt OUT
> ep, therefore use
Thanks Alex. I appreciate you introducing me to Peter. Any help is appreciated.
On the host (Wandboard iMX6q) the test app opens /dev/hidraw0 and
write 64 bytes with report ID (1). The HID device has no Interrupt OUT
ep, therefore uses control endpoint ep0 for the 64 bytes transfer to
gadget (Wand
Jayan John writes:
> I am developing a custom USB device on a iMX6q platform (Wandboard)
> Chipidea HDRC (highspeed dual role controller). The HID interface
> consists of a single Interrupt IN ep and ep0. It is required to send
> HID reports from Host to Gadget over ep0 (with set_report cmd on
>
I am developing a custom USB device on a iMX6q platform (Wandboard)
Chipidea HDRC (highspeed dual role controller). The HID interface
consists of a single Interrupt IN ep and ep0. It is required to send
HID reports from Host to Gadget over ep0 (with set_report cmd on
hidraw interface) in OUT direct
cc Alexander
Thanks
On Thu, Jun 25, 2015 at 7:41 PM, Jayan John wrote:
> I am developing a custom USB device on a iMX6q platform (Wandboard)
> Chipidea HDRC (highspeed dual role controller). The HID interface
> consists of a single Interrupt IN ep and ep0. It is required to send
> HID reports fr
20 matches
Mail list logo
