From: Dan Williams <dan.j.williams@intel.com>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] DMAENGINE: generic slave, generic status
Date: Thu, 25 Mar 2010 08:20:29 -0700 [thread overview]
Message-ID: <4BAB7F3D.7090703@intel.com> (raw)
In-Reply-To: <1269529319-16369-1-git-send-email-linus.walleij@stericsson.com>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
Linus Walleij wrote:
> This patch set will enable generic functions for controlling
> slave transfers, e.g. the ability to pause and resume transfers,
> as well as the ability to read a wider status including not only
> the current and last transfer cookie but also the residual
> bytes left on a channel.
>
> This was discussed by Dan and Guennadi some while back and now
> I implemented it.
>
> I did my best to read my own code over and over again so I
> didn't break anything, but please review again.
>
> I need help: does someone have a list of defconfigs I need to
> compile to compile-check the entire DMA engine subsystem?
> I guess I will need a number of cross compilers as well, this
> is a bit hairy but will probably help out in future refactoring
> as well if I can get them to fly.
I can check this out with my dmaengine build system. I have attached
the script and the defconfigs that I use. Yes, it does require a small
arsenal of cross-compilers.
--
Dan
[-- Attachment #2: build_dma.tar.gz --]
[-- Type: application/gzip, Size: 91651 bytes --]
next prev parent reply other threads:[~2010-03-25 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 15:01 [PATCH 0/2] DMAENGINE: generic slave, generic status Linus Walleij
2010-03-25 15:20 ` Dan Williams [this message]
2010-03-26 9:26 ` 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=4BAB7F3D.7090703@intel.com \
--to=dan.j.williams@intel.com \
--cc=g.liakhovetski@gmx.de \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox