All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: Russell King - ARM Linux <linux@armlinux.org.uk>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	vkoul@kernel.org, dan.j.williams@intel.com,
	dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-omap@vger.kernel.org
Subject: dmaengine: ti: omap-dma: Configure LCH_TYPE for OMAP1
Date: Sun, 25 Nov 2018 09:14:28 -0800	[thread overview]
Message-ID: <20181125171428.GL53235@atomide.com> (raw)

* Aaro Koskinen <aaro.koskinen@iki.fi> [181125 16:58]:
> Below changes get traffic going with DMA & g_ether...

Oh cool, if you have dma and g_ether working, you should
test it with a variable size ping test loop :) That should
expose any issues within few minutes.

Below is the test script I was using earlier, the
tusb6010 comment there is probably no longer valid.

Regards,

Tony

8< ----------------
#!/bin/bash

#
# At least tusb6010 dma needs 32-bit aligned buffers.
# That can be done by setting no_skb_reserve with:
# musb->g.quirk_avoids_skb_reserve = 1;
#

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"

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: Russell King - ARM Linux <linux@armlinux.org.uk>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	vkoul@kernel.org, dan.j.williams@intel.com,
	dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-omap@vger.kernel.org
Subject: Re: [PATCH] dmaengine: ti: omap-dma: Configure LCH_TYPE for OMAP1
Date: Sun, 25 Nov 2018 09:14:28 -0800	[thread overview]
Message-ID: <20181125171428.GL53235@atomide.com> (raw)
In-Reply-To: <20181125165830.GC3416@darkstar.musicnaut.iki.fi>

* Aaro Koskinen <aaro.koskinen@iki.fi> [181125 16:58]:
> Below changes get traffic going with DMA & g_ether...

Oh cool, if you have dma and g_ether working, you should
test it with a variable size ping test loop :) That should
expose any issues within few minutes.

Below is the test script I was using earlier, the
tusb6010 comment there is probably no longer valid.

Regards,

Tony

8< ----------------
#!/bin/bash

#
# At least tusb6010 dma needs 32-bit aligned buffers.
# That can be done by setting no_skb_reserve with:
# musb->g.quirk_avoids_skb_reserve = 1;
#

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"

             reply	other threads:[~2018-11-25 17:14 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-25 17:14 Tony Lindgren [this message]
2018-11-25 17:14 ` [PATCH] dmaengine: ti: omap-dma: Configure LCH_TYPE for OMAP1 Tony Lindgren
  -- strict thread matches above, loose matches on Subject: below --
2018-12-18 15:55 Tony Lindgren
2018-12-18 15:55 ` [PATCH] " Tony Lindgren
2018-12-18 10:11 Peter Ujfalusi
2018-12-18 10:11 ` [PATCH] " Peter Ujfalusi
2018-12-18 10:11 ` Peter Ujfalusi
2018-12-17 23:47 Aaro Koskinen
2018-12-17 23:47 ` [PATCH] " Aaro Koskinen
2018-12-17 19:16 Aaro Koskinen
2018-12-17 19:16 ` [PATCH] " Aaro Koskinen
2018-12-17 19:16 ` Aaro Koskinen
2018-11-25 16:58 Aaro Koskinen
2018-11-25 16:58 ` [PATCH] " Aaro Koskinen
2018-11-25 11:57 Russell King - ARM Linux
2018-11-25 11:57 ` [PATCH] " Russell King - ARM Linux
2018-11-25 11:11 Russell King - ARM Linux
2018-11-25 11:11 ` [PATCH] " Russell King - ARM Linux
2018-11-25  1:11 Tony Lindgren
2018-11-25  1:11 ` [PATCH] " Tony Lindgren
2018-11-25  1:07 Tony Lindgren
2018-11-25  1:07 ` [PATCH] " Tony Lindgren
2018-11-24 20:09 Russell King - ARM Linux
2018-11-24 20:09 ` [PATCH] " Russell King - ARM Linux
2018-11-24 19:29 Russell King - ARM Linux
2018-11-24 19:29 ` [PATCH] " Russell King - ARM Linux
2018-11-24 19:06 Aaro Koskinen
2018-11-24 19:06 ` [PATCH] " Aaro Koskinen
2018-11-24 17:48 Russell King - ARM Linux
2018-11-24 17:48 ` [PATCH] " Russell King - ARM Linux
2018-11-24  0:17 Aaro Koskinen
2018-11-24  0:17 ` [PATCH] " Aaro Koskinen
2018-11-23 23:27 Russell King - ARM Linux
2018-11-23 23:27 ` [PATCH] " Russell King - ARM Linux
2018-11-23 18:52 Aaro Koskinen
2018-11-23 18:52 ` [PATCH] " Aaro Koskinen
2018-11-23 16:16 Russell King - ARM Linux
2018-11-23 16:16 ` [PATCH] " Russell King - ARM Linux
2018-11-23 15:43 Russell King - ARM Linux
2018-11-23 15:43 ` [PATCH] " Russell King - ARM Linux
2018-11-23 12:35 Peter Ujfalusi
2018-11-23 12:35 ` [PATCH] " Peter Ujfalusi
2018-11-23 12:35 ` Peter Ujfalusi
2018-11-23 11:54 Peter Ujfalusi
2018-11-23 11:54 ` [PATCH] " Peter Ujfalusi
2018-11-23 11:54 ` Peter Ujfalusi
2018-11-23 11:49 Peter Ujfalusi
2018-11-23 11:49 ` [PATCH] " Peter Ujfalusi
2018-11-23 11:49 ` Peter Ujfalusi
2018-11-23 11:45 Peter Ujfalusi
2018-11-23 11:45 ` [PATCH] " Peter Ujfalusi
2018-11-23 11:45 ` Peter Ujfalusi
2018-11-23  1:23 Aaro Koskinen
2018-11-23  1:23 ` [PATCH] " Aaro Koskinen
2018-11-23  0:25 Russell King - ARM Linux
2018-11-23  0:25 ` [PATCH] " Russell King - ARM Linux
2018-11-22 22:24 Aaro Koskinen
2018-11-22 22:24 ` [PATCH] " Aaro Koskinen
2018-11-22 22:01 Aaro Koskinen
2018-11-22 22:01 ` [PATCH] " Aaro Koskinen
2018-11-22 15:12 Russell King - ARM Linux
2018-11-22 15:12 ` [PATCH] " Russell King - ARM Linux
2018-11-22 10:29 Russell King - ARM Linux
2018-11-22 10:29 ` [PATCH] " Russell King - ARM Linux
2018-11-22  8:31 Peter Ujfalusi
2018-11-22  8:31 ` [PATCH] " Peter Ujfalusi
2018-11-22  8:31 ` Peter Ujfalusi
2018-11-20 21:04 Aaro Koskinen
2018-11-20 21:04 ` [PATCH] " Aaro Koskinen
2018-11-20  7:28 Peter Ujfalusi
2018-11-20  7:28 ` [PATCH] " Peter Ujfalusi
2018-11-20  7:28 ` Peter Ujfalusi
2018-11-19 18:46 Aaro Koskinen
2018-11-19 18:46 ` [PATCH] " Aaro Koskinen
2018-11-19 10:40 Peter Ujfalusi
2018-11-19 10:40 ` [PATCH] " Peter Ujfalusi
2018-11-19 10:40 ` 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=20181125171428.GL53235@atomide.com \
    --to=tony@atomide.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=peter.ujfalusi@ti.com \
    --cc=vkoul@kernel.org \
    /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.