From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: <b-liu@ti.com>, <gregkh@linuxfoundation.org>,
<linux-usb@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<balbi@kernel.org>, <linux-kernel@vger.kernel.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>
Subject: Re: [PATCH 4/4] usb: musb: tusb6010_omap: Convert to DMAengine API
Date: Mon, 8 May 2017 18:12:56 +0300 [thread overview]
Message-ID: <10da9ac1-325c-792e-3fa1-ab44405ab1c9@ti.com> (raw)
In-Reply-To: <20170505225523.GD3489@atomide.com>
Tony,
On 2017-05-06 01:55, Tony Lindgren wrote:
> OK I verified that with the current mainline kernel using dma
> and g_ether and your patches 1 to 3 I can run the variable size
> ping test loop for few minutes before it just stops working and
> I can see the legacy DMA interrupt increase depending on the
> size of the packet. Then I checked with v4.1 kernel, and that
> too seems to have the same issue.
>
> I've also verified running the same variable size ping test with
> your patch 4/4 makes things stop within just a few seconds. The
> script I'm using for ping is below.
>
> Anyways, what we really should ensure here is that the external
> dmarequest line is properly triggering things with dmaengine :)
> That's why I'm a bit worried your patch 4/4.
>
> Oh and I also verified the GPMC timings we're using are the same
> as in production n810 kernel so that should not be the issue.
>
> And using the async access on n800 will not work as it will
> produce corrupt transfer size register the report I posted
> earlier is from n800 allowing it to use async transfers. On
> n810 async transfers may work as I recall it having a newer
> tusb6010 version.
I think I have nailed the issue. I had a bug in the omap-dma
implementation of the port_window (sigh) and couple of issues in the
tusb6010/*_omap, not introduced by the series.
The ASYNC access is pretty unstable on n810 as well, I got corruption in
the XFR_SIZE.
I have been using the g_ncm gadget with
"musb->g.quirk_avoids_skb_reserve = 1;" to ensure that we are using SYNC
access.
I'm running your variable ping script for 2 hours now, it wrapped >130
times already, I also run a standalone ping with 2048 size in parallel,
the n810 is booted to nfsroot:
# cat /proc/interrupts | grep dma
29: 9483598 INTC 13 Edge omap-dma-engine
#
I need to clean up the code as I had debugs (disabled now) and stuff and
I want to try the tusb6010 changes w/o the DMAengine conversion.
>
> Regards,
>
> Tony
>
> 8< ----------------
> #!/bin/bash
>
> device=$1
> size=$2
+ wraps = 0
>
> while [ 1 ]; do
> #echo "Pinging with size $size"
> if ! ping -w0 -c1 -s$size $device > /dev/null 2>&1; then
> break;
> fi
> size=$(expr $size + 1)
>
> if [ $size -gt 8192 ]; then
+ wraps=$(expr $wraps + 1)
+ echo "wrapping ($wraps) at $size"
> size=1
> fi
> done
> echo "Test ran up to $size"
>
- Péter
next prev parent reply other threads:[~2017-05-08 15:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 10:56 [PATCH 0/4] usb: musb: tusb6010_omap: Convert to DMAengine Peter Ujfalusi
2017-05-03 10:56 ` [PATCH 1/4] usb: musb: tusb6010_omap: Create new struct for DMA data/parameters Peter Ujfalusi
2017-05-03 10:56 ` [PATCH 2/4] usb: musb: tusb6010_omap: Allocate DMA channels upfront Peter Ujfalusi
2017-05-03 10:56 ` [PATCH 3/4] ARM: OMAP2+: DMA: Add slave map entries for 24xx external request lines Peter Ujfalusi
2017-05-03 10:56 ` [PATCH 4/4] usb: musb: tusb6010_omap: Convert to DMAengine API Peter Ujfalusi
2017-05-04 19:40 ` Tony Lindgren
2017-05-04 21:05 ` Tony Lindgren
2017-05-05 13:37 ` Peter Ujfalusi
2017-05-05 15:17 ` Peter Ujfalusi
2017-05-05 22:55 ` Tony Lindgren
2017-05-08 15:12 ` Peter Ujfalusi [this message]
2017-05-08 15:29 ` Tony Lindgren
2017-05-04 14:31 ` [PATCH 0/4] usb: musb: tusb6010_omap: Convert to DMAengine Tony Lindgren
2017-05-05 7:28 ` Peter Ujfalusi
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=10da9ac1-325c-792e-3fa1-ab44405ab1c9@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=b-liu@ti.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®