From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.8 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4F04AC433DF for ; Wed, 12 Aug 2020 10:58:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 10975208E4 for ; Wed, 12 Aug 2020 10:58:15 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=mg.codeaurora.org header.i=@mg.codeaurora.org header.b="TTAvbWvs" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726871AbgHLK5o (ORCPT ); Wed, 12 Aug 2020 06:57:44 -0400 Received: from mail29.static.mailgun.info ([104.130.122.29]:15323 "EHLO mail29.static.mailgun.info" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727814AbgHLK4a (ORCPT ); Wed, 12 Aug 2020 06:56:30 -0400 DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=mg.codeaurora.org; q=dns/txt; s=smtp; t=1597229778; h=Message-ID: References: In-Reply-To: Subject: Cc: To: From: Date: Content-Transfer-Encoding: Content-Type: MIME-Version: Sender; bh=+/GcN/uLcX86TA26NdQtGXl4jyQxmPmf10bKOB3HJrc=; b=TTAvbWvsFD6gwJSnpsacUDS0R5nfqhcEhri8NYznvM5Xd8zjdV/LGd78LEb32JlWkd+CpshZ B7zf7IWPIa4PlYaiv049P3bAt1KkRd7E6NFbT5RPWBTXcpXRirr/hoxs9wSixg3IUueDkgW3 JyBjQl2KhKWCUSlZ8inLU0Jlojk= X-Mailgun-Sending-Ip: 104.130.122.29 X-Mailgun-Sid: WyJiYTcxMiIsICJsaW51eC1tbWNAdmdlci5rZXJuZWwub3JnIiwgImJlOWU0YSJd Received: from smtp.codeaurora.org (ec2-35-166-182-171.us-west-2.compute.amazonaws.com [35.166.182.171]) by smtp-out-n13.prod.us-west-2.postgun.com with SMTP id 5f33caca668ab3fef65a655b (version=TLS1.2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256); Wed, 12 Aug 2020 10:56:10 GMT Received: by smtp.codeaurora.org (Postfix, from userid 1001) id 55698C433CB; Wed, 12 Aug 2020 10:56:10 +0000 (UTC) Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: sbhanu) by smtp.codeaurora.org (Postfix) with ESMTPSA id 0D774C433C9; Wed, 12 Aug 2020 10:56:09 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 12 Aug 2020 16:26:08 +0530 From: sbhanu@codeaurora.org To: Matthias Kaehlcke 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 In-Reply-To: <20200811170855.GK3191083@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> Message-ID: X-Sender: sbhanu@codeaurora.org User-Agent: Roundcube Webmail/1.3.9 Sender: linux-mmc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-mmc@vger.kernel.org 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. thanks, sajida