linux-kernel - Re: [PATCH] dmaengine: sprd: Fix the link-list pointer register configuration issue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20191014050313.GG27950@vkoul-mobl>
Date:   Mon, 14 Oct 2019 10:33:13 +0530
From:   Vinod Koul <vkoul@...nel.org>
To:     Baolin Wang <baolin.wang@...aro.org>
Cc:     orsonzhai@...il.com, zhang.lyra@...il.com,
        dan.j.williams@...el.com, linux-kernel@...r.kernel.org,
        dmaengine@...r.kernel.org, eric.long@...soc.com,
        zhenfang.wang@...soc.com
Subject: Re: [PATCH] dmaengine: sprd: Fix the link-list pointer register
 configuration issue

On 12-09-19, 13:47, Baolin Wang wrote:
> From: Zhenfang Wang <zhenfang.wang@...soc.com>
> 
> We will set the link-list pointer register point to next link-list
> configuration's physical address, which can load DMA configuration
> from the link-list node automatically.
> 
> But the link-list node's physical address can be larger than 32bits,
> and now Spreadtrum DMA driver only supports 32bits physical address,
> which may cause loading a incorrect DMA configuration when starting
> the link-list transfer mode. According to the DMA datasheet, we can
> use SRC_BLK_STEP register (bit28 - bit31) to save the high bits of the
> link-list node's physical address to fix this issue.

Applied, thanks

-- 
~Vinod