Received: by 2002:a05:7412:419a:b0:f3:1519:9f41 with SMTP id i26csp413932rdh; Thu, 23 Nov 2023 07:19:12 -0800 (PST) X-Google-Smtp-Source: AGHT+IF1ac8PAT0Hrlnb9JfkcnPnJnOg5G9wbLLYIoiuMSe1CnK0GJ9HUefnZABHREsb/hqZsCbM X-Received: by 2002:a05:6a20:e117:b0:18b:9f43:7d75 with SMTP id kr23-20020a056a20e11700b0018b9f437d75mr1967378pzb.17.1700752752332; Thu, 23 Nov 2023 07:19:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1700752752; cv=none; d=google.com; s=arc-20160816; b=pwx9IPAxkbTwgSJMWDc37hlDwUAvrAZeuyzbAsD83sKHCcKmCbjNZk9PrTzqOnBI8w Oiouq9FbJVXSfJdBg2bFMj1QotswbGYsUFUJ++GPEnAmlWqIJXxZe8uMi1vTcSP0eOSq BnDK29JVCPPujSIHyPhQ43jLi/MsrqB4oEZKVpGTC+w/BKD2QrAP8/CSq2Ns5Xogcae0 D412bcObH8eT+EhO12bQ2hkbr46RKO0CINqcy1zb3g1WkhKuXeb1aXVbRhLz9tCdHd2b 1bwfeDMBQvSsCwI2B6a3nvYswZw3yTdSTUtE5+RZffXTJu0+Past641DKbnJ4xHF6ME+ 9tGA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:references :cc:to:from:content-language:subject:user-agent:mime-version:date :message-id; bh=l91SYnEWRgcrJtBbv1Tiq11FkJJoT43JHaHvKQ6eeuc=; fh=s+3ccwKL/Xc2i8uH9tAeSOb9IGpvLhPrVmnBNs/vSzQ=; b=dM098NM6tlfwX/xUfjIctQhUPL38jqR02qTeWGUUnmIs/ur022aqiJ5/RljSE0DO19 XQKdmBClS0aeizQqFcaJwOIFgVdzfOCVvS8DQVeeQGZe8O6wuy6vfBK30j5/KBsQLYJe TP2dJBY4RBiZKseycWSQAIx2ZMV5+flxyEki6iNIjycwnNtG32xd40iJBBoqRPjX7qVJ bNY/3Wlenqk+79K3kK7vChWpjxeCYcX/mZ+mmfyVWY8HeLKyUJCplThGjW6tDX7U4Uo/ D1jlnw/LwI55KPjG3Y+7tVs1yWZqpOxBYBdHkWP1uLMlhK6/liH9N1K3Lzha+0S0UsQ6 ezlg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from agentk.vger.email (agentk.vger.email. [23.128.96.32]) by mx.google.com with ESMTPS id w19-20020a634913000000b005c1b289757dsi1450599pga.88.2023.11.23.07.19.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 23 Nov 2023 07:19:12 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) client-ip=23.128.96.32; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by agentk.vger.email (Postfix) with ESMTP id F17D9804C1B1; Thu, 23 Nov 2023 07:19:09 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at agentk.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346017AbjKWPSz (ORCPT + 99 others); Thu, 23 Nov 2023 10:18:55 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41046 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1345997AbjKWPSx (ORCPT ); Thu, 23 Nov 2023 10:18:53 -0500 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 26460C1; Thu, 23 Nov 2023 07:19:00 -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 5B41E12FC; Thu, 23 Nov 2023 07:19:46 -0800 (PST) Received: from [10.57.4.190] (unknown [10.57.4.190]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 0667D3F6C4; Thu, 23 Nov 2023 07:18:58 -0800 (PST) Message-ID: <5fd9ce52-9216-47ae-9ed3-fabb0f3b02fd@arm.com> Date: Thu, 23 Nov 2023 15:19:58 +0000 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 0/7] Minor cleanup for thermal gov power allocator Content-Language: en-US From: Lukasz Luba To: "Rafael J. Wysocki" Cc: linux-kernel@vger.kernel.org, daniel.lezcano@linaro.org, linux-pm@vger.kernel.org, rui.zhang@intel.com References: <20231025192225.468228-1-lukasz.luba@arm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on agentk.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (agentk.vger.email [0.0.0.0]); Thu, 23 Nov 2023 07:19:10 -0800 (PST) Hi Rafael, Gentle ping On 10/26/23 13:22, Lukasz Luba wrote: > > > On 10/26/23 09:54, Rafael J. Wysocki wrote: >> On Wed, Oct 25, 2023 at 9:21 PM Lukasz Luba wrote: >>> >>> Hi all, >>> >>> The patch set does some small clean up for Intelligent Power Allocator. >>> Those changes are not expected to alter the general functionality. >>> They just >>> improve the code reading. Only patch 3/7 might improve the use case for >>> binding the governor to thermal zone (very unlikely in real products, >>> but >>> it's needed for correctness). >>> >>> The changes are based on top of current PM thermal branch, so with the >>> new trip points. >>> >>> Regards, >>> Lukasz >>> >>> Lukasz Luba (7): >>>    thermal: gov_power_allocator: Rename trip_max_desired_temperature >>>    thermal: gov_power_allocator: Setup trip points earlier >>>    thermal: gov_power_allocator: Check the cooling devices only for >>>      trip_max >>>    thermal: gov_power_allocator: Rearrange the order of variables >>>    thermal: gov_power_allocator: Use shorter variable when possible >>>    thermal: gov_power_allocator: Remove unneeded local variables >>>    thermal: gov_power_allocator: Clean needed variables at the beginning >>> >>>   drivers/thermal/gov_power_allocator.c | 123 ++++++++++++++------------ >>>   1 file changed, 64 insertions(+), 59 deletions(-) >>> >>> -- >> >> The series looks good to me overall, but I'd prefer to make these >> changes in the 6.8 cycle, because the 6.7 merge window is around the >> corner and there is quite a bit of thermal material in this cycle >> already. > > Thanks for having a look! Yes, I agree, we can wait after the > merge window. It just have to be cleaned one day a bit and I postponed > this a few times, so no rush ;) I've seen you've created the new pm/thermal. Could you consider to take those in, please? I would send some RFC on top showing the issue with reading back the CPU max frequency from the PM_QoS chain. Regards, Lukasz