[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <D9DE553D-07F7-46EA-96E6-AA2A6ED5F6C6@flygoat.com>
Date: Tue, 21 Feb 2023 18:20:02 +0000
From: Jiaxun Yang <jiaxun.yang@...goat.com>
To: Conor Dooley <conor@...nel.org>
Cc: "linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>,
linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
mpe@...erman.id.au, paul.walmsley@...ive.com, palmer@...belt.com,
Rob Herring <robh+dt@...nel.org>,
Christoph Hellwig <hch@....de>, m.szyprowski@...sung.com,
robin.murphy@....com
Subject: Re: [PATCH 6/7] riscv: Select ARCH_DMA_DEFAULT_COHERENT
> 2023年2月21日 18:14,Conor Dooley <conor@...nel.org> 写道:
>
> On Tue, Feb 21, 2023 at 12:46:12PM +0000, Jiaxun Yang wrote:
>> For RISCV we always assume devices are DMA coherent.
>
> "Always assume", I'm not keen on that wording as it is unclear as to
> whether you are suggesting that a) we always take devices to be DMA
> coherent, or b) unless a device states it is non-coherent, we take it to
> be DMA coherent.
> I think you mean b, but being exact would be appreciated, thanks.
Yep I meant option b, thanks for the point.
>
>> Select ARCH_DMA_DEFAULT_COHERENT to ensure dev->dma_conherent
>> is always initialized to true.
>>
>> Signed-off-by: Jiaxun Yang <jiaxun.yang@...goat.com>
>
> Why was this not sent to the riscv list?
> When (or if) you send v2, can you please make sure that you do cc it?
Will do.
Thanks
- Jiaxun
>
> Thanks,
> Conor.
Powered by blists - more mailing lists