Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp1404509ybt; Thu, 2 Jul 2020 04:42:57 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy5DNFV859No24jl2/29gIMYGIDdvK+VpFqTd2diHTZRjth449eTTYsQsKYFrcs6RCcxnAj X-Received: by 2002:a17:906:35ce:: with SMTP id p14mr26766629ejb.514.1593690177461; Thu, 02 Jul 2020 04:42:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593690177; cv=none; d=google.com; s=arc-20160816; b=dp1zFfZQSj/pn4iKUWh4ALaa/u3P0s8HUA0YIAWfOB/0Fc5Nr0RgbAtFiebNjk5hug bmsj4edCZYq/6PZLKtPmcW0EPLsvdYVICbibskbUEar5DZPodHetG8hKpEx1xoRYAtVd t4vD8EB6J/FUf4yGKJFSu1epCzu7SjgBpcWfLUiYyQRMOuyV3yEotpJLQ4nZgIAzF/9R +niRhJhaZMcuTesMOFIgPN4Vmatxw2caldRqhBQthIvzMMyqpHTSYHSkKa3448tzWI23 OnecfVWbIVtd+MNTM7TKn1T+gPWh9fMLbMUMlv2zLVoZhP/zXNDDqcILjesCqCHBwJd+ xB9A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=293GaFTifXpe4OcKKB4xN33O7oQ+9U9vkY6HQ1Ma3xQ=; b=TwYqCp1se2Bv6mkewOw/qL/UTG0VbxMlwvA7Z9gGLx8E3DQyOXxFKMytqZG/c47gRx 2ffFU3D/zwPRVEc4huNJ9yzpRzGKMKYozwnkSrj73d0AEJnT+v7PDHZMeXB5lvRmHW+n yxvjAgaBcf254QsjE3ztYE9LyEnB5QEtb03bmAW9pQQvgLlor1eehkp+6muWuZ2ZonOu 9kSngXfLbGcO26nXqOIveGN+rFdx1pGCdu4/8Hr0vxiVGUYolN9G7jgCOM+KEkyPrhG6 Ury8H+2DzxA+rz6qztqDzjw9rSDW9Gyjx2nwQsPBpZY9edMZVqkiF/h65J5FTeORu78R ldyg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id r20si5480086edw.577.2020.07.02.04.42.34; Thu, 02 Jul 2020 04:42:57 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728698AbgGBLlz (ORCPT + 99 others); Thu, 2 Jul 2020 07:41:55 -0400 Received: from foss.arm.com ([217.140.110.172]:42548 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727016AbgGBLlz (ORCPT ); Thu, 2 Jul 2020 07:41:55 -0400 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 829D41FB; Thu, 2 Jul 2020 04:41:54 -0700 (PDT) Received: from localhost (unknown [10.1.198.53]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 239563F71E; Thu, 2 Jul 2020 04:41:54 -0700 (PDT) Date: Thu, 2 Jul 2020 12:41:52 +0100 From: Ionela Voinescu To: Viresh Kumar Cc: rjw@rjwysocki.net, catalin.marinas@arm.com, sudeep.holla@arm.com, will@kernel.org, linux@armlinux.org.uk, valentin.schneider@arm.com, mingo@redhat.com, peterz@infradead.org, dietmar.eggemann@arm.com, linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Liviu Dudau Subject: Re: [PATCH 4/8] cpufreq,vexpress-spc: fix Frequency Invariance (FI) for bL switching Message-ID: <20200702114123.GA28120@arm.com> References: <20200701090751.7543-1-ionela.voinescu@arm.com> <20200701090751.7543-5-ionela.voinescu@arm.com> <20200701095414.2wjcnyhndgcedk2q@vireshk-i7> <20200701140735.GB32736@arm.com> <20200702030551.p4cevaahgfvpum4o@vireshk-i7> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200702030551.p4cevaahgfvpum4o@vireshk-i7> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Thursday 02 Jul 2020 at 08:35:51 (+0530), Viresh Kumar wrote: > On 01-07-20, 15:07, Ionela Voinescu wrote: > > On Wednesday 01 Jul 2020 at 16:16:19 (+0530), Viresh Kumar wrote: > > > Is there anyone who cares for this driver and EAS ? I will just skip doing the > > > FIE thing here and mark it skipped. > > > > That is a good question. The vexpress driver is still used for TC2, but > > I don't know of any users of this bL switcher functionality that's part > > of the driver. I think there were a few people wondering recently if > > it's still used [1]. > > Even if it is used by some, there is no need, I believe, to enable > freq-invariance for it, which wasn't enabled until now. > It was enabled until now, but it was partially broken. If you look over the driver you'll see arch_set_freq_scale() being called for both is_bL_switching_enabled() and for when it's not [1]. For !is_bL_switching_enabled() this is fine. But for is_bL_switching_enabled(), it is broken as described in 4/8. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/cpufreq/vexpress-spc-cpufreq.c?h=v5.8-rc3#n203 > And considering that we are going to enable the flag only for the > interested parties now, as from the discussion on 1/8, this shouldn't > be required. > If we just don't want frequency invariance for is_bL_switching_enabled(), I can just guard the setting of the flag suggested by Rafael at 1/8 by !CONFIG_BL_SWITCHER. I'll proceed to do that and remove the fix at 4/8. Many thanks! Ionela. > -- > viresh