Received-SPF: pass (google.com: domain of linux-kernel+bounces-2735-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
From: Bjorn Andersson <andersson@kernel.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Andy Gross <agross@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH 0/2] arm64: dts: qcom: msm8916/39: Make blsp_dma controlled-remotely
Date: Sun, 17 Dec 2023 11:21:29 -0600
Message-ID: <170283349411.66089.7157787854311273289.b4-ty@kernel.org>
In-Reply-To: <20231204-msm8916-blsp-dma-remote-v1-0-3e49c8838c8d@gerhold.net>
References: <20231204-msm8916-blsp-dma-remote-v1-0-3e49c8838c8d@gerhold.net>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit


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@7884000 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@kernel.org>