From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5 v2] ARM/dma: pl08x: pass reasonable memcpy settings
Date: Wed, 24 May 2017 09:45:06 +0530 [thread overview]
Message-ID: <20170524041506.GW15061@localhost> (raw)
In-Reply-To: <20170520214254.21541-1-linus.walleij@linaro.org>
On Sat, May 20, 2017 at 11:42:50PM +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.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2017-05-24 4:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 21:42 [PATCH 1/5 v2] ARM/dma: pl08x: pass reasonable memcpy settings Linus Walleij
2017-05-20 21:42 ` [PATCH 2/5 v2] dma: pl08x: Add Faraday FTDMAC020 to compatible list Linus Walleij
2017-05-20 21:42 ` [PATCH 3/5 v2] dma: pl08x: Make slave engine optional Linus Walleij
2017-05-20 21:42 ` [PATCH 4/5 v2] dma: pl08x: Add support for Faraday Technology FTDMAC020 Linus Walleij
2017-05-20 21:42 ` [PATCH 5/5 v2] dma: pl08x: use GENMASK() to create bitmasks Linus Walleij
2017-05-24 4:15 ` Vinod Koul [this message]
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=20170524041506.GW15061@localhost \
--to=vinod.koul@intel.com \
--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).