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=-1.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 2F4D5C2D0D1 for ; Thu, 19 Dec 2019 16:18:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0735E24676 for ; Thu, 19 Dec 2019 16:18:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576772303; bh=1G7FsQcIs7vqbkyh2F1vAEGEbbdVT8Ma5gTl6fOBv5w=; h=References:In-Reply-To:From:Date:Subject:To:Cc:List-ID:From; b=NYazmiOVmHjpHlp8HUgaJiVygev7kDxM0bt1EYXxuOHJD2GpxH/2nAh8FfpNVtMY6 OrDgiivIocCSyGX/9G9+tKmSFFcG1xK5UW8AQiAaduQPU0jPu+lCUjj1hjrg096mS5 9mL0LlF0nfLFruIzkZc1y+nmxV4yE7s+e/PtfDl4= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726918AbfLSQSW (ORCPT ); Thu, 19 Dec 2019 11:18:22 -0500 Received: from mail.kernel.org ([198.145.29.99]:57964 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726776AbfLSQSV (ORCPT ); Thu, 19 Dec 2019 11:18:21 -0500 Received: from mail-lj1-f182.google.com (mail-lj1-f182.google.com [209.85.208.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 33F1E24680; Thu, 19 Dec 2019 16:18:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576772300; bh=1G7FsQcIs7vqbkyh2F1vAEGEbbdVT8Ma5gTl6fOBv5w=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=e7keS3P1LwF4ZT2yhL3hUCAcyVJrTsIR9UzKe57oNdsSAbK91huuUmxw4uj5fehea NPASNTU1i78K0CrfxLQzQTqC8PFXyuK78gWLUe1LkPDzOG6vkj8LaNDRMqbIllRKcW T4iQc286CEEUti1oEOpDrf0yM1+lENmw2XdKNYw4= Received: by mail-lj1-f182.google.com with SMTP id k8so6866223ljh.5; Thu, 19 Dec 2019 08:18:20 -0800 (PST) X-Gm-Message-State: APjAAAU0x40zpci5J3G0cWwdsMzCLVSzYN6y7pKloPZCDf5nhEACZCB7 baMj4YqOZTyOiPxL9dzDIy/OiQkKK0nmjVYW/gs= X-Google-Smtp-Source: APXvYqzjT3A3BOaMem5ewvhYkhpvnQHmXadd3vZ1Bf2o2UnYr9PFiKmPucQrvExdBSOloWvbcQbzeuZa1+Z2P1vedZA= X-Received: by 2002:a2e:2d01:: with SMTP id t1mr1311467ljt.36.1576772298339; Thu, 19 Dec 2019 08:18:18 -0800 (PST) MIME-Version: 1.0 References: <20190724014222.110767-1-saravanak@google.com> <754ec843-eb8f-5149-bf7f-ec4abf938821@samsung.com> In-Reply-To: <754ec843-eb8f-5149-bf7f-ec4abf938821@samsung.com> From: Chanwoo Choi Date: Fri, 20 Dec 2019 01:17:41 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v4 0/5] Add required-opps support to devfreq passive gov To: Chanwoo Choi Cc: Saravana Kannan , MyungJoo Ham , Kyungmin Park , Viresh Kumar , Nishanth Menon , Stephen Boyd , "Rafael J. Wysocki" , Sibi Sankar , Android Kernel Team , Linux PM , LKML Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Saravana, 2019=EB=85=84 11=EC=9B=94 14=EC=9D=BC (=EB=AA=A9) =EC=98=A4=ED=9B=84 5:36, = Chanwoo Choi =EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1: > > Hi Saravana, > > On 11/14/19 5:23 PM, Saravana Kannan wrote: > > On Wed, Nov 13, 2019 at 11:48 PM Chanwoo Choi w= rote: > >> > >> Dear Saravana, > >> > >> Any other progress of this series? > > > > Hi Chanwoo, > > > > Thanks for checking. I haven't abandoned this patch series. This patch > > series depends on "lazy linking" of required-opps to avoid a cyclic > > dependency between devfreq and OPP table population. But Viresh wasn't > > happy with my implementation of the lazy liking for reasonable > > reasons. > > > > I had a chat with Viresh during one of the several conferences that I > > met him at. To fix the lazy linking in the way he wanted it meant we > > had to fix other issues in the OPP framework that arise when OPP > > tables are shared in DT but not in memory. So he was kind enough to > > sign up to add lazy linking support to OPPs so that I won't have to do > > it. So, I'm waiting on that. So once that's added, I should be able to > > drop a few patches in this series, do some minor updates and then this > > will be good to go. > > Thanks for the detailed explanation. I'll expect the your next version. As I know, the lazy linking issue was fixed by Viresh. If possible, I want to know your plan about 'required-opp' with passive governor. Because I think that the patch[1] is good for devfreq device. As you mentioned, you have the other idea to implement the 'cpu based scaling support' to passive governor without cpu notifier. Actually, if there are no any other best solution, I prefer to use cpu notifier for 'cpu based scaling support to passive_governor'. [1] https://patchwork.kernel.org/patch/11046147/ - [RFC,v2] PM / devfreq: Add cpu based scaling support to passive_governor --=20 Best Regards, Chanwoo Choi