From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: "Dan Williams" <dan.j.williams@intel.com>,
"Vinod Koul" <vinod.koul@intel.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, dmaengine@vger.kernel.org,
"Russell King" <linux@arm.linux.org.uk>,
"Arnd Bergmann" <arnd@arndb.de>,
"Antoine Ténart" <antoine@free-electrons.com>,
"Thomas Petazzoni" <thomas@free-electrons.com>,
"Alexandre Belloni" <alexandre.belloni@free-electrons.com>,
"Boris Brezillon" <boris@free-electrons.com>,
"Matt Porter" <matt.porter@linaro.org>,
"Gregory Clement" <gregory.clement@free-electrons.com>,
"Nicolas Ferre" <nicolas.ferre@atmel.com>
Subject: Re: [PATCH v2 2/2] Documentation: dmaengine: Add a documentation for the dma controller API
Date: Wed, 22 Oct 2014 23:08:14 +0300 [thread overview]
Message-ID: <3369016.M8rcEK3Bf6@avalon> (raw)
In-Reply-To: <20141017112356.GO19438@lukather>
Hi Maxime,
On Friday 17 October 2014 13:23:56 Maxime Ripard wrote:
> Hi Laurent,
>
> Just getting back on something...
>
> On Mon, Oct 06, 2014 at 03:09:48PM +0300, Laurent Pinchart wrote:
> > > + * device_prep_dma_*
> > > + - These functions are matching the capabilities you registered
> > > + previously.
> > > + - These functions all take the buffer or the scatterlist relevant
> > > + for the transfer being prepared, and should create a hardware
> > > + descriptor or a list of descriptors from it
> > > + - These functions can be called from an interrupt context
> > > + - Any allocation you might do should be using the GFP_NOWAIT
> > > + flag, in order not to potentially sleep, but without depleting
> > > + the emergency pool either.
> >
> > You could add "Drivers should try to preallocate the data structures they
> > require to prepare a transfer."
>
> Isn't that obvious?
>
> I mean, if we're in this function, we're already preparing a
> transfer... And I would expect any programmer that followed CS101 to
> be able to allocate the memory it needs :)
I meant that memory should be pre-allocated earlier (at probe time or channel
alloc time for instance) to avoid putting pressure on the nowait memory pool.
> The rest of the issues have been fixed, thanks!
> Maxime
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-10-22 20:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 15:40 [PATCH v2 1/2] Documentation: dmaengine: Move the current doc to a folder of its own Maxime Ripard
2014-09-26 15:40 ` [PATCH v2 2/2] Documentation: dmaengine: Add a documentation for the dma controller API Maxime Ripard
2014-09-26 18:04 ` Randy Dunlap
2014-10-07 16:48 ` Maxime Ripard
2014-10-06 12:09 ` Laurent Pinchart
2014-10-07 12:16 ` Nicolas Ferre
2014-10-07 14:52 ` Maxime Ripard
2014-10-07 15:05 ` Laurent Pinchart
2014-10-08 12:19 ` Vinod Koul
2014-10-09 8:56 ` Laurent Pinchart
2014-10-08 12:07 ` Vinod Koul
2014-10-09 13:39 ` Geert Uytterhoeven
2014-10-09 14:04 ` Nicolas Ferre
2014-10-17 11:23 ` Maxime Ripard
2014-10-22 20:08 ` Laurent Pinchart [this message]
2014-09-28 15:57 ` [PATCH v2 1/2] Documentation: dmaengine: Move the current doc to a folder of its own Vinod Koul
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=3369016.M8rcEK3Bf6@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=antoine@free-electrons.com \
--cc=arnd@arndb.de \
--cc=boris@free-electrons.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=matt.porter@linaro.org \
--cc=maxime.ripard@free-electrons.com \
--cc=nicolas.ferre@atmel.com \
--cc=thomas@free-electrons.com \
--cc=vinod.koul@intel.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 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).