[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <9AD04590-81B1-4420-979E-ACC1C7C6C8E8@flygoat.com>
Date: Tue, 21 Feb 2023 18:18:58 +0000
From: Jiaxun Yang <jiaxun.yang@...goat.com>
To: Christoph Hellwig <hch@....de>
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>, m.szyprowski@...sung.com,
robin.murphy@....com
Subject: Re: [PATCH 5/7] dma-mapping: Provide CONFIG_ARCH_DMA_DEFAULT_COHERENT
> 2023年2月21日 17:58,Christoph Hellwig <hch@....de> 写道:
>
> On Tue, Feb 21, 2023 at 12:46:11PM +0000, Jiaxun Yang wrote:
>> Provide a kconfig option to allow arches to manipulate default
>> value of dma_default_coherent in Kconfig.
>
> I don't see the win over just doing this by setting dma_default_coherent
> in the early boot code.
I just don’t want to dig into every archs’ early boot code to decide a good
timing for setting this variable.
Also as we do have a OF_DMA_DEFAULT_COHERENT before it makes more
sense to me.
Thanks
- Jiaxun
Powered by blists - more mailing lists