> dan.j.willi...@intel.com; s.ha...@pengutronix.de; li...@armlinux.or
> > g.uk
> > Cc: dmaeng...@vger.kernel.org; dl-linux-imx ;
> > ker...@pengutronix.de; linux-arm-ker...@lists.infradead.org;
> > linux-kernel@vger.kernel.org
> > Subject: RE: [PATCH v3 3/3]
> dan.j.willi...@intel.com; s.ha...@pengutronix.de; li...@armlinux.or
> > g.uk
> > Cc: dmaeng...@vger.kernel.org; dl-linux-imx ;
> > ker...@pengutronix.de; linux-arm-ker...@lists.infradead.org;
> > linux-kernel@vger.kernel.org
> > Subject: RE: [PATCH v3 3/3]
-linux-imx ;
> ker...@pengutronix.de; linux-arm-ker...@lists.infradead.org;
> linux-kernel@vger.kernel.org
> Subject: RE: [PATCH v3 3/3] dmaengine: imx-sdma: allocate max 20 bds for one
> transfer
>
> > -Original Message-
> > From: Lucas Stach [mailto:l.st...@pengutronix
-linux-imx ;
> ker...@pengutronix.de; linux-arm-ker...@lists.infradead.org;
> linux-kernel@vger.kernel.org
> Subject: RE: [PATCH v3 3/3] dmaengine: imx-sdma: allocate max 20 bds for one
> transfer
>
> > -Original Message-
> > From: Lucas Stach [mailto:l.st...@pengutronix
pengutronix.de; linux-arm-ker...@lists.infradead.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v3 3/3] dmaengine: imx-sdma: allocate max 20 bds for one
> transfer
>
> Am Montag, den 23.07.2018, 13:55 + schrieb Robin Gong:
> > > -Original Mess
pengutronix.de; linux-arm-ker...@lists.infradead.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v3 3/3] dmaengine: imx-sdma: allocate max 20 bds for one
> transfer
>
> Am Montag, den 23.07.2018, 13:55 + schrieb Robin Gong:
> > > -Original Mess
..@armlinux.or
> > g.uk
> > Cc: dmaeng...@vger.kernel.org; dl-linux-imx ;
> > ker...@pengutronix.de; linux-arm-ker...@lists.infradead.org;
> > linux-kernel@vger.kernel.org
> > Subject: Re: [PATCH v3 3/3] dmaengine: imx-sdma: allocate max 20
> > bds for one
>
..@armlinux.or
> > g.uk
> > Cc: dmaeng...@vger.kernel.org; dl-linux-imx ;
> > ker...@pengutronix.de; linux-arm-ker...@lists.infradead.org;
> > linux-kernel@vger.kernel.org
> > Subject: Re: [PATCH v3 3/3] dmaengine: imx-sdma: allocate max 20
> > bds for one
>
pengutronix.de; linux-arm-ker...@lists.infradead.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v3 3/3] dmaengine: imx-sdma: allocate max 20 bds for one
> transfer
>
> Am Dienstag, den 24.07.2018, 01:46 +0800 schrieb Robin Gong:
> > If multi-bds used in one transfer,
pengutronix.de; linux-arm-ker...@lists.infradead.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v3 3/3] dmaengine: imx-sdma: allocate max 20 bds for one
> transfer
>
> Am Dienstag, den 24.07.2018, 01:46 +0800 schrieb Robin Gong:
> > If multi-bds used in one transfer,
Am Dienstag, den 24.07.2018, 01:46 +0800 schrieb Robin Gong:
> If multi-bds used in one transfer, all bds should be consisten
> memory.To easily follow it, enlarge the dma pool size into 20 bds,
> and it will report error if the number of bds is over than 20. For
> dmatest, the max count for
Am Dienstag, den 24.07.2018, 01:46 +0800 schrieb Robin Gong:
> If multi-bds used in one transfer, all bds should be consisten
> memory.To easily follow it, enlarge the dma pool size into 20 bds,
> and it will report error if the number of bds is over than 20. For
> dmatest, the max count for
If multi-bds used in one transfer, all bds should be consisten
memory.To easily follow it, enlarge the dma pool size into 20 bds,
and it will report error if the number of bds is over than 20. For
dmatest, the max count for single transfer is NUM_BD *
SDMA_BD_MAX_CNT = 20 * 65535 = ~1.28MB.
If multi-bds used in one transfer, all bds should be consisten
memory.To easily follow it, enlarge the dma pool size into 20 bds,
and it will report error if the number of bds is over than 20. For
dmatest, the max count for single transfer is NUM_BD *
SDMA_BD_MAX_CNT = 20 * 65535 = ~1.28MB.
14 matches
Mail list logo