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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 848A6C38142 for ; Thu, 19 Jan 2023 07:59:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230040AbjASH7O (ORCPT ); Thu, 19 Jan 2023 02:59:14 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34042 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230006AbjASH6o (ORCPT ); Thu, 19 Jan 2023 02:58:44 -0500 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 178A83EFED; Wed, 18 Jan 2023 23:58:41 -0800 (PST) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id BA0441758; Wed, 18 Jan 2023 23:59:22 -0800 (PST) Received: from [10.57.10.42] (unknown [10.57.10.42]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 2201F3F445; Wed, 18 Jan 2023 23:58:39 -0800 (PST) Message-ID: Date: Thu, 19 Jan 2023 07:58:38 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: [PATCH v2] cpufreq: Register with perf domain before Content-Language: en-US To: Viresh Kumar Cc: Vincent Wang , Vincent Wang , rafael@kernel.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org References: <20230118044733.29391-1-bhuwz@163.com> <20230118084923.m3ztfn6v3hskpad6@vireshk-i7> <529d967f-9dbc-5b35-546a-428cbb191f0f@arm.com> <20230119053952.qwh2yrmhddzocnju@vireshk-i7> From: Lukasz Luba In-Reply-To: <20230119053952.qwh2yrmhddzocnju@vireshk-i7> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/19/23 05:39, Viresh Kumar wrote: > On 18-01-23, 09:24, Lukasz Luba wrote: >> Viresh, If that's an issue for other governors, than maybe >> we should address that. > > As you said in the other email, it isn't a mainline issue, I will > ignore it then :) > Fair enough. Although, I hope one day, maybe at some conference, we could discuss those Android-kernel vs. mainline differences. IMO the gap isn't shrinking, but I would like to shrink it. Especially when we are serious about long term kernel support for mobile devices, this gap should be tiny. Therefore, I would tackle this scheduler cpufreq governors and API for them.