From: Marcus Folkesson <marcus.folkesson@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Matt Ranostay <mranostay@gmail.com>,
Sandhya Bankar <bankarsandhya512@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: max1027: allocate DMA-safe buffer
Date: Sat, 10 Dec 2016 21:53:33 +0100 [thread overview]
Message-ID: <20161210205333.24gjh6vccyqdo5ll@gmail.com> (raw)
In-Reply-To: <915bf030-49c3-5d56-73c2-9c3da3f1a02e@kernel.org>
On Sat, Dec 10, 2016 at 05:36:34PM +0000, Jonathan Cameron wrote:
> On 09/12/16 10:24, Marcus Folkesson wrote:
> > The buffer needs to be DMA-safe when used with spi_read()
> >
> > Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
> Please read the documentation in include/linux/gfp.h about GFP_DMA.
>
> Specifically:
> 220 * GFP_DMA exists for historical reasons and should be avoided where possible.
> 221 * The flags indicates that the caller requires that the lowest zone be
> 222 * used (ZONE_DMA or 16M on x86-64). Ideally, this would be removed but
> 223 * it would require careful auditing as some users really require it and
> 224 * others use the flag to avoid lowmem reserves in ZONE_DMA and treat the
> 225 * lowest zone as a type of emergency reserve.
>
> Seems unlikely this applies! This caught me by surprise as I didn't even know
> that flag existed - hence I went digging.
>
> Jonathan
Always learn something!
I did not know it was depricated, seems like the comment about GFP_DMA was
commited just a year ago.
I had a problem with a driver on my own that by using a non
DMA-safe buffer, so I was digging around looking for similiar cases in
the kernel.
I thought other drivers (iio/common/ssp_sensors/sspi_spi.c,
input/rmi4/rmi_spi.c) was using GFP_DMA for this purpose.
Anyway, thanks.
Cheers,
Marcus Folkesson
next prev parent reply other threads:[~2016-12-10 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 10:24 Marcus Folkesson
2016-12-10 17:36 ` Jonathan Cameron
2016-12-10 20:53 ` Marcus Folkesson [this message]
2016-12-11 15:07 ` Jonathan Cameron
2016-12-12 17:31 ` Lars-Peter Clausen
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=20161210205333.24gjh6vccyqdo5ll@gmail.com \
--to=marcus.folkesson@gmail.com \
--cc=bankarsandhya512@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mranostay@gmail.com \
--cc=pmeerw@pmeerw.net \
/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
Powered by JetHome