Received: by 2002:a05:6358:45e:b0:b5:b6eb:e1f9 with SMTP id 30csp842932rwe; Thu, 25 Aug 2022 10:03:39 -0700 (PDT) X-Google-Smtp-Source: AA6agR6uJ+3GkLKvKO0bGNkX9E0CgsfgBDQpOWneKP41ACN+G92BoHnAWLbgtyl8dCk6D5xxKceS X-Received: by 2002:a63:6804:0:b0:422:1689:ed05 with SMTP id d4-20020a636804000000b004221689ed05mr32202pgc.289.1661447019611; Thu, 25 Aug 2022 10:03:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1661447019; cv=none; d=google.com; s=arc-20160816; b=g7uOL5J++gtMV2h9gAnPjFZq+mb5NVamkDwNJyIG3nP+hSQKqyC91EkjiQEUzrtQGw Fp2GerRmn5E5DiufO1eWv4KdPmsbKecehvHJ2r06F5Kue+EAaUJXtMH9j90BHd0ouyGN Q2VzSU0qNRemKUayegnEfCJX+i79O9QqkG2Xd7Frju5nBeMSfusVCXjSb1v8jnLQ9HdW 9NU9lC8dg+rRioecL3ta2JozC5L3qs8IiuiUZoKEjg4Wy8e+m986Nh3EOdrshBZI8cbg y8SwT6mX3vgAlImZWbZE9vO0hIZvxH+i3fZWinkzbivbxfO9khRbHw+tblmW2yoBBS7e urkQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=0TbBYS0Nqh3bgSdnakQbiIorETtqlVR3C7+nG6SfSzA=; b=PUEgmPOpKcPsiSVBCiZREUFW5QXuhBpo3EhRXgsTGbSerB036AAxjaF0sF9jfdxJ9G Qc1Wvd6obqTah0Sa0pgruS2UJbKR58HOf/qEPdEdK2fcfenE+Us+svzemj3JFHnF6Fu2 2oTsoSz8JGSKYdpshtS5IJ18WxzRa77ucAT8Hge0Tv8R8Kaph1N7hGu2ZgxKa4DC8X/U 5NDZ4GGfqqWLnLrHw+rBThAN6M7RoIxLj3FkFQcSmqGXaAP3R0iKuKJmNouJIWWpok9y 2AiI5Z8B9FvIZ6unJMEptbEWEpZ+dKegKQZKMiv33jUwEnp27cRmeQeeYCvtvVeGAcEO vN5w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=A1CPNa0A; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id y9-20020a17090322c900b00172f12565c5si10558719plg.228.2022.08.25.10.03.27; Thu, 25 Aug 2022 10:03:39 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=A1CPNa0A; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243354AbiHYQoL (ORCPT + 99 others); Thu, 25 Aug 2022 12:44:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43542 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243233AbiHYQnW (ORCPT ); Thu, 25 Aug 2022 12:43:22 -0400 Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7A32CBC10C for ; Thu, 25 Aug 2022 09:42:45 -0700 (PDT) Received: by mail-pf1-x42d.google.com with SMTP id x19so17546365pfq.1 for ; Thu, 25 Aug 2022 09:42:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc; bh=0TbBYS0Nqh3bgSdnakQbiIorETtqlVR3C7+nG6SfSzA=; b=A1CPNa0ANiPIdOyEFNl/pcWWHZNCIdrC1EKRfKXZhZ3NFYRg1PtX1Htujhmy2fze4Z /sL7i/WiChF1ZA4G4yrV3SHo/peV+S3COXHuyBg9SJMbLojnHVFCdT51DvjJWG2SbJWJ VCq61CHAOGfIFj/j+Bbdp4F9a0Ndbywt3RpXI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc; bh=0TbBYS0Nqh3bgSdnakQbiIorETtqlVR3C7+nG6SfSzA=; b=ubfAT98mYqYn32nzJrsYmPKBXKUqQd4RfUjXdA9gY5HILu4HxCQi9Q0hAJKak2woi8 xNYmwA276fp/SxIZf1SMHfmecv5bocdox8CjcOgumpSE8bMhVazgln1nr1Eo7B4pbVvt /YPqByAfNJgdZ3JeXmLFBYqmtmnT0f0UnJdmMOzGM6MYpsnp5Enia5m09rn383xDq8QG RPXpaywdYdB9z17pTwn5uUnFA1yxbVjVr19WtiaSsUxz+cEXS0SaFmokcPlyzeWpMiSh 333st7pyx5BbYwMSjCQfKU61mI3BDZarwME+DaYpau/godpQWXvFmQ8JSle+xp+6VqZy Fy+Q== X-Gm-Message-State: ACgBeo3Ut/X1F5TvQpmd4gfOBvKraLcC3uw7TVg8CF0Lr3GZFWI/o8lv rwsXlR3taUH0jUqPBV62w34xjQ== X-Received: by 2002:a63:e102:0:b0:41b:3901:990e with SMTP id z2-20020a63e102000000b0041b3901990emr3893320pgh.107.1661445764637; Thu, 25 Aug 2022 09:42:44 -0700 (PDT) Received: from tictac2.mtv.corp.google.com ([2620:15c:202:201:b7f2:d739:e847:6e53]) by smtp.gmail.com with ESMTPSA id y13-20020a17090a154d00b001f2ef3c7956sm3775799pja.25.2022.08.25.09.42.42 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 25 Aug 2022 09:42:43 -0700 (PDT) From: Douglas Anderson To: Bjorn Andersson Cc: Andrew Halaney , Mark Brown , Douglas Anderson , Andy Gross , Konrad Dybcio , Krzysztof Kozlowski , Rob Herring , Vinod Koul , devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 7/7] arm64: dts: qcom: sm8350-hdk: Specify which LDO modes are allowed Date: Thu, 25 Aug 2022 09:42:05 -0700 Message-Id: <20220825094155.7.I6799be85cf36d3b494f803cba767a569080624f5@changeid> X-Mailer: git-send-email 2.37.2.672.g94769d06f0-goog In-Reply-To: <20220825164205.4060647-1-dianders@chromium.org> References: <20220825164205.4060647-1-dianders@chromium.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This board uses RPMH, specifies "regulator-allow-set-load" for LDOs, but doesn't specify any modes with "regulator-allowed-modes". Prior to commit efb0cb50c427 ("regulator: qcom-rpmh: Implement get_optimum_mode(), not set_load()") the above meant that we were able to set either LPM or HPM mode. After that commit (and fixes [1]) we'll be stuck at the initial mode. Discussion of this has resulted in the decision that the old dts files were wrong and should be fixed to fully restore old functionality. Let's re-enable the old functionality by fixing the dts. [1] https://lore.kernel.org/r/20220824142229.RFT.v2.2.I6f77860e5cd98bf5c67208fa9edda4a08847c304@changeid Fixes: 9208c19f2124 ("arm64: dts: qcom: Introduce SM8350 HDK") Signed-off-by: Douglas Anderson --- arch/arm64/boot/dts/qcom/sm8350-hdk.dts | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/sm8350-hdk.dts b/arch/arm64/boot/dts/qcom/sm8350-hdk.dts index 0fcf5bd88fc7..69ae6503c2f6 100644 --- a/arch/arm64/boot/dts/qcom/sm8350-hdk.dts +++ b/arch/arm64/boot/dts/qcom/sm8350-hdk.dts @@ -107,6 +107,9 @@ vreg_l5b_0p88: ldo5 { regulator-max-microvolt = <888000>; regulator-initial-mode = ; regulator-allow-set-load; + regulator-allowed-modes = + ; }; vreg_l6b_1p2: ldo6 { @@ -115,6 +118,9 @@ vreg_l6b_1p2: ldo6 { regulator-max-microvolt = <1208000>; regulator-initial-mode = ; regulator-allow-set-load; + regulator-allowed-modes = + ; }; vreg_l7b_2p96: ldo7 { @@ -123,6 +129,9 @@ vreg_l7b_2p96: ldo7 { regulator-max-microvolt = <2504000>; regulator-initial-mode = ; regulator-allow-set-load; + regulator-allowed-modes = + ; }; vreg_l9b_1p2: ldo9 { @@ -131,6 +140,9 @@ vreg_l9b_1p2: ldo9 { regulator-max-microvolt = <1200000>; regulator-initial-mode = ; regulator-allow-set-load; + regulator-allowed-modes = + ; }; }; -- 2.37.2.672.g94769d06f0-goog