Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp749902iob; Wed, 18 May 2022 12:05:31 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzLIcNPFBk4AmlgqFBIX4t/GBL4NXOttnxWkEerIf0ivDnSNGWhBqOBOISGtv/Nf+1GYZZR X-Received: by 2002:a63:1e55:0:b0:3db:84c2:8b2c with SMTP id p21-20020a631e55000000b003db84c28b2cmr746120pgm.546.1652900731174; Wed, 18 May 2022 12:05:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652900731; cv=none; d=google.com; s=arc-20160816; b=d1M7rA3GOun2CKn/AQ+iAWDgTj76agyc33oCZ7PE/8RtA1qmavEuCJZWdVg4RUFTQG VNtZHsEOlFlC0pjFjqx7gnCgXD1UTAQMuvx6yYLCl8VhTpKYmhRDsbf5jh8oThNm3XBu pOkmkZ3XzjLKh3g/GisDFpcMqIE5177ppie2LMWLXJwWbLjQCeFEN7ZWrA3REVxic5zl oY0J/9IyF6V/E+X29MBFqluDiw7zVEov6H/EJ5YjgXSMUFJEinPb7aO21M9N6KQgA2H4 G9kt4bfCkthRsFdymVNus/oMgW83nWlOMFhr9ILOp8sE2WFgjG2pbTBYQKim2dnSGXPL jfqw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version; bh=QRP/znsW6twON92OkuCxDQka0yD+6IG0hBq5yN5qSP0=; b=NgJbthfSpZt79Od8Ih0BPkozZNUDiLx0shl3AjTr285VfdMXW8WO+6GIQkqj6XNWEc Q61Qjj2s61si4YPYntS4V+6kEz40bxvA7Npl4KRTZWuRyL7Ly/wlqSSBwTjoawg+Tt4Y mb505AAX57tXSD4ZTUl+e+Mv5LN+ZEUEOkoaDq6gYVzdFBRkS2OnZurqshn1z5ft+G2B uyVe9wBfApk+YalmmUpRKFQsYJGHPtR5C/GFdnrfmJZJ6czrrpVAHJ+w1YmDL2jp59Gm F1w4prdgSX+WwzQxEODMDmknM8MPusdqVyhATkzBChQs+Z3q+k2m92z8b1iqQg3DGThY NfpA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id z10-20020a63e10a000000b003ab238a2af3si3624637pgh.134.2022.05.18.12.05.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 18 May 2022 12:05:31 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id CF6DC218FF2; Wed, 18 May 2022 12:04:39 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241730AbiERTEd (ORCPT + 99 others); Wed, 18 May 2022 15:04:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40074 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241721AbiERTEc (ORCPT ); Wed, 18 May 2022 15:04:32 -0400 Received: from mail-yw1-f177.google.com (mail-yw1-f177.google.com [209.85.128.177]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7575B20EE27; Wed, 18 May 2022 12:04:29 -0700 (PDT) Received: by mail-yw1-f177.google.com with SMTP id 00721157ae682-2fefb051547so34864037b3.5; Wed, 18 May 2022 12:04:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QRP/znsW6twON92OkuCxDQka0yD+6IG0hBq5yN5qSP0=; b=EbQp6tEvYlRFvrx2KtPg/OgRf2EePPZtbNWZLJDvPnTI9zZeS3sJnavNWnAtOTSEF/ Ja+YIIj0RjXBU3Gjw0LHAMqDpip+xv0sBRV+d3VbHS0vVAyDY7KnOis+0cUMmIgQkANq atRg8WW/bMx7Pa8C+1PYogqCvQQ3ITSM2ECuv5gdKAHGtdNwHhyCLh8sDmMB1K7annyB D5/3O6F/0Bi/nc06C0lNSR/+CIqfbOj8nW63zeXoCh4Wg4KM5T9PZBVjGVtwdXTVizZo xg9gaeVTlP8vlUvMNyPexS7lF38V5hk18aiDMi+msvJGoykgW0Q+aXZDE9itmUO+gbjX qVNQ== X-Gm-Message-State: AOAM531oNkRuOSbw/fFd9ABoH8LeLAKe0k82KgTFyxqUZ/ifKlmPTNpz w8E2sbSWrI+DWSBjcup0SaM+jjvuMTwIG0r9mlY= X-Received: by 2002:a0d:c8c3:0:b0:2fe:e9eb:664 with SMTP id k186-20020a0dc8c3000000b002fee9eb0664mr910598ywd.301.1652900668697; Wed, 18 May 2022 12:04:28 -0700 (PDT) MIME-Version: 1.0 References: <3acd6c32-6e78-dfc2-3e45-84f69a7d5f36@samsung.com> In-Reply-To: <3acd6c32-6e78-dfc2-3e45-84f69a7d5f36@samsung.com> From: "Rafael J. Wysocki" Date: Wed, 18 May 2022 21:04:17 +0200 Message-ID: Subject: Re: [GIT PULL] devfreq next for 5.19 To: Chanwoo Choi Cc: "Rafael J. Wysocki " , "linux-kernel@vger.kernel.org" , "linux-pm@vger.kernel.org" , "Chanwoo Choi (chanwoo@kernel.org)" , Kyungmin Park , =?UTF-8?B?7ZWo66qF7KO8?= Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI, RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 18, 2022 at 4:16 AM Chanwoo Choi wrote: > > Dear Rafael, > > This is devfreq-next pull request for v5.19-rc1. I add detailed description of > this pull request on the following tag. Please pull devfreq with > following updates. > - tag name : devfreq-next-for-5.19 > > Best Regards, > Chanwoo Choi > > > The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17: > > Linux 5.18-rc1 (2022-04-03 14:08:21 -0700) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git tags/devfreq-next-for-5.19 > > for you to fetch changes up to 26984d9d581e5049bd75091d2e789b9cc3ea12e0: > > PM / devfreq: passive: Keep cpufreq_policy for possible cpus (2022-05-17 18:24:39 +0900) > > ---------------------------------------------------------------- > Update devfreq next for v5.19 > > Detailed description for this pull request: > 1. Update devfreq core > - Add cpu based scaling support to passive governor. Some device like > cache might require the dynamic frequency scaling. But, it has very > tightly to cpu frequency. So that use passive governor to scale > the frequency according to current cpu frequency. > > To decide the frequency of the device, the governor does one of the following: > : Derives the optimal devfreq device opp from required-opps property of > the parent cpu opp_table. > > : Scales the device frequency in proportion to the CPU frequency. So, if > the CPUs are running at their max frequency, the device runs at its > max frequency. If the CPUs are running at their min frequency, the > device runs at its min frequency. It is interpolated for frequencies > in between. > > 2. Update devfreq driver > - Update rk3399_dmc.c as following: > : Convert dt-binding document to YAML and deprecate unused properties. > > : Use Hz units for the device-tree properties of rk3399_dmc. > > : rk3399_dmc is able to set the idle time before changing the dmc clock. > Specify idle time parameters by using nano-second unit on dt bidning. > > : Add new disable-freq properties to optimize the power-saving feature > of rk3399_dmc. > > : Disable devfreq-event device on remove() to fix unbalanced > enable-disable count. > > : Use devm_pm_opp_of_add_table() > > : Block PMU (Power-Management Unit) transitions when scaling frequency > by ARM Trust Firmware in order to fix the conflict between PMU and DMC > (Dynamic Memory Controller). > ---------------------------------------------------------------- > > Brian Norris (15): > dt-bindings: devfreq: rk3399_dmc: Convert to YAML > dt-bindings: devfreq: rk3399_dmc: Deprecate unused/redundant properties > dt-bindings: devfreq: rk3399_dmc: Fix Hz units > dt-bindings: devfreq: rk3399_dmc: Specify idle params in nanoseconds > dt-bindings: devfreq: rk3399_dmc: Add more disable-freq properties > PM / devfreq: rk3399_dmc: Drop undocumented ondemand DT props > PM / devfreq: rk3399_dmc: Drop excess timing properties > PM / devfreq: rk3399_dmc: Use bitfield macro definitions for ODT_PD > PM / devfreq: rk3399_dmc: Support new disable-freq properties > PM / devfreq: rk3399_dmc: Support new *-ns properties > PM / devfreq: rk3399_dmc: Disable edev on remove() > PM / devfreq: rk3399_dmc: Use devm_pm_opp_of_add_table() > PM / devfreq: rk3399_dmc: Avoid static (reused) profile > soc: rockchip: power-domain: Manage resource conflicts with firmware > PM / devfreq: rk3399_dmc: Block PMU during transitions > > Chanwoo Choi (3): > PM / devfreq: Export devfreq_get_freq_range symbol within devfreq > PM / devfreq: passive: Reduce duplicate code when passive_devfreq case > PM / devfreq: passive: Keep cpufreq_policy for possible cpus > > Saravana Kannan (1): > PM / devfreq: Add cpu based scaling support to passive governor > > .../devicetree/bindings/devfreq/rk3399_dmc.txt | 212 ----------- > .../memory-controllers/rockchip,rk3399-dmc.yaml | 384 ++++++++++++++++++++ > drivers/devfreq/devfreq.c | 20 +- > drivers/devfreq/governor.h | 27 ++ > drivers/devfreq/governor_passive.c | 403 +++++++++++++++++---- > drivers/devfreq/rk3399_dmc.c | 312 ++++++++-------- > drivers/soc/rockchip/pm_domains.c | 118 ++++++ > include/linux/devfreq.h | 17 +- > include/soc/rockchip/pm_domains.h | 25 ++ > 9 files changed, 1063 insertions(+), 455 deletions(-) > delete mode 100644 Documentation/devicetree/bindings/devfreq/rk3399_dmc.txt > create mode 100644 Documentation/devicetree/bindings/memory-controllers/rockchip,rk3399-dmc.yaml > create mode 100644 include/soc/rockchip/pm_domains.h Pulled, thanks!