Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp314398ybb; Tue, 24 Mar 2020 23:36:09 -0700 (PDT) X-Google-Smtp-Source: ADFU+vsciF3de8I0WXziwP0Fbb20jGbcNv7pCgOJPv9dWiRqXQj1+oo3mEcE49groZDGGmO8hvmC X-Received: by 2002:a9d:2f26:: with SMTP id h35mr1312236otb.246.1585118168979; Tue, 24 Mar 2020 23:36:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585118168; cv=none; d=google.com; s=arc-20160816; b=sIUce/k3qYPDtPVPy8EifQ+bOJeoAG+FvkYMHkSO9aX5RKsn93AlUTeT3mcGskdKK/ 56Sv0uxexmMyKqzlQIo8jYFz8Xn7SHokvV4LwUUQguigmCevqPPHVz/u0acf2MsJmrqt e7Js1jlWoNIzykLgoIyEmWX/OQwk7LhuBMaKJFeWuxtvKOg/9ZVgYHmyN/uJLAo1Qs/J 77J3S1UO1LXs79wgsqIFMQEhxUn5OriAJ4zRuFHzoCEsEfcYdpRR3RSzBoWcA7WBtyTS ek/X7COHUPvHzRZa7K1TyltQcaaapbFi5df7nwKsMJ7mtCNJepzMSrOedio6I5TgTeoJ Fs5w== 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:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=cUTwMh8vYUOuCdm83Oh+4utbVCeDW5nkMaz7OgaXqiA=; b=ilGgepgVCPOirZjQy408GllXYE7NIYCanC/NrK4cu0uQWX3ktV5wM/fEvf91c77KkN G1LK2zWc6dILh4E6EzL13tPsGVaGffsOx+0Uy/VUskFtSuuLatu14ogf0vYKwrpWfXJf eFXai8TxVqrwpFQnL+y8yrzdjV6d1lIHSJckxoiChPT8gF8M/Pzy22A9AZOA7gq6qA8i CJtNitGl7wZJSY1yyPis2rIgt7Cv5IK+ah9mul5Pm2oV0cLnlZNwEV2/APUQsQludxwR mIkbdJPOQOMtMabD7NAh9y78JjC7aPDeihgJHcKXKN1EMmOSGl681Z8PIvopnnCbx5lE 6SlQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=XrvKWaKg; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k26si10304638otr.68.2020.03.24.23.35.55; Tue, 24 Mar 2020 23:36:08 -0700 (PDT) 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; dkim=pass header.i=@linaro.org header.s=google header.b=XrvKWaKg; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727302AbgCYGfM (ORCPT + 99 others); Wed, 25 Mar 2020 02:35:12 -0400 Received: from mail-pl1-f181.google.com ([209.85.214.181]:42584 "EHLO mail-pl1-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727291AbgCYGfL (ORCPT ); Wed, 25 Mar 2020 02:35:11 -0400 Received: by mail-pl1-f181.google.com with SMTP id e1so416041plt.9 for ; Tue, 24 Mar 2020 23:35:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=cUTwMh8vYUOuCdm83Oh+4utbVCeDW5nkMaz7OgaXqiA=; b=XrvKWaKgVCjcVg5NxnjxhOOyGfckchfa6NdqKzjA2rQWga/RhL7RsqYLXjVCBK3dXz R3aHEFbgCCB5aZMJtL2ZjF2y/cbS/E3QZrYYS3IlkwHH88GwZwY6Dtx3nbZGHAMu3w1Y 2xzpbyFQawY5lWyXn5ifN6COr5on0z8xol5EULoxlKcYPRZIstapvHdcP4w/GBqOdgp4 20aam8ZYfZvdLtjRJ+tlWRglRNm8Db21+MVaL0hvS+CHLB9B00Z9SYuje2ltTwrE5fmm 0gIAbEIk+BPLY3AlQb8PKoQ9bpPo4/SZrVYWUpNmoNg3agpT149ugTSU3gl34O9ZzXba 0oZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=cUTwMh8vYUOuCdm83Oh+4utbVCeDW5nkMaz7OgaXqiA=; b=SGURbudPF67SEaekD9idkrRVn6nF8xiquxLaPM72HXb43pWwoFlFuktpjfU4HeeL2/ pINR0l0vZ/vQfmxn3WKkXK+j6P18Tdfk+xjekc4DVTT/KtBdpXz0Aolt/8UlbcBkXdp4 hu+M/xEsm7ECkRsI6wPCxZNtbw1u7s5XnE/duvPpOdigwuRwzYVwCywkMXC3Ivv7Vd4u oNSzWPih2ygPyTP6vI1BETs0ktTcmBs4ADL1wovs5M+2qBf9xZazJD/3qxH27qOvDXIa PbaFrxj/9X1jobN3s/uuhNkLJddQyRhhDaRWI9RPBm+7UrMeD3VhsmtLje4abPGK0nxK izKQ== X-Gm-Message-State: ANhLgQ0eKVFfb7weYiYW6mdFWYiS1Qlb45GHO8RqnuId7aCZ99MjLLXc KFv55JMC/jY3ycdtf1SFDEcsMn9s9Bo= X-Received: by 2002:a17:90a:da03:: with SMTP id e3mr1960501pjv.57.1585118108692; Tue, 24 Mar 2020 23:35:08 -0700 (PDT) Received: from localhost ([103.195.202.71]) by smtp.gmail.com with ESMTPSA id mn18sm3822619pjb.13.2020.03.24.23.35.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 24 Mar 2020 23:35:07 -0700 (PDT) From: Amit Kucheria To: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, swboyd@chromium.org, mka@chromium.org, daniel.lezcano@linaro.org, Amit Kucheria , Zhang Rui Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org Subject: [PATCH v3 2/3] dt-bindings: thermal: Add yaml bindings for thermal cooling-devices Date: Wed, 25 Mar 2020 12:04:53 +0530 Message-Id: <1ee4240e29edefc36b5d410d4792971c2bb4c5d5.1585117436.git.amit.kucheria@linaro.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org As part of moving the thermal bindings to YAML, split it up into 3 bindings: thermal sensors, cooling devices and thermal zones. The property #cooling-cells is required in each device that acts as a cooling device - whether active or passive. So any device that can throttle its performance to passively reduce heat dissipation (e.g. cpus, gpus) and any device that can actively dissipate heat at different levels (e.g. fans) will contain this property. Signed-off-by: Amit Kucheria --- .../thermal/thermal-cooling-devices.yaml | 116 ++++++++++++++++++ 1 file changed, 116 insertions(+) create mode 100644 Documentation/devicetree/bindings/thermal/thermal-cooling-devices.yaml diff --git a/Documentation/devicetree/bindings/thermal/thermal-cooling-devices.yaml b/Documentation/devicetree/bindings/thermal/thermal-cooling-devices.yaml new file mode 100644 index 000000000000..b5599f7859f8 --- /dev/null +++ b/Documentation/devicetree/bindings/thermal/thermal-cooling-devices.yaml @@ -0,0 +1,116 @@ +# SPDX-License-Identifier: (GPL-2.0) +# Copyright 2020 Linaro Ltd. +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/thermal/thermal-cooling-devices.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Thermal cooling device binding + +maintainers: + - Amit Kucheria + +description: | + Thermal management is achieved in devicetree by describing the sensor hardware + and the software abstraction of cooling devices and thermal zones required to + take appropriate action to mitigate thermal overload. + + The following node types are used to completely describe a thermal management + system in devicetree: + - thermal-sensor: device that measures temperature, has SoC-specific bindings + - cooling-device: device used to dissipate heat either passively or artively + - thermal-zones: a container of the following node types used to describe all + thermal data for the platform + + This binding describes the cooling devices. + + There are essentially two ways to provide control on power dissipation: + - Passive cooling: by means of regulating device performance. A typical + passive cooling mechanism is a CPU that has dynamic voltage and frequency + scaling (DVFS), and uses lower frequencies as cooling states. + - Active cooling: by means of activating devices in order to remove the + dissipated heat, e.g. regulating fan speeds. + + Any cooling device has a range of cooling states (i.e. different levels of + heat dissipation). They also have a way to determine the state of cooling in + which the device is. For example, a fan's cooling states correspond to the + different fan speeds possible. Cooling states are referred to by single + unsigned integers, where larger numbers mean greater heat dissipation. The + precise set of cooling states associated with a device should be defined in + a particular device's binding. + +select: true + +properties: + "#cooling-cells": + description: + Must be 2, in order to specify minimum and maximum cooling state used in + the cooling-maps reference. The first cell is the minimum cooling state + and the second cell is the maximum cooling state requested. + const: 2 + +examples: + - | + #include + #include + + // Example 1: Cpufreq cooling device on CPU0 + cpus { + #address-cells = <2>; + #size-cells = <0>; + + CPU0: cpu@0 { + device_type = "cpu"; + compatible = "qcom,kryo385"; + reg = <0x0 0x0>; + enable-method = "psci"; + cpu-idle-states = <&LITTLE_CPU_SLEEP_0 + &LITTLE_CPU_SLEEP_1 + &CLUSTER_SLEEP_0>; + capacity-dmips-mhz = <607>; + dynamic-power-coefficient = <100>; + qcom,freq-domain = <&cpufreq_hw 0>; + #cooling-cells = <2>; + next-level-cache = <&L2_0>; + L2_0: l2-cache { + compatible = "cache"; + next-level-cache = <&L3_0>; + L3_0: l3-cache { + compatible = "cache"; + }; + }; + }; + + /* ... */ + + }; + + /* ... */ + + thermal-zones { + cpu0-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens0 1>; + + trips { + cpu0_alert0: trip-point0 { + temperature = <90000>; + hysteresis = <2000>; + type = "passive"; + }; + }; + + cooling-maps { + map0 { + trip = <&cpu0_alert0>; + cooling-device = <&CPU0 THERMAL_NO_LIMIT + THERMAL_NO_LIMIT>; + }; + }; + }; + + /* ... */ + }; +... -- 2.20.1