On Sun, 26 Jan 2020 at 12:53, Michael Ellerman wrote:
>
> There's an OF helper called of_dma_is_coherent(), which checks if a
> device has a "dma-coherent" property to see if the device is coherent
> for DMA.
>
> But on some platforms devices are coherent by default, and on some
> platforms it's n
Krzysztof Kozlowski wrote:
> The ioreadX() helpers have inconsistent interface. On some architectures
> void *__iomem address argument is a pointer to const, on some not.
>
> Implementations of ioreadX() do not modify the memory under the address
> so they can be converted to a "const" version
allnoconfig
s390 allyesconfig
s390 debug_defconfig
s390defconfig
s390 zfcpdump_defconfig
configs tested: 120
configs skipped: 0
x86_64 randconfig-c003-20200126
alpha
allnoconfig
i386 allyesconfig
i386defconfig
x86_64 randconfig-g001-20200126
x86_64 randconfig-g002-20200126
x86_64 randconfig-g003-20200126
i386 randconfig-g001
There's an OF helper called of_dma_is_coherent(), which checks if a
device has a "dma-coherent" property to see if the device is coherent
for DMA.
But on some platforms devices are coherent by default, and on some
platforms it's not possible to update existing device trees to add the
"dma-coherent
Dan Williams writes:
> On Fri, Jan 24, 2020 at 9:07 AM Aneesh Kumar K.V
> wrote:
>>
>> On 1/24/20 10:15 PM, Dan Williams wrote:
>> > On Thu, Jan 23, 2020 at 11:34 PM Aneesh Kumar K.V
>> > wrote:
>> >>
>> >> On 1/24/20 11:27 AM, Dan Williams wrote:
>> >>> On Mon, Jan 20, 2020 at 6:08 AM Aneesh K
