On Thu, Aug 15, 2024 at 02:27:23PM GMT, Md Sadre Alam wrote: > enable bam pipe locking/unlocking for ipq9507 SoC. Note that the commit messages for the other non-dts commits will not show up in the git history for this file. So, please follow https://docs.kernel.org/process/submitting-patches.html#describe-your-changes and give some indication of "problem description", to give future readers an idea why this is here. > > Signed-off-by: Md Sadre Alam <quic_mdalam@xxxxxxxxxxx> > --- > > Change in [v2] > > * enabled locking/unlocking support for ipq9574 > > Change in [v1] > > * This patch was not included in [v1] > > arch/arm64/boot/dts/qcom/ipq9574.dtsi | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/arch/arm64/boot/dts/qcom/ipq9574.dtsi b/arch/arm64/boot/dts/qcom/ipq9574.dtsi > index 48dfafea46a7..dacaec62ec39 100644 > --- a/arch/arm64/boot/dts/qcom/ipq9574.dtsi > +++ b/arch/arm64/boot/dts/qcom/ipq9574.dtsi > @@ -262,6 +262,7 @@ cryptobam: dma-controller@704000 { > #dma-cells = <1>; > qcom,ee = <1>; > qcom,controlled-remotely; > + qcom,bam_pipe_lock; Per the question before about what does this actually lock. Is this a property of the BAM controller, or the crypto channel? Regards, Bjorn > }; > > crypto: crypto@73a000 { > -- > 2.34.1 >
