linux-kernel - Re: [PATCH v2] dmaengine: qcom: bam_dma: Fix BAM

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 for Android: free password hash cracker in your pocket

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

Message-ID: <211df2ed-0e01-ccb5-ca3d-1d021361ea5e@quicinc.com>
Date: Mon, 20 Jan 2025 11:55:25 +0530
From: Md Sadre Alam <quic_mdalam@...cinc.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
CC: <vkoul@...nel.org>, <robin.murphy@....com>,
        <linux-arm-msm@...r.kernel.org>, <dmaengine@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <quic_varada@...cinc.com>,
        <quic_srichara@...cinc.com>
Subject: Re: [PATCH v2] dmaengine: qcom: bam_dma: Fix BAM_RIVISON register
 handling



On 1/19/2025 11:11 AM, Manivannan Sadhasivam wrote:
> On Fri, Jan 17, 2025 at 04:43:02PM +0530, Md Sadre Alam wrote:
>> This patch resolves a bug from the previous commit where the
>> BAM_DESC_CNT_TRSHLD register was conditionally written based on BAM-NDP
>> mode. It also fixes an issue where reading the BAM_REVISION register
> 
> The 'also' sounds like the patch is fixing 2 issues, but it is just fixing one.
Will update the commit message in next revision.
> 
>> would hang if num-ees was not zero, which occurs when the SoCs power on
>> BAM remotely. The BAM_REVISION register read has been moved to inside if
>> condition.
>>
>> Cc: stable@...r.kernel.org
> 
> The offending commit is just in the -next branch. So CCing stable is pointless.
Ok, will remove in next revision.
> 
> - Mani
>