Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp257772rwb; Thu, 1 Dec 2022 01:44:01 -0800 (PST) X-Google-Smtp-Source: AA0mqf72RQipPVMiNL4fbyB2MkEb+uwUtLCxGU5WtfV2WwJ1g61vN+OGg9Ah6jMF6oFb9K8kSlcK X-Received: by 2002:a17:90a:df0e:b0:20b:22fb:2ef with SMTP id gp14-20020a17090adf0e00b0020b22fb02efmr76196681pjb.158.1669887840841; Thu, 01 Dec 2022 01:44:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669887840; cv=none; d=google.com; s=arc-20160816; b=wrml8hqaaraKoIWVfo7v/c8FVg0NThIExps0EVyqlw+3OXUpYlvTd6web92pIiGEJo fKUg6tZ70nKiYbDvMMxzc0UTdUM0tdfSam97rW5rD0Ysn1qjH/s8UQx41Aq4TfJimBQ/ OWIJIFS6bMHleLnYjVVtmIcUKRoZ+PwthfNyLGKnHQKJ8O/JlHFjCIupmVaCb7Fvt6Pk kFsUlDn2WQSytk9cnVu9Y7hvQ5thQg4Gx2qHHFd2SglpBBET3UAZ0Sys451SpyBRJxyN 3Dfsov84sFAhJj2wAuHeXk2uuYMg/96k2gBtQBIlLNYAdfdbz9fADvtID9pzShtwkRa7 N7QA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:subject:cc:to:from; bh=14qbYOEYpzReMsIPScSsUx8HUeChG3nOvHbGQWlJUb4=; b=jpLpjhxatNmkmxkbtyMAJ8s3pzu5wshWWERgfqAiWRTkzKhVoKQEcZ91dYQtpqZxPx W2hP/UzQ/rd2Q1huPGSHlj2VW+n9BEN99FbKBucOW27NDa0N0jeINxjhitKROwh+PHS3 BO3PB9KeXsdVern1y7RfotSrlbmg1sqdXiBRS3xmpKVFyd5oAIiUXMDN7bDyn04+LrfH GBvHQsi7fHmHovW+5+jpktx+Ok66o2A+r5Ae/CgF6LEdM4iAV263xMKi9NzPuVlvADcV kN9vPg7uEfqo2ne33wQbCTRGlqCMt0OjubSXHMTgXNqCiWIg0RnIRT7xoBZNLJ67EM++ aVoA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x18-20020a17090a8a9200b00218906bfbcbsi4289793pjn.172.2022.12.01.01.43.50; Thu, 01 Dec 2022 01:44:00 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229877AbiLAI4n (ORCPT + 82 others); Thu, 1 Dec 2022 03:56:43 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56606 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229863AbiLAI4i (ORCPT ); Thu, 1 Dec 2022 03:56:38 -0500 Received: from SHSQR01.spreadtrum.com (mx1.unisoc.com [222.66.158.135]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BA55C4A06F; Thu, 1 Dec 2022 00:56:34 -0800 (PST) Received: from SHSend.spreadtrum.com (bjmbx01.spreadtrum.com [10.0.64.7]) by SHSQR01.spreadtrum.com with ESMTPS id 2B18sQ3b030588 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NO); Thu, 1 Dec 2022 16:54:26 +0800 (CST) (envelope-from Di.Shen@unisoc.com) Received: from bj10906pcu1.spreadtrum.com (10.0.74.51) by BJMBX01.spreadtrum.com (10.0.64.7) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Thu, 1 Dec 2022 16:54:27 +0800 From: Di Shen To: , , , CC: , , Subject: [PATCH] thermal/of: Allow users to set governor for a thermal zone in DT Date: Thu, 1 Dec 2022 16:54:23 +0800 Message-ID: <20221201085423.10360-1-di.shen@unisoc.com> X-Mailer: git-send-email 2.17.1 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.0.74.51] X-ClientProxiedBy: SHCAS03.spreadtrum.com (10.0.1.207) To BJMBX01.spreadtrum.com (10.0.64.7) X-MAIL: SHSQR01.spreadtrum.com 2B18sQ3b030588 X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The governor of all thermal zones can be initialized in thermal_zone_device_register_with_trips(), but it is always the def_governor, this means the governor of all thermal zones are the same. Allow users to set governor for a specific thermal zone in DT, in this way, users can use different policies for thermal management. Signed-off-by: Di Shen --- drivers/thermal/thermal_of.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/drivers/thermal/thermal_of.c b/drivers/thermal/thermal_of.c index d4b6335ace15..5dd4101dffb6 100644 --- a/drivers/thermal/thermal_of.c +++ b/drivers/thermal/thermal_of.c @@ -355,6 +355,7 @@ static struct thermal_zone_params *thermal_of_parameters_init(struct device_node int coef[2]; int ncoef = ARRAY_SIZE(coef); int prop, ret; + const char *governor_name; tzp = kzalloc(sizeof(*tzp), GFP_KERNEL); if (!tzp) @@ -365,6 +366,9 @@ static struct thermal_zone_params *thermal_of_parameters_init(struct device_node if (!of_property_read_u32(np, "sustainable-power", &prop)) tzp->sustainable_power = prop; + if (!of_property_read_string(np, "policy", &governor_name)) + strncpy(tzp->governor_name, governor_name, THERMAL_NAME_LENGTH); + /* * For now, the thermal framework supports only one sensor per * thermal zone. Thus, we are considering only the first two -- 2.17.1