Received: by 2002:ac0:da4c:0:0:0:0:0 with SMTP id a12csp557523imi; Thu, 21 Jul 2022 06:37:06 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vzQx7wbv2EYrn5eUUkgxvFPOGITNDOMdMjryecf/8JuOx8zJrU/whuvQioMRUHgcHizdxU X-Received: by 2002:a05:6638:aca:b0:33f:5888:ea0f with SMTP id m10-20020a0566380aca00b0033f5888ea0fmr22677868jab.39.1658410625898; Thu, 21 Jul 2022 06:37:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658410625; cv=none; d=google.com; s=arc-20160816; b=ejfmeHq1zqk6kh58SKhtES07PTXCui6DRfYZxTp81BPqcxbhPL8ULHP5RK6dYiIs29 Gph8U7SgtJxVY5aIe9tzu3PPjvqX2rI4F2/yIvI2nHdzWTyBN8Mjxe16Dt1saoE25jX/ adhPPEPXYVPhpEooPYmDUoR0Wn36uKRe3MDdCHfRYNug7vzgXVtImfN9eB6pKNWfGJ9P u+JejkiqLrPY/1e06sXXh7TrYToMEg4XrAYNPkVL05g9HniUp8R7nwRXiVABL3aswdVB Cth++DWaJ5bstC4M7TA4FMv8NeVqB54WmUUYIJS3bnTv/4I5D/OgLPPQp6PvqQAkOSWC XYjg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=DGrBLaNIprWPnLASVzucMIdeH8IwcuTiWBUYmrgNEq4=; b=j/BK41aynn7YuV7FCiuCLvPErw9Ez16wjPbJdfK1IDwwH0L8TTbftAYfnyB98Xj1qX jO8+J5STYaePoIvf3GOGlnCJDUxIosMLg/s7LsEyJDcMzx05PYhYW+73ENbkI366hmt9 +vpeZrml5AyWfdEE9zCwbguh6RXiA7/w2bJFGByq2Ajl2L0rs7MkScOs0tyhP3qzzzt8 fmSPPSeYoBNVyDI3G9Z/fUMEv62TuM5BXoduaP2Ei1AFofeGhymUwQmH9+O/HOjuplQl od+4y4n73HC5PPtZ9vA5N1zrSV6AbANXFfuSbJpywM9syik+KmMOOwejLCwIhbsVV5pW +JSA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=blMArCRI; 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=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id n27-20020a02715b000000b0032de0c106a0si1339495jaf.21.2022.07.21.06.36.49; Thu, 21 Jul 2022 06:37:05 -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=@linaro.org header.s=google header.b=blMArCRI; 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=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229576AbiGUNZs (ORCPT + 99 others); Thu, 21 Jul 2022 09:25:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35260 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229469AbiGUNZq (ORCPT ); Thu, 21 Jul 2022 09:25:46 -0400 Received: from mail-qv1-xf30.google.com (mail-qv1-xf30.google.com [IPv6:2607:f8b0:4864:20::f30]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F3229B82 for ; Thu, 21 Jul 2022 06:25:44 -0700 (PDT) Received: by mail-qv1-xf30.google.com with SMTP id m10so1149780qvu.4 for ; Thu, 21 Jul 2022 06:25:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DGrBLaNIprWPnLASVzucMIdeH8IwcuTiWBUYmrgNEq4=; b=blMArCRIQqdXMvhhNuLcI+8rbpoj3mba+jisYAjiGNck3+Yrkpitf3sBSMLXU0MYu1 JnGMr7qaUuib3O0fPQMF23cjXCfaiwVbi8pH05GUO0+w3HJy0f70v+OYZCWvTWwruCT8 cbkbGErUBDDfm6CgzF82H+OS71moycWT9T1MrNyE6JMJin9EyL/oDIhMYC8VeTuAqsB7 8MOJpuVrOi6hrwjiCJA/evwd6WfNyNw6tVB7TdBfikLUxjzFRU02ArPAu7usZ3LWLAcG pD0qfxC8x7dPyqMwAfo1On3QDv2/kl81p3iLk1f2deY53RKZHwV26qUBXuOVQEAkIYrk EORw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DGrBLaNIprWPnLASVzucMIdeH8IwcuTiWBUYmrgNEq4=; b=GXY206TJidRpcHNLGj24r2cqXHef8LNcp3rgf9zqub0JmPOTCvbZ7XXCUsFlVJYHhy tWOeavQEtDFfyPbr2iX96IX4Zq9Y3OLa3uC1UsQBA9yPmjPdjlQjsSPHyMhiCIZwTapB 0JDbsq4b+rrKgDhRH733g9Wbl7AyVScS+seDGKjk5cpYuAx7kjzBs4uml5awPcyoU88l CX7K4tCY8Tyaolp7LnjWWFqlgPtGLuZakWo4mCNdQs9mKahFjnF7575KpiCDSc/MhGJN +5gdqz8pYl/ZAUVxDYIEkTkH0BnJm7zJd+Kvtp1iV8RyIv/6SyNRR1BMf4nhIRgsn7w9 8dWQ== X-Gm-Message-State: AJIora85cvwwx9Ce1hrPzPhjGlxAVZeuG3Rrd52tY6iASORKMSWVJrkf rc8ILBzcqUTDm3XU9FrqqsAV6JiqbCnxT5zZM1PRjg== X-Received: by 2002:ad4:5761:0:b0:473:7861:69d1 with SMTP id r1-20020ad45761000000b00473786169d1mr34026860qvx.73.1658409944065; Thu, 21 Jul 2022 06:25:44 -0700 (PDT) MIME-Version: 1.0 References: <1657038556-2231-1-git-send-email-quic_khsieh@quicinc.com> In-Reply-To: From: Dmitry Baryshkov Date: Thu, 21 Jul 2022 16:25:32 +0300 Message-ID: Subject: Re: [PATCH v16 0/3] eDP/DP Phy vdda realted function To: Johan Hovold Cc: Kuogee Hsieh , Douglas Anderson , Bjorn Andersson , Vinod Koul , Mark Brown , dri-devel@lists.freedesktop.org, robdclark@gmail.com, sean@poorly.run, swboyd@chromium.org, daniel@ffwll.ch, airlied@linux.ie, agross@kernel.org, quic_abhinavk@quicinc.com, quic_aravindh@quicinc.com, quic_sbillaka@quicinc.com, freedreno@lists.freedesktop.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, Liam Girdwood , Manivannan Sadhasivam , Rob Herring , Krzysztof Kozlowski Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=ham 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 On Thu, 21 Jul 2022 at 13:31, Johan Hovold wrote: > > On Tue, Jul 05, 2022 at 09:29:13AM -0700, Kuogee Hsieh wrote: > > 0) rebase on https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git tree > > 1) add regulator_set_load() to eDP phy > > 2) add regulator_set_load() to DP phy > > 3) remove vdda related function out of eDP/DP controller > > > > Kuogee Hsieh (3): > > phy: qcom-edp: add regulator_set_load to edp phy > > phy: qcom-qmp: add regulator_set_load to dp phy > > drm/msm/dp: delete vdda regulator related functions from eDP/DP > > controller > > > > drivers/gpu/drm/msm/dp/dp_parser.c | 14 ----- > > drivers/gpu/drm/msm/dp/dp_parser.h | 8 --- > > drivers/gpu/drm/msm/dp/dp_power.c | 95 +------------------------------ > > drivers/phy/qualcomm/phy-qcom-edp.c | 12 ++++ > > drivers/phy/qualcomm/phy-qcom-qmp-combo.c | 41 ++++++++++--- > > 5 files changed, 46 insertions(+), 124 deletions(-) > > This series breaks USB and PCIe for some SC8280XP and SA540P machines > where the DP PHY regulators are shared with other PHYs whose drivers do > not request a load. I'm trying to understand, why does this series cause the regression. Previously it would be the DP controller voting on the regulators load, now it has been moved to the DP/eDP PHYs. > Specifically, the hard-coded vdda-phy load of 21.8 mA added by this > series, causes several RPMh regulators to now be put in low-power mode. > > I found Doug's suggestion to handle situations like this in regulator > core: > > https://lore.kernel.org/all/20180814170617.100087-1-dianders@chromium.org/ > > but since that was rejected, how do we deal with this generally? > > In the above thread Doug mentioned adding support for load requests to > further drivers and Bjorn mentioned working around it by adding > regulator-system-load properties to DT. > > It seems quite likely that changes like this one affects other systems > too, and the effects may be hard to debug. So a more general solution > than playing whack-a-mole using DT would be good to have. I think enabling a regulator which supports set_load() and without load being set should cause a warning, at least with CONFIG_REGULATOR_DEBUG. WDYT? -- With best wishes Dmitry