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=-8.3 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_IN_DEF_DKIM_WL autolearn=no 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 5FC80C2D0EC for ; Thu, 26 Mar 2020 18:34:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 37A8920857 for ; Thu, 26 Mar 2020 18:34:22 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="D5KANnoU" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727719AbgCZSeV (ORCPT ); Thu, 26 Mar 2020 14:34:21 -0400 Received: from mail-oi1-f196.google.com ([209.85.167.196]:46510 "EHLO mail-oi1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727354AbgCZSeV (ORCPT ); Thu, 26 Mar 2020 14:34:21 -0400 Received: by mail-oi1-f196.google.com with SMTP id q204so6399158oia.13 for ; Thu, 26 Mar 2020 11:34:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zvcRbO8JiiH8TflCF3JYY64FRuv850T5VBR+zKWVaAo=; b=D5KANnoUgA813LQvHjIp5rAoPhY2gTJup4nP+xGLb5FNmM7+8RNwum/ue1O95T+xWb 5Ktbnl2iWEXVoCU3oOQg1rH6QozCfngfrmRO501JFNyUSHuo2dqvZagSkuCv/ZkCcdDy 9SNPpYOLAEHYsE4N1CYsv1lw2JsDmzr3bO5CAhprXa6CHmJ/wgf3TslEjhp5iWSPZbla 6EGwewp3bw3kVgK1ceZl6cCzyM58RIqxXE7Ece2gV1Bkyopg2Mdv5j42z6O1C0vGsEb+ xUlK8kqOpBq79qowMpVYE7dI2KBF+1Bmk+h2mEbeqaCTkXHdCSEol6R1AyJ6SpC3NLmt slKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zvcRbO8JiiH8TflCF3JYY64FRuv850T5VBR+zKWVaAo=; b=gyQmfztVmtmvakLVnE6OS+eCimeEs5OEfh3j7F6gbEQkN1vmylj7toS3hRtlAKW0AK OtjMz93Y004aejoY+Agryrte65Mw2S4vmP7q94stRGljI8Ajt+XSEyDTsjjxJlK4AkkE Z5y44eR4MjTb0rDao8oehT08TbirLwAs9L8gGC4OtRgpWGVrEA9pWUXF+tOQ033L6IcI pxOCIC1BZADqX2uHBo3/ThY70OqrNVt1IPqTCQ0CX8AXlsNEIO4NXUm87hDKwVoHd/5Y etF0A/r21DuD6eQ4G6PhWqD43BOeJHFal/FViK2M+GPJ+DQLLNjYul1Hu+eCk9FAX985 piSQ== X-Gm-Message-State: ANhLgQ2rDA4g2OZpkxHpj8rHyy/IYxJY6zxrSsRzORFVvYUBeKfvuL6g 1w/XSryJmBvGDHIIFScT5QlsuQTTTnMkV6AS4ukEtw== X-Google-Smtp-Source: ADFU+vuhr19j1Gh9BuMJvyrUH94cq/bHJXqm/DeIzQEZemccehjW6KDkcmRhHiQOfwXBWmMBVCeLo1LvtVagEPcJ2FU= X-Received: by 2002:aca:f541:: with SMTP id t62mr1218807oih.172.1585247660202; Thu, 26 Mar 2020 11:34:20 -0700 (PDT) MIME-Version: 1.0 References: <1584973502-14775-1-git-send-email-ppvk@codeaurora.org> In-Reply-To: From: Saravana Kannan Date: Thu, 26 Mar 2020 11:33:44 -0700 Message-ID: Subject: Re: [RFC v6 0/2] Add SDHC interconnect bandwidth scaling To: Rajendra Nayak Cc: Pradeep P V K , Bjorn Andersson , adrian.hunter@intel.com, Rob Herring , Ulf Hansson , asutoshd@codeaurora.org, stummala@codeaurora.org, sayalil@codeaurora.org, rampraka@codeaurora.org, vbadigan@codeaurora.org, Stephen Boyd , Georgi Djakov , mka@chromium.org, linux-mmc@vger.kernel.org, LKML , linux-arm-msm@vger.kernel.org, "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Andy Gross , linux-mmc-owner@vger.kernel.org, Viresh Kumar Content-Type: text/plain; charset="UTF-8" Sender: linux-arm-msm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On Thu, Mar 26, 2020 at 2:22 AM Rajendra Nayak wrote: > > Adding Viresh and Saravana, > > On 3/23/2020 7:55 PM, Pradeep P V K wrote: > > Add interconnect bandwidths for SDHC driver using OPP framework that > > is 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 > > [RFC] mmc: host: sdhci-msm: Use the interconnect API > > (https://lkml.org/lkml/2018/10/11/499) and > > > > [PATCH v6] Introduce Bandwidth OPPs for interconnects > > (https://lkml.org/lkml/2019/12/6/740) > > Pradeep, since your series seems to depend on the above proposed bw bindings, > can you post the DT changes for the platform that you are testing these > patches on? > > Please note that the above series is currently deadlocked [1][2] with no clear path > forward for now, so looking at how you plan to use this might throw some light onto > the requirements > > [1] https://lkml.org/lkml/2020/1/14/511 > [2] https://lkml.org/lkml/2020/3/20/106 Sorry, not deadlocked. Just kinda busy. For [1] I believe I agreed with Viresh later on. I'll respond to [2] soon. -Saravana > > > > > Pradeep P V K (2): > > mmc: sdhci-msm: Add interconnect bus bandwidth scaling support > > dt-bindings: mmc: sdhci-msm: Add interconnect BW scaling strings > > > > .../devicetree/bindings/mmc/sdhci-msm.txt | 18 ++ > > drivers/mmc/host/sdhci-msm.c | 240 ++++++++++++++++++++- > > 2 files changed, 254 insertions(+), 4 deletions(-) > > > > -- > QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member > of Code Aurora Forum, hosted by The Linux Foundation