linux-kernel - Re: [PATCH 0/2] arm64: dts: qcom: msm8916/39: Make blsp

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]

Date: Sun, 17 Dec 2023 11:21:29 -0600
From: Bjorn Andersson <andersson@...nel.org>
To: Stephan Gerhold <stephan@...hold.net>
Cc: Andy Gross <agross@...nel.org>,
	Konrad Dybcio <konrad.dybcio@...aro.org>,
	Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
	linux-arm-msm@...r.kernel.org,
	devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	stable@...r.kernel.org
Subject: Re: [PATCH 0/2] arm64: dts: qcom: msm8916/39: Make blsp_dma controlled-remotely


On Mon, 04 Dec 2023 11:21:19 +0100, Stephan Gerhold wrote:
> The blsp_dma controller is shared between the different subsystems,
> which is why it is already initialized by the firmware. We should not
> reinitialize it from Linux to avoid potential other users of the DMA
> engine to misbehave.
> 
> In mainline this can be described using the "qcom,controlled-remotely"
> property. In the downstream/vendor kernel from Qualcomm there is an
> opposite "qcom,managed-locally" property. This property is *not* set
> for the qcom,sps-dma@...4000 so adding "qcom,controlled-remotely"
> upstream matches the behavior of the downstream/vendor kernel.
> 
> [...]

Applied, thanks!

[1/2] arm64: dts: qcom: msm8916: Make blsp_dma controlled-remotely
      commit: 7c45b6ddbcff01f9934d11802010cfeb0879e693
[2/2] arm64: dts: qcom: msm8939: Make blsp_dma controlled-remotely
      commit: 4bbda9421f316efdaef5dbf642e24925ef7de130

Best regards,
-- 
Bjorn Andersson <andersson@...nel.org>