Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp547425pxa; Wed, 12 Aug 2020 08:16:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzfRvg8p3+F/vQ0KhsLnx7U5f3Lwd0S3HSLYTLDeueaBgcZUWoKw74Beh6jPo0197/Lj2XK X-Received: by 2002:a17:906:bcc4:: with SMTP id lw4mr224632ejb.361.1597245382061; Wed, 12 Aug 2020 08:16:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1597245382; cv=none; d=google.com; s=arc-20160816; b=Z95UMvVVeAJXwKCv89yOdb5hXAvRdh2WBsqYHbsR1eU+1fi2JFTd55ruQ8i71xGUcp N5HsHpKWcyMm298cWPRInB5HBBBQs4UKZD6QJYBaueP/2IxF4qYaLF4odlMqlHtljCwN o30QB2i8Thk9CyozWXjZnAdVNzuXAQaQbPYMeGZzCAT++M8iab30Tt/ZaQpXsleNFaV/ ElDMr+5sof0XBhLXIt+SN8rAsf8rft9CAwxT8+S5e2hD4HHxGGk1MP8cNuTBeRHXvMFZ nsvg9GThdtIXTKTqj6rHgF81EuOMRqVnOzCdJ1BPvym0WQOJiSsL1RZ9cZln53gRo/4q M5Jw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=rhn3sqAjMO7fHW50VMJNtuaUppNZfZWxCntk8JftCgQ=; b=Zs8R9eZWlRwLd+SDtRzyMhDOucJUeJZZ+MI1gtFdOXm2r1PNuuNdLqQAtFf513CysX Oa/vIzAtwPigtw5qgRuMw+O62on0+xrqJbnkCMqs3pmb6OVxJhlJgexh2Zmrg1K7/Qg4 DCmPK1Os4E0UAjz8h/L0C199lwjZVKflqs4XKjksu0WMUQC4HRwKXICSjCr+3ZvGWyeJ LyAAg1lssEmRbdDcqo2KL8IOhDb0tXJ0mvz7iKe/hoa7sqUIaqmm35HQJtfaXrbQPRVm hI9AR4ECVx6xB3GDNYuF7Ik7j6lNLdekJdXdbhaXpLCQbo0A/TG7BNWdPv1f9Xo2hg3k 9/ZA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b="RRZmS/K4"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s18si1397737ejr.190.2020.08.12.08.15.58; Wed, 12 Aug 2020 08:16:22 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b="RRZmS/K4"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S1726547AbgHLPPU (ORCPT + 99 others); Wed, 12 Aug 2020 11:15:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53576 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726489AbgHLPPT (ORCPT ); Wed, 12 Aug 2020 11:15:19 -0400 Received: from mail-pf1-x442.google.com (mail-pf1-x442.google.com [IPv6:2607:f8b0:4864:20::442]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1EC00C061383 for ; Wed, 12 Aug 2020 08:15:19 -0700 (PDT) Received: by mail-pf1-x442.google.com with SMTP id m8so1187008pfh.3 for ; Wed, 12 Aug 2020 08:15:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=rhn3sqAjMO7fHW50VMJNtuaUppNZfZWxCntk8JftCgQ=; b=RRZmS/K4r4bVHEUwf8n+9+7Ir4gT7POq7veOwiR/I9olsAHAhQKduUFHS1xvULIqMQ QYZYafxj5Yph4zoWUZjHGyki2EPuKQx7c7Lgn59Rqg+qdkOgqjx1z61Kg1yKQCJIZhSV B8NNy7735o8SLwnR4TEt8i/O05/V4RpgsJlOk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=rhn3sqAjMO7fHW50VMJNtuaUppNZfZWxCntk8JftCgQ=; b=Iw7nSsDVQNOW9D/h7EUMSsGrvanUxfg0io4yroFqGA2zTiIiQQcPtcAIDSp7gY9C2B 8ltcN/EAJUxbWPz2eiX4sSiwgFGTmupzvHg4/8zRRiAyoyx/PUOhEf3ChhG7zhwx3qVP yJIqdTATLhxu7rq0fs/57CCk6nBlEnW3j9Q/E92sDszIZs/iiVcEXrscbnHAz/zrEM+Z 02iXFZZwr+IvhR/q0PA6ZzkPzdvhBN4EwPD1vJURZQ+SQZgUVFBA2qYNMxJsOzq0zL9F PEoLzfgiJxMhg5bUke8GLnClU+tGdLetdnYGo0kfTr+jhpAr135+b8BiVJgTLBXsP8XI 1ixw== X-Gm-Message-State: AOAM5339YBzsBx0oJEatMgPCAe0ZyMiwkFF5f4joRpzDMHo4nu3VMVJM g8f2iWVD2YzjyVP3DVcN+y35sQ== X-Received: by 2002:aa7:93a6:: with SMTP id x6mr30835pff.37.1597245318477; Wed, 12 Aug 2020 08:15:18 -0700 (PDT) Received: from localhost ([2620:15c:202:1:f693:9fff:fef4:e70a]) by smtp.gmail.com with ESMTPSA id h18sm2825713pfo.21.2020.08.12.08.15.16 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 12 Aug 2020 08:15:17 -0700 (PDT) Date: Wed, 12 Aug 2020 08:15:16 -0700 From: Matthias Kaehlcke To: sbhanu@codeaurora.org Cc: adrian.hunter@intel.com, ulf.hansson@linaro.org, robh+dt@kernel.org, linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, agross@kernel.org, bjorn.andersson@linaro.org, rnayak@codeaurora.org, Pradeep P V K , devicetree-owner@vger.kernel.org Subject: Re: [PATCH V2] arm64: dts: qcom: sc7180: Add bandwidth votes for eMMC and SDcard Message-ID: <20200812151516.GA2995789@google.com> References: <1595328381-29552-1-git-send-email-sbhanu@codeaurora.org> <20200724171018.GZ3191083@google.com> <7ffcb56e9e6723f4bae687e0f491cb93@codeaurora.org> <20200727191029.GA3191083@google.com> <20200811170855.GK3191083@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 12, 2020 at 04:26:08PM +0530, sbhanu@codeaurora.org wrote: > On 2020-08-11 22:38, Matthias Kaehlcke wrote: > > On Tue, Jul 28, 2020 at 04:49:05PM +0530, sbhanu@codeaurora.org wrote: > > > On 2020-07-28 00:40, Matthias Kaehlcke wrote: > > > > Hi, > > > > > > > > On Mon, Jul 27, 2020 at 12:20:38PM +0530, sbhanu@codeaurora.org wrote: > > > > > On 2020-07-24 22:40, Matthias Kaehlcke wrote: > > > > > > Hi Shaik, > > > > > > > > > > > > On Tue, Jul 21, 2020 at 04:16:21PM +0530, Shaik Sajida Bhanu wrote: > > > > > > > From: Pradeep P V K > > > > > > > > > > > > > > Add the bandwidth domain supporting performance state and > > > > > > > the corresponding OPP tables for the sdhc device on sc7180. > > > > > > > > > > > > > > Signed-off-by: Pradeep P V K > > > > > > > Signed-off-by: Shaik Sajida Bhanu > > > > > > > --- > > > > > > > > > > > > > > Changes since V1: > > > > > > > - Incorporated review comments by Bjorn Andersson. > > > > > > > --- > > > > > > > arch/arm64/boot/dts/qcom/sc7180.dtsi | 15 +++++++++++++++ > > > > > > > 1 file changed, 15 insertions(+) > > > > > > > > > > > > > > diff --git a/arch/arm64/boot/dts/qcom/sc7180.dtsi > > > > > > > b/arch/arm64/boot/dts/qcom/sc7180.dtsi > > > > > > > index 68f9894..d78a066 100644 > > > > > > > --- a/arch/arm64/boot/dts/qcom/sc7180.dtsi > > > > > > > +++ b/arch/arm64/boot/dts/qcom/sc7180.dtsi > > > > > > > @@ -684,6 +684,9 @@ > > > > > > > clocks = <&gcc GCC_SDCC1_APPS_CLK>, > > > > > > > <&gcc GCC_SDCC1_AHB_CLK>; > > > > > > > clock-names = "core", "iface"; > > > > > > > + interconnects = <&aggre1_noc MASTER_EMMC &mc_virt SLAVE_EBI1>, > > > > > > > + <&gem_noc MASTER_APPSS_PROC &config_noc SLAVE_EMMC_CFG>; > > > > > > > + interconnect-names = "sdhc-ddr","cpu-sdhc"; > > > > > > > power-domains = <&rpmhpd SC7180_CX>; > > > > > > > operating-points-v2 = <&sdhc1_opp_table>; > > > > > > > > > > > > > > @@ -704,11 +707,15 @@ > > > > > > > opp-100000000 { > > > > > > > opp-hz = /bits/ 64 <100000000>; > > > > > > > required-opps = <&rpmhpd_opp_low_svs>; > > > > > > > + opp-peak-kBps = <100000 100000>; > > > > > > > + opp-avg-kBps = <100000 50000>; > > > > > > > }; > > > > > > > > > > > > > > opp-384000000 { > > > > > > > opp-hz = /bits/ 64 <384000000>; > > > > > > > required-opps = <&rpmhpd_opp_svs_l1>; > > > > > > > + opp-peak-kBps = <600000 900000>; > > > > > > > + opp-avg-kBps = <261438 300000>; > > > > > > > }; > > > > > > > }; > > > > > > > }; > > > > > > > @@ -2476,6 +2483,10 @@ > > > > > > > clocks = <&gcc GCC_SDCC2_APPS_CLK>, > > > > > > > <&gcc GCC_SDCC2_AHB_CLK>; > > > > > > > clock-names = "core", "iface"; > > > > > > > + > > > > > > > + interconnects = <&aggre1_noc MASTER_SDCC_2 &mc_virt SLAVE_EBI1>, > > > > > > > + <&gem_noc MASTER_APPSS_PROC &config_noc SLAVE_SDCC_2>; > > > > > > > + interconnect-names = "sdhc-ddr","cpu-sdhc"; > > > > > > > power-domains = <&rpmhpd SC7180_CX>; > > > > > > > operating-points-v2 = <&sdhc2_opp_table>; > > > > > > > > > > > > > > @@ -2489,11 +2500,15 @@ > > > > > > > opp-100000000 { > > > > > > > opp-hz = /bits/ 64 <100000000>; > > > > > > > required-opps = <&rpmhpd_opp_low_svs>; > > > > > > > + opp-peak-kBps = <160000 100000>; > > > > > > > + opp-avg-kBps = <80000 50000>; > > > > > > > }; > > > > > > > > > > > > > > opp-202000000 { > > > > > > > opp-hz = /bits/ 64 <202000000>; > > > > > > > required-opps = <&rpmhpd_opp_svs_l1>; > > > > > > > + opp-peak-kBps = <200000 120000>; > > > > > > > + opp-avg-kBps = <100000 60000>; > > > > > > > }; > > > > > > > }; > > > > > > > }; > > > > > > > > > > > > Does the sdhci-msm driver actually have BW scaling support at this > > > > > > point? > > > > > > > > > > > > > > > > yes > > > > > > > > > > > There is commit 4ece9795be56 ("mmc: sdhci-msm: Add interconnect > > > > > > bandwidth scaling support"), whose commit message says "make sure > > > > > > interconnect driver is ready before handling interconnect scaling.". > > > > > > > > > > > > I haven't seen any patch adding the scaling support (supposedly by > > > > > > adding dev_pm_opp_set_bw() calls?). Did I miss it? If not it seems > > > > > > it would make sense to post it in a series together with this patch, > > > > > > as far as I can tell this patch alone does nothing in practical terms. > > > > > > > > > > > > grep sdhc /sys/kernel/debug/interconnect/interconnect_summary > > > > > > 8804000.sdhci 0 0 0 > > > > > > 7c4000.sdhci 0 0 0 > > > > > > 7c4000.sdhci 0 0 0 > > > > > > 8804000.sdhci 0 0 0 > > > > > > ... > > > > > > > > > > "mmc: sdhci-msm: Use OPP API to set clk/perf > > > > > state"(https://lkml.org/lkml/2020/4/8/425) and "mmc: sdhci-msm: Add > > > > > interconnect bandwidth scaling > > > > > support"(https://lkml.org/lkml/2020/3/12/60) > > > > > with these two patches scaling will be supported for sdhci-msm driver. > > > > > > > > Are you testing with exactly these patches or with the ones that landed > > > > upstream? At least the second one changed substantially > > > > > > > > > the values in grep sdhc > > > > > /sys/kernel/debug/interconnect/interconnect_summary will be zero > > > > > during > > > > > device is in suspend state... > > > > > > > > Yes, I forgot to mention that I started MMC IO before looking at > > > > 'interconnect_summary'. > > > > > > > > > and the values in grep sdhc > > > > > /sys/kernel/debug/interconnect/interconnect_summary during device in > > > > > resume > > > > > state will be like the following:: > > > > > > > > > > cicalhost / # cat > > > > > /sys/kernel/debug/interconnect/interconnect_summary | grep > > > > > sdh > > > > > 8804000.sdhci 0 60000 120000 > > > > > 7c4000.sdhci 0 300000 900000 > > > > > 7c4000.sdhci 0 300000 900000 > > > > > 8804000.sdhci 0 60000 120000 > > > > > 8804000.sdhci 0 100000 200000 > > > > > 7c4000.sdhci 0 261438 600000 > > > > > 8804000.sdhci 0 60000 120000 > > > > > > > > On my system the bandwidth is never set: > > > > > > > > 3.590152] sdhci_msm 7c4000.sdhci: DBG: old/new frequencies (384000000 > > > > Hz) are same, nothing to do > > > > https://elixir.bootlin.com/linux/v5.7.8/source/drivers/opp/core.c#L847 > > > > > > > > This happens every time, even after the bandwith is set to 0. The > > > > problem > > > > seems to be that opp_table->clk doesn't change for target_freq = 0. > > > > > > > > My system is based on v5.4, so it is possible that my kernel is missing > > > > some > > > > relevant patch from upstream. > > > Hi matthias, > > > > > > In order to aviod confusion this patch is continuation of the below > > > patch:: > > > "mmc: sdhci-msm: Add interconnect bandwidth scaling support" > > > (https://lkml.org/lkml/2020/6/9/160). > > > > My kernel contains this patch. > > > > As you told me in private, the patch "opp: Fix dev_pm_opp_set_rate() > > to not return early" (https://patchwork.kernel.org/patch/11707003/) is > > needed, which fixes exactly the problem I described. > > > > It seems the tree you tested was not based on the maintainer tree or > > upstream, > > please make that clear when someone reports issues. Since you said it > > works > > for you I wasted time trying to chase down a missing patch which did not > > exist > > (yet). > > > Hi Matthis, > > Can you confirm from your end the issue that you reported got fixed > with Rajendra patch or not. Once you confirm, I can ask Bjorn to pull > this dt change. Yes, the issue is fixed with Rajendra's patch Tested-by: Matthias Kaehlcke