From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Bin Liu <binmlist@gmail.com>,
Brian Hutchinson <b.hutchman@gmail.com>,
Matthijs van Duin <matthijsvanduin@gmail.com>
Subject: Re: [PATCH 3/4] ARM: dts: Add cppi41 support for dm816x MUSB
Date: Tue, 17 Mar 2015 18:18:37 -0700 [thread overview]
Message-ID: <20150318011836.GK31346@atomide.com> (raw)
In-Reply-To: <20150318003121.GA12911@saruman.tx.rr.com>
* Felipe Balbi <balbi@ti.com> [150317 17:32]:
> Hi,
>
> On Tue, Mar 17, 2015 at 05:19:20PM -0700, Tony Lindgren wrote:
> > Looks like we have cppi41 on dm816x just like on am335x.
> >
> > Cc: Bin Liu <binmlist@gmail.com>
> > Cc: Brian Hutchinson <b.hutchman@gmail.com>
> > Cc: Felipe Balbi <balbi@ti.com>
> > Cc: Matthijs van Duin <matthijsvanduin@gmail.com>
> > Signed-off-by: Tony Lindgren <tony@atomide.com>
>
> Any logs available ? Any throughput improvements with DMA ?
So far I only logged with the debug option on. I can do some
test runs with your for-next branch to a USB mass storage device
if you prefer that, or got some other test in mind?
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] ARM: dts: Add cppi41 support for dm816x MUSB
Date: Tue, 17 Mar 2015 18:18:37 -0700 [thread overview]
Message-ID: <20150318011836.GK31346@atomide.com> (raw)
In-Reply-To: <20150318003121.GA12911@saruman.tx.rr.com>
* Felipe Balbi <balbi@ti.com> [150317 17:32]:
> Hi,
>
> On Tue, Mar 17, 2015 at 05:19:20PM -0700, Tony Lindgren wrote:
> > Looks like we have cppi41 on dm816x just like on am335x.
> >
> > Cc: Bin Liu <binmlist@gmail.com>
> > Cc: Brian Hutchinson <b.hutchman@gmail.com>
> > Cc: Felipe Balbi <balbi@ti.com>
> > Cc: Matthijs van Duin <matthijsvanduin@gmail.com>
> > Signed-off-by: Tony Lindgren <tony@atomide.com>
>
> Any logs available ? Any throughput improvements with DMA ?
So far I only logged with the debug option on. I can do some
test runs with your for-next branch to a USB mass storage device
if you prefer that, or got some other test in mind?
Regards,
Tony
next prev parent reply other threads:[~2015-03-18 1:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 0:19 [PATCH 0/4] Few dm816x fixes and improvments Tony Lindgren
2015-03-18 0:19 ` Tony Lindgren
2015-03-18 0:19 ` [PATCH 1/4] ARM: dts: Fix gpio interrupts for dm816x Tony Lindgren
2015-03-18 0:19 ` Tony Lindgren
2015-03-18 0:19 ` [PATCH 2/4] ARM: dts: Fix typo for dm816x usb0_pins Tony Lindgren
2015-03-18 0:19 ` Tony Lindgren
2015-03-18 0:19 ` [PATCH 3/4] ARM: dts: Add cppi41 support for dm816x MUSB Tony Lindgren
2015-03-18 0:19 ` Tony Lindgren
2015-03-18 0:31 ` Felipe Balbi
2015-03-18 0:31 ` Felipe Balbi
2015-03-18 1:18 ` Tony Lindgren [this message]
2015-03-18 1:18 ` Tony Lindgren
2015-03-18 14:40 ` Felipe Balbi
2015-03-18 14:40 ` Felipe Balbi
2015-03-18 16:25 ` Tony Lindgren
2015-03-18 16:25 ` Tony Lindgren
2015-03-18 0:19 ` [PATCH 4/4] ARM: dts: Remove PIN_INPUT for dm816x McSPI Tony Lindgren
2015-03-18 0:19 ` Tony Lindgren
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=20150318011836.GK31346@atomide.com \
--to=tony@atomide.com \
--cc=b.hutchman@gmail.com \
--cc=balbi@ti.com \
--cc=binmlist@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=matthijsvanduin@gmail.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.