[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e78107ae-e2d9-4ffb-9a2a-bc04426e2a75@linaro.org>
Date: Tue, 10 Jun 2025 10:03:18 +0100
From: James Clark <james.clark@...aro.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: Vladimir Oltean <vladimir.oltean@....com>, linux-spi@...r.kernel.org,
imx@...ts.linux.dev, linux-kernel@...r.kernel.org,
Vladimir Oltean <olteanv@...il.com>, Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH 2/4] spi: spi-fsl-dspi: Use non-coherent memory for DMA
On 10/06/2025 9:26 am, Arnd Bergmann wrote:
> On Mon, Jun 9, 2025, at 17:32, James Clark wrote:
>> Using coherent memory here isn't functionally necessary. Because the
>> change to use non-coherent memory isn't overly complex and only a few
>> synchronization points are required, we might as well do it while fixing
>> up some other DMA issues.
>>
>> Suggested-by: Arnd Bergmann <arnd@...db.de>
>> Signed-off-by: James Clark <james.clark@...aro.org>
>
> This version looks good to me,
>
> Acked-by: Arnd Bergmann <arnd@...db.de>
>
> I had reviewed an internal version originally and had some comment
> on that, all of which are addressed now. You did not Cc me on the
> other patches, so I looked them up in the archive, Patch 3 also
Yes sorry about that. I've just started using "b4 send" and I was under
the impression that it would automatically CC all patches the same way,
but apparently not. Maybe I'm holding it wrong.
> looks good to me and complements this one (i.e. you really want
> the combination). I did not understand the logic in patch 4,
> and it would be good if someone else can take a closer look
> at that in order to Ack that.
>
> Arnd
Powered by blists - more mailing lists