Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2622428imu; Thu, 29 Nov 2018 07:47:52 -0800 (PST) X-Google-Smtp-Source: AFSGD/Wcm9uo3avvtKXTykKN60bu1tx2Rsc2/i2H1W6TgBVhRir6wb3r6oBCgx4sApKii+plhY5F X-Received: by 2002:a17:902:a5ca:: with SMTP id t10mr1935522plq.139.1543506472772; Thu, 29 Nov 2018 07:47:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543506472; cv=none; d=google.com; s=arc-20160816; b=Z1w5Ib8r/KMX/JJRsEYDuwcdN1oR+KN/5rveiKMwGPgpetlFD53/XNeYaTT+JbhBLP 1QeUMkEbDkEJw//P03/pnP87U0NZZ/4Avcjl/+F+LwHeeFc1SbVniEp9ji3chcGkxzGb O+nq81mzfdndGVU4sSMi9WuPfI2+ch6UTo14c3o96ket3pRWPqRzN6QaOUxVno8ui+4m s+CJuOKl56A3M1bxJmEsf3GMwP0Cpa225LpAclG9vUqdsxDEgKtHbm+zIKP+lTLZOAQH SLp9jfY4O5MU6WU3M7wbCPuCwp0IohuuX2j6aKmDsrKkoapI9otGKNm+5mst2GHBnzf3 fJlQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject; bh=7Hv7vgAeE6rSVKDozESCWC9lcnMqBkGSGO2AzL8NYz4=; b=uiajN2YBlvEjjInJaSSdDmt8kacMxVUmjgrUBn63nO5VdxskKas29nlPjyY5UWZtUk CatUDg4W6ZRzplCsMIMJ9sONNNfFQvoI1k4xoI3LmirEBRNILdeiF3GFJcBTbs1HCRwh ep76ZvXV9hmfpLdkHkhhuJT6lQbvmHSF48YMXssGoihbEXzUMtWfz1bjfIUoTWAeRAts TvLY5nHwJM0KrZH9tlukqyl8Md77ye3CouSy0GIuM9ykZbDt/tW6j4TEVl9U+P/8N3Vi Pv8BpM3ZFBYcJSLpTkvFxErnFYufkafS3nAmOP8I87XGDgYlaCcNnb6MQiog03Y3AXFV WdHQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 7si2401322pll.297.2018.11.29.07.47.29; Thu, 29 Nov 2018 07:47:52 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728899AbeK3CvF (ORCPT + 99 others); Thu, 29 Nov 2018 21:51:05 -0500 Received: from szxga05-in.huawei.com ([45.249.212.191]:15172 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728363AbeK3CvF (ORCPT ); Thu, 29 Nov 2018 21:51:05 -0500 Received: from DGGEMS409-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id 061C188CC4085; Thu, 29 Nov 2018 23:45:14 +0800 (CST) Received: from [127.0.0.1] (10.202.226.42) by DGGEMS409-HUB.china.huawei.com (10.3.19.209) with Microsoft SMTP Server id 14.3.408.0; Thu, 29 Nov 2018 23:45:14 +0800 Subject: Re: [PATCH 05/10] ARM64: dts: hisilicon: Add all CPUs in cooling maps To: Viresh Kumar , Mark Rutland , Rob Herring , References: <89bb8c62404aa875d597da89c18852ce81fb9f26.1542362530.git.viresh.kumar@linaro.org> CC: , Vincent Guittot , Daniel Lezcano , , From: Wei Xu Message-ID: <5C000983.3030609@hisilicon.com> Date: Thu, 29 Nov 2018 15:45:07 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <89bb8c62404aa875d597da89c18852ce81fb9f26.1542362530.git.viresh.kumar@linaro.org> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.202.226.42] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Viresh, On 2018/11/16 10:04, Viresh Kumar wrote: > Each CPU can (and does) participate in cooling down the system but the > DT only captures a handful of them, normally CPU0, in the cooling maps. > Things work by chance currently as under normal circumstances its the > first CPU of each cluster which is used by the operating systems to > probe the cooling devices. But as soon as this CPU ordering changes and > any other CPU is used to bring up the cooling device, we will start > seeing failures. > > Also the DT is rather incomplete when we list only one CPU in the > cooling maps, as the hardware doesn't have any such limitations. > > Update cooling maps to include all devices affected by individual trip > points. > > Signed-off-by: Viresh Kumar Applied to the hisilicon soc dt tree. Thanks! Best Regards, Wei > --- > arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 10 ++++++++-- > arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 9 ++++++++- > 2 files changed, 16 insertions(+), 3 deletions(-) > > diff --git a/arch/arm64/boot/dts/hisilicon/hi3660.dtsi b/arch/arm64/boot/dts/hisilicon/hi3660.dtsi > index d943a96eedee..20ae40df61d5 100644 > --- a/arch/arm64/boot/dts/hisilicon/hi3660.dtsi > +++ b/arch/arm64/boot/dts/hisilicon/hi3660.dtsi > @@ -1118,12 +1118,18 @@ > map0 { > trip = <&target>; > contribution = <1024>; > - cooling-device = <&cpu0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>; > + cooling-device = <&cpu0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>, > + <&cpu1 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>, > + <&cpu2 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>, > + <&cpu3 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>; > }; > map1 { > trip = <&target>; > contribution = <512>; > - cooling-device = <&cpu4 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>; > + cooling-device = <&cpu4 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>, > + <&cpu5 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>, > + <&cpu6 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>, > + <&cpu7 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>; > }; > }; > }; > diff --git a/arch/arm64/boot/dts/hisilicon/hi6220.dtsi b/arch/arm64/boot/dts/hisilicon/hi6220.dtsi > index 97d5bf2c6ec5..aec9e371c2a7 100644 > --- a/arch/arm64/boot/dts/hisilicon/hi6220.dtsi > +++ b/arch/arm64/boot/dts/hisilicon/hi6220.dtsi > @@ -893,7 +893,14 @@ > cooling-maps { > map0 { > trip = <&target>; > - cooling-device = <&cpu0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>; > + cooling-device = <&cpu0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>, > + <&cpu1 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>, > + <&cpu2 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>, > + <&cpu3 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>, > + <&cpu4 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>, > + <&cpu5 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>, > + <&cpu6 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>, > + <&cpu7 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>; > }; > }; > }; >