[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bcd31292-4caf-19fa-c4ea-d85c5fd77861@nvidia.com>
Date: Fri, 21 Jun 2019 08:36:26 +0530
From: Sameer Pujar <spujar@...dia.com>
To: Jon Hunter <jonathanh@...dia.com>, <vkoul@...nel.org>,
<dan.j.williams@...el.com>
CC: <thierry.reding@...il.com>, <ldewangan@...dia.com>,
<dmaengine@...r.kernel.org>, <linux-tegra@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] dmaengine: tegra210-adma: fix transfer failure
On 6/20/2019 10:13 PM, Jon Hunter wrote:
> On 20/06/2019 17:15, Sameer Pujar wrote:
>> From Tegra186 onwards OUTSTANDING_REQUESTS field is added in channel
>> configuration register (bits 7:4). ADMA allows a maximum of 8 reads
>> to source and that many writes to target memory be outstanding at any
>> given point of time. If this field is not programmed, DMA transfers
>> fail to happen.
> BTW, I am not sure I follow the above. You say a max of 8 reads to the
> source, however, the field we are programming can have a value of up to
> 15. So does that mean this field should only be programmed with a max of 8?
Yes. As per spec. ADMA allows max value of 8.
> Thanks
> Jon
>
Powered by blists - more mailing lists