[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <63639fa4-240b-0f7b-1adb-b79b2f33bef8@cogentembedded.com>
Date: Fri, 23 Dec 2016 16:07:49 +0300
From: Nikita Yushchenko <nikita.yoush@...entembedded.com>
To: Arnd Bergmann <arnd@...db.de>, linux-arm-kernel@...ts.infradead.org
Cc: Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Simon Horman <horms@...ge.net.au>,
Magnus Damm <magnus.damm@...il.com>,
Vladimir Barinov <vladimir.barinov@...entembedded.com>,
Artemi Ivanov <artemi.ivanov@...entembedded.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: arm64: mm: bug around swiotlb_dma_ops
> If trying to avoid big changes and only fixing particular problem with
> particular device not working on arm64, I think best way is to
> alter__swiotlb_dma_supported() in arch/arm64/mm/dma-mapping.c to detect
> and decline (with -EIO) mask that is unsupported by device connection.
> This will cover both dma_mask and coherent_dma_mask.
>
> This has to be combined with some way to explicitly extract information
> about limitations. Checking device parent's dma masks won't work unless
> somebody bothers to populate them.
I'm trying to bring together a patch doing this, will post that when ready
Powered by blists - more mailing lists