[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3aias5ufn2gdta7lr4g2phzg4vfynarrup36zmiuxndd6zgzqc@6z57kf4wk4ut>
Date: Thu, 18 Apr 2024 18:52:46 +0300
From: Serge Semin <fancer.lancer@...il.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Viresh Kumar <vireshk@...nel.org>, Vinod Koul <vkoul@...nel.org>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jirislaby@...nel.org>, dmaengine@...r.kernel.org, linux-serial@...r.kernel.org,
linux-kernel@...r.kernel.org, Viresh Kumar <viresh.kumar@...aro.org>
Subject: Re: [PATCH 2/4] dmaengine: dw: Add memory bus width verification
On Thu, Apr 18, 2024 at 12:37:09PM +0300, Andy Shevchenko wrote:
> On Wed, Apr 17, 2024 at 09:52:42PM +0300, Serge Semin wrote:
> > On Wed, Apr 17, 2024 at 08:28:06PM +0300, Andy Shevchenko wrote:
> > > On Wed, Apr 17, 2024 at 08:13:59PM +0300, Serge Semin wrote:
>
> ...
>
> > > Got it. Maybe a little summary in the code to explain all this magic?
> >
> > Will it be enough to add something like this:
> > /*
> > * It's possible to have a data portion locked in the DMA FIFO in case
> > * of the channel suspension. Subsequent channel disabling will cause
> > * that data silent loss. In order to prevent that maintain the src
> > * and dst transfer widths coherency by means of the relation:
> > * (CTLx.SRC_TR_WIDTH * CTLx.SRC_MSIZE >= CTLx.DST_TR_WIDTH)
> > */
>
> Yes, and you may add something like
> "Look for the details in the commit message that brings this change."
> at the end of it.
Agreed. Thanks.
-Serge(y)
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
Powered by blists - more mailing lists