Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp1792569ybn; Thu, 26 Sep 2019 02:14:52 -0700 (PDT) X-Google-Smtp-Source: APXvYqxb9zVYQkwz6qB22jnCjCu5Fh+buqUmCNKc4omFnRzt0ni/FZNiH0KynHD223akcVXd3pi+ X-Received: by 2002:a50:d084:: with SMTP id v4mr2476043edd.48.1569489292867; Thu, 26 Sep 2019 02:14:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569489292; cv=none; d=google.com; s=arc-20160816; b=oQYikCY/2xc+NG35/B9LUM1PIH99VGBaUfHYrJPaq5j/rFzioVkN6ekS76MeEl4d+F FDzLmiBfnQvXgwl8f66E1Z1vEuziwRipMjQZWSkTzvffL7VSO9ZE3s2JBqdDrwBZdcXD EjzPV3hJRFDN/DH7Nvi64Q+VQYZ2INquOKAPSKDq0oD4M3a/ZUsGyoXBwK8wMuXDqXVw HDljc57Vb+T6Xv5YOa0Ys5knFwwlDQ/FIQd+ZA1DqFSH85mKch+FZxBthwWGs+CbPxuO ygBfF3anm1R8hwZXiUYmdI+jMQMypuXy9ijRRw04s/oXWe0QSG1CWWvS9K0YInnMLPEb SYoA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:message-id:references :in-reply-to:subject:cc:to:from:date:content-transfer-encoding :mime-version:dkim-signature:dkim-signature; bh=yDfZMhE92LEXf1Mi1a9fwXIM2vFvidI2977eY3XQ2DI=; b=hsE03WPk+WTYf5oA04S4I4biI4Hu2pmT98hSqzsjAVfixZnRkdhxQ3dG216I4oyV1A uMFDEPkYhengHczNzfxnoQ68SBhAxEgc49x5OG3vaWgjzMgIP0WvLGSkWFXBarS/wBAb SiAVmUgu/Bc03WRk2pac1c/C9u8z9fdsbw7M6Lh2G1PpeU1PzCKVZjHQazffZ5meV/P1 pplMmjRgxNlZFddmoFHsiSwXO9gigp24w6lDulu3ON5QlC44qkQGUFEZwj1uHrF1qWpS dTlQnf6Kmg7KAP4m5rEPb88ZfxoiHkAIVF/nEHr9H68neiIdssmSqSfP5Vr0Je65+31k CipQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=ogaMPrR+; dkim=pass header.i=@codeaurora.org header.s=default header.b=ogaMPrR+; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t26si934111edd.184.2019.09.26.02.14.29; Thu, 26 Sep 2019 02:14:52 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=ogaMPrR+; dkim=pass header.i=@codeaurora.org header.s=default header.b=ogaMPrR+; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2442260AbfIYGYN (ORCPT + 99 others); Wed, 25 Sep 2019 02:24:13 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:45338 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404570AbfIYGYN (ORCPT ); Wed, 25 Sep 2019 02:24:13 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id EA4E861197; Wed, 25 Sep 2019 06:24:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1569392651; bh=efyvQV7q7fIN6ZkOeoxT6VazF4LiJT3OJPSTTXRZbJQ=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=ogaMPrR+nmcQbEvlzytpjir1Xy/qKVqEGmn5ROTxTq8C81BvoSE7POnTLXwIKgBgj tx2zGwFW0ps/spY586xrdcflVRQUGMzPTX2cpk44BPmodH+EHNAYbeknxeheXjecJd 8sVlaO1xL6gSyL71OJWFVeW4BymdvSCHhuuWwUg0= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_INVALID,DKIM_SIGNED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.codeaurora.org (Postfix) with ESMTP id 3292560128; Wed, 25 Sep 2019 06:24:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1569392651; bh=efyvQV7q7fIN6ZkOeoxT6VazF4LiJT3OJPSTTXRZbJQ=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=ogaMPrR+nmcQbEvlzytpjir1Xy/qKVqEGmn5ROTxTq8C81BvoSE7POnTLXwIKgBgj tx2zGwFW0ps/spY586xrdcflVRQUGMzPTX2cpk44BPmodH+EHNAYbeknxeheXjecJd 8sVlaO1xL6gSyL71OJWFVeW4BymdvSCHhuuWwUg0= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 25 Sep 2019 11:54:11 +0530 From: ppvk@codeaurora.org To: Georgi Djakov Cc: adrian.hunter@intel.com, ulf.hansson@linaro.org, robh+dt@kernel.org, asutoshd@codeaurora.org, vbadigan@codeaurora.org, stummala@codeaurora.org, sayalil@codeaurora.org, rampraka@codeaurora.org, linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, Subhash Jadavani , Andy Gross , linux-mmc-owner@vger.kernel.org Subject: Re: [RFC 1/2] mmc: sdhci-msm: Add support for bus bandwidth voting In-Reply-To: <616c7a8c-a1cf-2043-4ea4-f452ee90f083@linaro.org> References: <1567774037-2344-1-git-send-email-ppvk@codeaurora.org> <1567774037-2344-2-git-send-email-ppvk@codeaurora.org> <616c7a8c-a1cf-2043-4ea4-f452ee90f083@linaro.org> Message-ID: X-Sender: ppvk@codeaurora.org User-Agent: Roundcube Webmail/1.2.5 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019-09-12 18:26, Georgi Djakov wrote: > Hi Pradeep, > > Thanks for the patch! > > On 9/6/19 15:47, Pradeep P V K wrote: >> Vote for the MSM bus bandwidth required by SDHC driver >> based on the clock frequency and bus width of the card. >> Otherwise,the system clocks may run at minimum clock speed >> and thus affecting the performance. >> >> This change is based on Georgi Djakov [RFC] >> (https://lkml.org/lkml/2018/10/11/499) > > I am just wondering whether do we really need to predefine the > bandwidth values > in DT? Can't we use the computations from the above patch or is there > any > problem with that approach? > > Thanks, > Georgi Hi Georgi, By using the direct required bandwidth(bw / 1000) values, it will not guarantee that all the NOC clocks are running in the same voltage corner as required, which is very crucial for power concern devices like Mobiles etc. Also, it will not guarantee that the value passed is in proper Clock Plans domain there by effecting the requested Bandwidth. I think, you already aware of these consequences on using direct bandwidth values for RPMh based devices. The value the we passed in DT will make sure that all the NOC clocks between the end points are running in the same voltage corners as required and also it will guarantee that the requested BW's for the clients are obtained. Hence the reason for passing the predefined bandwidth values in DT. Thanks and Regards, Pradeep