From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by smtp.subspace.kernel.org (Postfix) with ESMTP id CD8465A0EB; Tue, 23 Jan 2024 10:15:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.140.110.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706004930; cv=none; b=OaII2NXuE9AgSP0iFaMsojEHhE+F5mX1bhYUUjzZC/AmvRQXiaoH1Dub3jWW+IUcMDIhxuOkFY9K+c2BRk6ix14UmbsPemqfR5IOthjKDE/GOd50B9K5U0LNsWjJLV44RLFq7auLYJK2byMm+Bu+TmJeCC9T1rAUw9y7ba4JTYo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706004930; c=relaxed/simple; bh=qgJAvwjqadOAFVHNp00pGGzUi/Sz+qHJ/cHPAJhKjYg=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=YY5scCwMnIdiKwjp198DU7j5Zwu611RY0Bjhv6ctFR9kYHHIaH6f8XoaC2fvJ0BySsLNIILYKkUVReE1yTUf400w3Jj4kwh5jhnHS52WfisEnb/Xx1dkCA0Mwz+bYrE3B2CaVrncihcZN9usxuwVbtBm6tZnWy1CtJkQwwKUtkw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com; spf=pass smtp.mailfrom=arm.com; arc=none smtp.client-ip=217.140.110.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arm.com 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 778521FB; Tue, 23 Jan 2024 02:16:06 -0800 (PST) Received: from bogus (e103737-lin.cambridge.arm.com [10.1.197.49]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 3F35F3F5A1; Tue, 23 Jan 2024 02:15:19 -0800 (PST) Date: Tue, 23 Jan 2024 10:15:16 +0000 From: Sudeep Holla To: Viresh Kumar Cc: Sibi Sankar , cristian.marussi@arm.com, rafael@kernel.org, morten.rasmussen@arm.com, Sudeep Holla , dietmar.eggemann@arm.com, lukasz.luba@arm.com, sboyd@kernel.org, linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, quic_mdtipton@quicinc.com, linux-arm-msm@vger.kernel.org, nm@ti.com Subject: Re: [PATCH 0/3] cpufreq: scmi: Add boost frequency support Message-ID: References: <20240117110443.2060704-1-quic_sibis@quicinc.com> <20240123060827.a3vszziftj6pszt3@vireshk-i7> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240123060827.a3vszziftj6pszt3@vireshk-i7> On Tue, Jan 23, 2024 at 11:38:27AM +0530, Viresh Kumar wrote: > On 17-01-24, 16:34, Sibi Sankar wrote: > > This series adds provision to mark dynamic opps as boost capable and adds > > boost frequency support to the scmi cpufreq driver. > > > > Depends on: > > HW pressure v4: https://patchwork.kernel.org/project/linux-arm-msm/cover/20240109164655.626085-1-vincent.guittot@linaro.org/ > > scmi notification v2: https://patchwork.kernel.org/project/linux-arm-msm/cover/20240117104116.2055349-1-quic_sibis@quicinc.com/ > > > > Sibi Sankar (3): > > OPP: Extend dev_pm_opp_data with turbo support > > firmware: arm_scmi: Add support for marking certain frequencies as > > boost > > cpufreq: scmi: Enable boost support > > Sudeep, please lemme know if you are okay with the changes. Will apply > them. I was planning to look at it once Lukasz/Dietmar confirm that this concept doesn't change anything fundamental in the way EAS related changes work today. I know I suggested the change as that seem to be right way to do but I haven't analysed if this has any negative impact on the existing features as this change will impact all the existing platform with OPPs above sustained performance/frequency advertised from the SCMI platform firmware. -- Regards, Sudeep