From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Vinod Koul <vinod.koul@intel.com>,
linux-kernel@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
linux-arm-kernel@lists.infradead.org,
Viresh Kumar <viresh.kumar@st.com>,
Alim Akhtar <alim.akhtar@gmail.com>,
Alessandro Rubini <rubini@gnudd.com>
Subject: Re: [PATCH 2/2 v2] dma/amba-pl08x: add support for the Nomadik variant
Date: Thu, 12 Apr 2012 00:05:58 +0100 [thread overview]
Message-ID: <20120411230558.GF24211@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1334185214-27250-1-git-send-email-linus.walleij@linaro.org>
On Thu, Apr 12, 2012 at 01:00:14AM +0200, Linus Walleij wrote:
> The Nomadik PL080 variant has some extra protection bits that
> may be set, so we need to check these bits to see if the
> channels are actually available for the DMAengine to use.
Actually, there is another issue to be considered with PL080. For memcpy
transfers, a restricted set of channels should be used, because the PL080
only guarantees certain channels won't consume all bus bandwidth, locking
out (eg) the CPU from doing other stuff while the memcpy DMA is running.
So really the way physical channels are selected needs to become more
inteligent overall.
WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2 v2] dma/amba-pl08x: add support for the Nomadik variant
Date: Thu, 12 Apr 2012 00:05:58 +0100 [thread overview]
Message-ID: <20120411230558.GF24211@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1334185214-27250-1-git-send-email-linus.walleij@linaro.org>
On Thu, Apr 12, 2012 at 01:00:14AM +0200, Linus Walleij wrote:
> The Nomadik PL080 variant has some extra protection bits that
> may be set, so we need to check these bits to see if the
> channels are actually available for the DMAengine to use.
Actually, there is another issue to be considered with PL080. For memcpy
transfers, a restricted set of channels should be used, because the PL080
only guarantees certain channels won't consume all bus bandwidth, locking
out (eg) the CPU from doing other stuff while the memcpy DMA is running.
So really the way physical channels are selected needs to become more
inteligent overall.
next prev parent reply other threads:[~2012-04-11 23:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 23:00 [PATCH 2/2 v2] dma/amba-pl08x: add support for the Nomadik variant Linus Walleij
2012-04-11 23:00 ` Linus Walleij
2012-04-11 23:05 ` Russell King - ARM Linux [this message]
2012-04-11 23:05 ` Russell King - ARM Linux
2012-04-12 3:42 ` Viresh Kumar
2012-04-12 3:42 ` Viresh Kumar
2012-04-12 6:56 ` Linus Walleij
2012-04-12 6:56 ` Linus Walleij
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=20120411230558.GF24211@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=alim.akhtar@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@gnudd.com \
--cc=vinod.koul@intel.com \
--cc=viresh.kumar@st.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.