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 E19051E32C5; Wed, 30 Oct 2024 11:33:14 +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=1730287997; cv=none; b=o9doOB8/vgA2NPHf9fnYooTsNf+qUF/8m+QXrWg6KObud3Qti9U5PdG0jNcoHcwW9D9k/VN9/U5QFbKSizOD40EGAidBW2SXkTwEHqH+KpkyMP++Fp67+KHyua5+cPomGPmGxHOgY/URFGJoPwMy0lE/j4b8LQGqJI22mdrrhn8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1730287997; c=relaxed/simple; bh=9B/VVbiId1lYYO5sgVk3wUfVIDhtcgA4odTw4h0xYKo=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=OO8EGN9aPTB6erjr7GCd1ZnyGSuLHHSVEbqpYb9y+90/ebtUxP5Vp0gFgeIVCyUoaK8R7x4jKxo9df/WA4UZVL6k0qrk7xHBF5ZicCTFnnrheDvyAHH5YoxrAgScAnc4sFP2LFWk3cU9quDTZJBEBl9v4j6pzeE2lqPhsXEctYo= 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 C76A8113E; Wed, 30 Oct 2024 04:33:43 -0700 (PDT) Received: from [10.57.58.72] (unknown [10.57.58.72]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 3AAB93F66E; Wed, 30 Oct 2024 04:33:13 -0700 (PDT) Message-ID: <6847bb0d-805f-4bf6-bb22-635d5f8e9d6b@arm.com> Date: Wed, 30 Oct 2024 11:34:26 +0000 Precedence: bulk X-Mailing-List: linux-pm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v2 1/1] PM: EM: Add min/max available performance state limits To: "Rafael J. Wysocki" Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, dietmar.eggemann@arm.com References: <20241029094452.495439-1-lukasz.luba@arm.com> <20241029094452.495439-2-lukasz.luba@arm.com> <6cdb2f8b-62e0-455c-a3a5-ed5359a2e941@arm.com> <61afac10-b434-4e39-8c49-c220add4bd8e@arm.com> Content-Language: en-US From: Lukasz Luba In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 10/30/24 11:23, Rafael J. Wysocki wrote: > On Wed, Oct 30, 2024 at 11:00 AM Lukasz Luba wrote: >> >> On 10/30/24 08:48, Lukasz Luba wrote: >>> Hi Rafael, >>> >>> On 10/29/24 18:29, Rafael J. Wysocki wrote: >>>> On Tue, Oct 29, 2024 at 10:43 AM Lukasz Luba wrote: >>>>> >> >> [snip] >> >>>>> +EXPORT_SYMBOL_GPL(em_update_performance_limits); >>>> >>>> It would be good to have at least one caller of this function in the >>>> tree. >>> >>> Yes, I know, but we had delays with the SCMI cpufreq to get the >>> notifications support, which are sent from FW... >>> >>> The patch using this API was part of v1 but with assumption that >>> those SCMI notifications are merged. >>> >>> The patch v1 for the SCMI cpufreq driver [1]. >>> >>> In that v1 cover letter I mentioned that the 2nd patch depends >>> on notifications [2]. >>> >>> I will have to work with Cristian on that notification in SCMI >>> then this API will be used. I can see that it stuck for a while >>> in v5. Let me sort that out (probably not in this merge window >>> though). >> >> Just to link the effort which has been started into that direction: >> >> https://lore.kernel.org/lkml/ab36709d-a181-4621-a8e5-0ef38b80186b@arm.com/ > > OK, then this can be queued up as a prerequisite for the upcoming changes. > > I would, however, mention that in the patch changelog and add a Link: > tag pointing to the above. > Thank you Rafael!