[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190816222506.GA24413@Asurada-Nvidia.nvidia.com>
Date: Fri, 16 Aug 2019 15:25:07 -0700
From: Nicolin Chen <nicoleotsuka@...il.com>
To: Tobias Klausmann <tobias.johannes.klausmann@....thm.de>
Cc: Christoph Hellwig <hch@....de>, kvalo@...eaurora.org,
davem@...emloft.net, ath10k@...ts.infradead.org,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, m.szyprowski@...sung.com,
robin.murphy@....com, iommu@...ts.linux-foundation.org,
tobias.klausmann@...enet.de
Subject: Re: regression in ath10k dma allocation
Hi Tobias
On Fri, Aug 16, 2019 at 10:16:45PM +0200, Tobias Klausmann wrote:
> > do you have CONFIG_DMA_CMA set in your config? If not please make sure
> > you have this commit in your testing tree, and if the problem still
> > persists it would be a little odd and we'd have to dig deeper:
> >
> > commit dd3dcede9fa0a0b661ac1f24843f4a1b1317fdb6
> > Author: Nicolin Chen <nicoleotsuka@...il.com>
> > Date: Wed May 29 17:54:25 2019 -0700
> >
> > dma-contiguous: fix !CONFIG_DMA_CMA version of dma_{alloc, free}_contiguous()
> yes CONFIG_DMA_CMA is set (=y, see attached config), the commit you mention
> above is included, if you have any hints how to go forward, please let me
> know!
For CONFIG_DMA_CMA=y, by judging the log with error code -12, I
feel this one should work for you. Would you please check if it
is included or try it out otherwise?
dma-contiguous: do not overwrite align in dma_alloc_contiguous()
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=c6622a425acd1d2f3a443cd39b490a8777b622d7
Thanks
Nicolin
Powered by blists - more mailing lists