From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/6] ARM/dma: pl08x: pass reasonable memcpy settings
Date: Wed, 19 Apr 2017 06:58:01 -0700 [thread overview]
Message-ID: <20170419135801.GH29219@localhost> (raw)
In-Reply-To: <20170408120457.22750-1-linus.walleij@linaro.org>
On Sat, Apr 08, 2017 at 02:04:52PM +0200, Linus Walleij wrote:
> We cannot use bits from configuration registers as API between
> platforms and driver like this, abstract it out to two enums
> and mimic the stuff passed as device tree data.
>
> This is done to make it possible for the driver to generate the
> ccfg word on-the-fly so we can support more PL08x derivatives.
>
> Cc: arm at kernel.org
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ARM SoC folks: I'd like your ACK on this eventually, it needs to
> go through the DMA engine tree with the patches following this one.
Acked-by: Olof Johansson <olof@lixom.net>
-Olof
next prev parent reply other threads:[~2017-04-19 13:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 12:04 [PATCH 1/6] ARM/dma: pl08x: pass reasonable memcpy settings Linus Walleij
2017-04-08 12:04 ` [PATCH 2/6] dma: pl08x: Add Faraday FTDMAC020 to compatible list Linus Walleij
2017-04-13 20:03 ` Rob Herring
2017-04-08 12:04 ` [PATCH 3/6] dma: pl08x: Make slave engine optional Linus Walleij
2017-04-08 12:04 ` [PATCH 4/6] dma: pl08x: Add support for Faraday Technology FTDMAC020 Linus Walleij
2017-05-14 12:34 ` Vinod Koul
2017-05-20 17:56 ` Linus Walleij
2017-05-24 4:11 ` Vinod Koul
2017-04-08 12:04 ` [PATCH 5/6] ARM: gemini: select ARM_AMBA Linus Walleij
2017-04-08 12:04 ` [PATCH 6/6] ARM: dts: Add Gemini DMA controller Linus Walleij
2017-04-19 13:58 ` Olof Johansson [this message]
2017-04-19 19:43 ` [PATCH 1/6] ARM/dma: pl08x: pass reasonable memcpy settings Arnd Bergmann
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=20170419135801.GH29219@localhost \
--to=olof@lixom.net \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).