From nobody Tue Feb 10 09:43:12 2026 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 720FAEB64DD for ; Wed, 21 Jun 2023 14:36:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231826AbjFUOgt (ORCPT ); Wed, 21 Jun 2023 10:36:49 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48248 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232066AbjFUOgj (ORCPT ); Wed, 21 Jun 2023 10:36:39 -0400 Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 887D81BCF for ; Wed, 21 Jun 2023 07:36:32 -0700 (PDT) Received: by mail-wm1-x32c.google.com with SMTP id 5b1f17b1804b1-3f8fcaa31c7so65644885e9.3 for ; Wed, 21 Jun 2023 07:36:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1687358191; x=1689950191; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=Q267PzQvbc4qiFwzCDZZB6FJw0yi1HjyAE+qzfNhuaE=; b=rctvtICKF4lpjMQ4GFaTKRkNEYiwDdBGk+QsCrkbDIvg2uKEXYwGN3Wa0p+Vkp04Qu Mc+CJdKQoGg2fnW3O2noq9sVKVt1r2fp4uGqKX8clqnunM31HC2FP78fjWw16TzOIJze yG6G9rpvpMV9bVY1CxNBf0JbNnSU0ACalWYnWbsOh7tSZ59syXRaQMYxm8kaLiZJ4MSF qj3FILCAHpak5gHHfuP5rLYG1uJK3fBWnr9xLRiyalNDbRc6nYwRPLLMImk0Ijf+iTCS K3StGdsijCQgTHT9Tm0nDauIz4fR8T0CZr4wVVEaCfCkc1CnkrnQHCoX6wlYLQLEYsfW 65Uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687358191; x=1689950191; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Q267PzQvbc4qiFwzCDZZB6FJw0yi1HjyAE+qzfNhuaE=; b=LY9tnZdhM+mwPHqCJ6BRi9dNDorvMBN6KTp8wWE3+6sMzU9H8TwiUORuMGfcfnaxMI FHLrGcFTWJZyXltnpcJYbDUaGsSH6XoY1HhbAG4V/lZ5/VTb7sLCCQ5rFpeFFWtO5asg 2afB4ILYtrU2RGMGVess3j5sKblCNNzynr9QrdLF/hxPKIZOsmG9L0XbaVxAPQqWlma3 WAvjm/dvFE3ijEyE2xV96fUssEFD2d6aHw2P1EMlrnT0D0V72hJCuiQTPFww53umN3a5 o6Wl5/h+Mo1+yZg9WZhbKevoZmgWmRWQUhyUUn6Cf1UZOolL1AsOYsL1NX+ZoQIWkEgt x9dg== X-Gm-Message-State: AC+VfDybrvJoeKkuQbVl2imQ6mSC9GG5e5xjziKFUGw9uXUE/T2ElCwy iMAogJwnIlOsTAFPPK/ZW7waNmuKcwwgknYNMMM= X-Google-Smtp-Source: ACHHUZ5ZhzIpeWIh4DikrGJcv3Fx3/cxAiObvcEZly48e8AIamOEO6BA+6S4z/LW5iad5YqDZNOJlw== X-Received: by 2002:a05:600c:281:b0:3f9:960:2bb7 with SMTP id 1-20020a05600c028100b003f909602bb7mr11643793wmk.23.1687358190927; Wed, 21 Jun 2023 07:36:30 -0700 (PDT) Received: from krzk-bin.. ([178.197.219.26]) by smtp.gmail.com with ESMTPSA id y9-20020adfdf09000000b0031122bd3c82sm4642396wrl.17.2023.06.21.07.36.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 21 Jun 2023 07:36:30 -0700 (PDT) From: Krzysztof Kozlowski To: Andy Gross , Bjorn Andersson , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Bhupesh Sharma , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Krzysztof Kozlowski , Manivannan Sadhasivam Subject: [PATCH] arm64: dts: qcom: sm8350: fix BAM DMA crash and reboot Date: Wed, 21 Jun 2023 16:36:27 +0200 Message-Id: <20230621143627.189134-1-krzysztof.kozlowski@linaro.org> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="utf-8" SM8350 HDK and MTP boards were silently dying and rebooting during BAM DMA probe: [ 1.574304] vreg_bob: Setting 3008000-3960000uV [ 1.576918] bam-dFormat: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=3DBOOT.MXF.1.0-00637.1-LAHAINA-1 S - IMAGE_VARIANT_STRING=3DSocLahainaLAA S - OEM_IMAGE_VERSION_STRING=3Dcrm-ubuntu77 S - Boot Interface: UFS It seems that BAM DMA is locally controller (not by firmware) and requires proper initialization by the driver prior to use, at least on HDK8350 and MTP8350, but probably on all boards. Fixes: f1040a7fe8f0 ("arm64: dts: qcom: sm8350: Add Crypto Engine support") Signed-off-by: Krzysztof Kozlowski Acked-by: Manivannan Sadhasivam Reviewed-by: Konrad Dybcio Tested-by: Konrad Dybcio # SM8350 PDX215 --- Cc: Manivannan Sadhasivam --- arch/arm64/boot/dts/qcom/sm8350.dtsi | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/arm64/boot/dts/qcom/sm8350.dtsi b/arch/arm64/boot/dts/qco= m/sm8350.dtsi index 88ef478cb5cc..b382ce66387e 100644 --- a/arch/arm64/boot/dts/qcom/sm8350.dtsi +++ b/arch/arm64/boot/dts/qcom/sm8350.dtsi @@ -1741,7 +1741,6 @@ cryptobam: dma-controller@1dc4000 { interrupts =3D ; #dma-cells =3D <1>; qcom,ee =3D <0>; - qcom,controlled-remotely; iommus =3D <&apps_smmu 0x594 0x0011>, <&apps_smmu 0x596 0x0011>; }; --=20 2.34.1