[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <915bf030-49c3-5d56-73c2-9c3da3f1a02e@kernel.org>
Date: Sat, 10 Dec 2016 17:36:34 +0000
From: Jonathan Cameron <jic23@...nel.org>
To: Marcus Folkesson <marcus.folkesson@...il.com>,
Hartmut Knaack <knaack.h@....de>,
Lars-Peter Clausen <lars@...afoo.de>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
Matt Ranostay <mranostay@...il.com>,
Sandhya Bankar <bankarsandhya512@...il.com>
Cc: linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] iio: adc: max1027: allocate DMA-safe buffer
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@...il.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
> ---
> drivers/iio/adc/max1027.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/adc/max1027.c b/drivers/iio/adc/max1027.c
> index 712fbd2b1f16..ff1f1f15a873 100644
> --- a/drivers/iio/adc/max1027.c
> +++ b/drivers/iio/adc/max1027.c
> @@ -435,7 +435,7 @@ static int max1027_probe(struct spi_device *spi)
>
> st->buffer = devm_kmalloc(&indio_dev->dev,
> indio_dev->num_channels * 2,
> - GFP_KERNEL);
> + GFP_KERNEL | GFP_DMA);
> if (st->buffer == NULL) {
> dev_err(&indio_dev->dev, "Can't allocate buffer\n");
> return -ENOMEM;
>
Powered by blists - more mailing lists