All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
To: Andrzej Pietrasiewicz <andrzejtp2010@gmail.com>,
	Minas Harutyunyan <minas.harutyunyan@synopsys.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Felipe Balbi <felipe.balbi@linux.intel.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: [v3] usb: dwc2: gadget: Add scatter-gather mode
Date: Tue, 12 Mar 2019 13:23:47 +0000	[thread overview]
Message-ID: <410670D7E743164D87FA6160E7907A56013A7E9B6F@am04wembxa.internal.synopsys.com> (raw)

Hi Andrzej,

On 3/12/2019 3:39 PM, Andrzej Pietrasiewicz wrote:
> Hi Minas,
> 
> 
> W dniu 12.03.2019 o 08:54, Minas Harutyunyan pisze:
>> Hi,
>>
>> SB CV MSC tests failed starting from Test Case 6 with BNA interrupt on
>> ep1in. It's first BULK IN transaction after GET MAXLUN.
>>
> Can you help me reproduce the problem? I have an Odroid U3.
1. Download from usb.org USB CV tool. Install on MS Windows.
2. Setup your Odroid U3 as mass storage and connect to MS Windows.
3. Run USB CV. Choose MSC tests to run.

I used "USB 3 Gen X Command Verifier".
> 
>>
>> Meantime it's passing smoke test with mass storage function connected to
>> Linux host.
> 
> So the "real" use case with mass storage works, right?
> 
Yes, it's works. Actually, USB CV use another OS and host driver which 
can be reason of fail, but mass storage should pass all CV MSC tests 
besides smoke tests with Linux.

> Andrzej
> 

Thanks,
Minas

             reply	other threads:[~2019-03-12 13:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 13:23 Minas Harutyunyan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-03-18 10:32 [v3] usb: dwc2: gadget: Add scatter-gather mode Minas Harutyunyan
2019-03-15 11:31 Andrzej Pietrasiewicz
2019-03-15 11:27 Andrzej Pietrasiewicz
2019-03-12 11:39 Andrzej Pietrasiewicz
2019-03-12  7:54 Minas Harutyunyan
2019-01-21 13:44 Marek Szyprowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=410670D7E743164D87FA6160E7907A56013A7E9B6F@am04wembxa.internal.synopsys.com \
    --to=minas.harutyunyan@synopsys.com \
    --cc=andrzejtp2010@gmail.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=felipe.balbi@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.