Received: by 2002:ac0:a874:0:0:0:0:0 with SMTP id c49csp583158ima; Fri, 15 Mar 2019 09:19:25 -0700 (PDT) X-Google-Smtp-Source: APXvYqyY0sEXXYwKeLEU6zkQmz25I0V4nrFSwXx+Z36P0njjb1+ZcucJWp8i5Zz08qJkQIOScRT0 X-Received: by 2002:a65:4547:: with SMTP id x7mr4136200pgr.350.1552666764906; Fri, 15 Mar 2019 09:19:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552666764; cv=none; d=google.com; s=arc-20160816; b=ng9xh0UrMXZTxiI3ImqOyQqrL66afVShXXmHEzWh1yKScV74pDYSHVMj43GYAIAIOh HfFv37TAXsAK8cMG3XXPcAHCGSVy/b/RutOR9iPprG9AJ6bdfoftnIgxLTUOq5Dzs+PO 5PnKIn+v++g1UOXdTOxcQzYGR7q26yd3ayF1z28YzdtXKDzr6gUFgu4lH7oUX8iPyMrA REoknJ3VjGIaJPqIhXwGxFBZobyfe2VzwoyovBLVwHE6g9XaP72y2ia+kUMZSNpgvCzc /dvBhWudr2s7WFp0peEukBh04500karFZZqiWa4ldL1ipTi969mFTOlW2b3qsenT49zm dsLQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=yUGJ75OmBZQm5OTwyXIACWB5EDYwvdGF1+g28FmmE5U=; b=GEb6lebmHxz3uet5VCfTK87ESa0WDqi1+1t/VriDrNwAVzYQ2lr+sIkRC7GdGGksH8 U4EkwwXSz7WQx1TLJXWPGVPKhuu9rrEvV0++hYYT0Bgy0RRbc8WqnYbtmBAkkFIfy+Fc 5ZyHo/CFa/Nz06ExPUJpqsch1UbzgsUC3SBWoNhNRgX/gmaaMYfa+4gkMu00T63boGu2 AWp1Wi4e9t1+tz9R0u+X4heqrUkR3CRK7FWIKH8E7GnnO44zF2hoAXfpp74Oisopb58R KbMBhQyFw57wkSF5H83Wp5i+87MzGr6sJwcfKRRnX4eaCufRNIpWdu3BroG4OehXTo4s YyJA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20150623.gappssmtp.com header.s=20150623 header.b=gjo1O64T; 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 n62si2251904pfi.57.2019.03.15.09.19.08; Fri, 15 Mar 2019 09:19:24 -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=@baylibre-com.20150623.gappssmtp.com header.s=20150623 header.b=gjo1O64T; 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 S1729529AbfCOQSO (ORCPT + 99 others); Fri, 15 Mar 2019 12:18:14 -0400 Received: from mail-lf1-f68.google.com ([209.85.167.68]:46854 "EHLO mail-lf1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726632AbfCOQSN (ORCPT ); Fri, 15 Mar 2019 12:18:13 -0400 Received: by mail-lf1-f68.google.com with SMTP id a132so5846501lfa.13 for ; Fri, 15 Mar 2019 09:18:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yUGJ75OmBZQm5OTwyXIACWB5EDYwvdGF1+g28FmmE5U=; b=gjo1O64TSZq7jpmOv0+3khF3F/O+txIJMfgDOrKmzAQ8AGAuuUj9FSSRPWcwZjsqZF tFe2cmnqP7lx66qYP+gWKMmtfH6s0fIyCeMqx9i/S9xIDUzQDUphmUcvzDCgvLR1pEuF gN/HWl5PVZ0FBTIBpkNB2mZ5ClfnZ2gJoSA6MYERqJ7zgcFpJ2/YDoAGrndTtHmtWyWo 91RxajFnncP9vzPZb20kfxx3bsykFuQRfsFqQOXxm9/fL+b9yZYcvhyEPlmOppNaHEcW fjCTEQOV02e0my0QS2E9nR1scryCJ7XesL4NlHhW1G9GHGhjZFp5XJqFX1TPCDaDQ2XO VEZw== 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=yUGJ75OmBZQm5OTwyXIACWB5EDYwvdGF1+g28FmmE5U=; b=t/hywLiU1jh7XoXqELxOS899oWCBBf3d5upJsj6n49TXQCEREF0BrkJrnp2YSZAe+D d+WLN2uN3gZuIFrpK6wbKUMFlwsIPUgRun5+PoxmGrP6nMG/8n1plEBffq+7cym+XeCV eRfD7MOEplO0/3151Si1B/BjNq/Flx5eEapESpgJMAczkxjWAGpV2Zw98VoFJhCrr7u0 +6UmQc3zRCbpIfuOWIe+YccZNIekNIhBeCvx+0LVDljfpCAbn9EuEgyFxbdW1elffEVh AsNgA6gtXl17fik4g9e0OM/t0sxB2IjEVxhSARjpKV4xI67uEiono4m/1vPdEYrt9p3c Py1w== X-Gm-Message-State: APjAAAV5Bac4ZCJtrzT+xrx/7HDFf91pgfdpwki36hWIfFEUJksA5N+P Z1MWZchWnTAi0erUzsl3AAv5gr4wSM1yMuXNhhOuSA== X-Received: by 2002:ac2:4343:: with SMTP id o3mr2390773lfl.129.1552666691178; Fri, 15 Mar 2019 09:18:11 -0700 (PDT) MIME-Version: 1.0 References: <20190313193408.23740-1-abailon@baylibre.com> In-Reply-To: <20190313193408.23740-1-abailon@baylibre.com> From: Michael Turquette Date: Fri, 15 Mar 2019 09:17:44 -0700 Message-ID: Subject: Re: [RFC PATCH 0/3] Add support of busfreq To: Alexandre Bailon Cc: Linux PM list , Georgi Djakov , Patrick Titiano , Linux Kernel Mailing List , "Stephen Boyd , Emilio Lopez , Hans de Goede , linux-clk , linux-arm-kernel" , Zening Wang , Dong Aisheng , Kevin Hilman , Carlo Caione Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Alex, Some nitpick review comments below. On Wed, Mar 13, 2019 at 12:33 PM Alexandre Bailon wrote: > > This series implements busfreq, a framework used in MXP's s/MXP/NXP/ > tree to scale the interconnect and dram frequencies. > In the vendor tree, device's driver request for a > performance level, which is used to scale the frequencies. > This series implements it using the interconnect framework. > Devices' driver request for bandwidth which is use by busfreq > to determine a performance level, and then scale the frequency. > > Busfreq is quite generic. It could be used for any i.MX SoC. > A busfreq platform driver just have to define a list of > interconnect nodes, and some OPPs. > > This series is sent as RFC mostly because the current support > of i.MX SoC won't benefit of busfreq framework, because the > clocks' driver don't support interconnect / dram frequency > scaling. In your v2 cover letter could you post a link to a git branch that has everything integrated that is needed to test the series? I guess this is similar to what Aisheng asked for already. > As exemple, this series implements busfreq for i.MX8MM whose > upstreaming is in progress. Because this relies on ATF to > do the frequency scaling, it won't be hard make it work. It's not clear to me whether this series actual scales the dram frequency based on what you said above. Is it just theoretical or do you have it working with a pile of out-of-tree patches? Would be good to include that pile of patches in your integration branch that I suggested above. Thanks, Mike > > As exemple, this series implements busfreq for > Alexandre Bailon (3): > drivers: interconnect: Add a driver for i.MX SoC > drivers: interconnect: imx: Add support of i.MX8MM > dt-bindings: interconnect: Document fsl,busfreq-imx8mm bindings > > .../bindings/interconnect/imx8mm.txt | 24 + > drivers/interconnect/Kconfig | 1 + > drivers/interconnect/Makefile | 1 + > drivers/interconnect/imx/Kconfig | 17 + > drivers/interconnect/imx/Makefile | 2 + > drivers/interconnect/imx/busfreq-imx8mm.c | 132 ++++ > drivers/interconnect/imx/busfreq.c | 570 ++++++++++++++++++ > drivers/interconnect/imx/busfreq.h | 123 ++++ > include/dt-bindings/interconnect/imx8mm.h | 37 ++ > 9 files changed, 907 insertions(+) > create mode 100644 Documentation/devicetree/bindings/interconnect/imx8mm.txt > create mode 100644 drivers/interconnect/imx/Kconfig > create mode 100644 drivers/interconnect/imx/Makefile > create mode 100644 drivers/interconnect/imx/busfreq-imx8mm.c > create mode 100644 drivers/interconnect/imx/busfreq.c > create mode 100644 drivers/interconnect/imx/busfreq.h > create mode 100644 include/dt-bindings/interconnect/imx8mm.h > > -- > 2.19.2 -- Michael Turquette CEO BayLibre - At the Heart of Embedded Linux http://baylibre.com/ Schedule a meeting: https://calendly.com/mturquette