[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <A8AC22A0-E883-4D9B-A629-5A3721B976C5@flygoat.com>
Date: Tue, 21 Feb 2023 18:15:51 +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 0/7] MIPS DMA coherence fixes
> 2023年2月21日 17:54,Christoph Hellwig <hch@....de> 写道:
>
> Can you explain the motivation here? Also why riscv patches are at
> the end of a mips fіxes series?
Ah sorry for any confusion.
So the main purpose of this patch is to fix MIPS’s broken per-device coherency.
To be more precise, we want to be able to control the default coherency for all devices probed from
devicetree in early boot code.
To achieve that I decided to reuse dma_default_coherent to set default coherency for devicetree.
And all later patches are severing for this purpose.
Thanks
- Jiaxun
Powered by blists - more mailing lists