Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp2127583ybv; Sun, 23 Feb 2020 23:21:14 -0800 (PST) X-Google-Smtp-Source: APXvYqxTjxOqZqtCy903KNs21eQOCk/2vaBuhvwNYc7K6CKmyg96nRXwS63kmHh8A++1DrP2VcdA X-Received: by 2002:aca:2412:: with SMTP id n18mr11376473oic.134.1582528874569; Sun, 23 Feb 2020 23:21:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582528874; cv=none; d=google.com; s=arc-20160816; b=MV5LJanelO8Fy7Gwk5eI9HEHB2L/YW76SrNRmj1pdTasFzHJZWFrMEtU3yiPurY60L BXIuUOm3MYvXWTff4i6eTmWH8MUxYzvyX842dRNn336HSJyZL9K3c8dNjWtyVKsxFtGh 0IobWvVJA6kcdD/e9mTSTbPqCOMWqnODa+vawxHT+Vg5xGIMTrkrmAKcuHY2sjlalQOr B4+u9vak8B0aP/YOGEWI2arCqOC60V9C+NYocKbqP9pVQ2+yaufUU6Kr8/noSheE0Ujb xZCnIotgmkQhhNz1QoOi/rQE2g7LKxz7TNfE3K9HGta8aPbAr7Wpu4FCN/yGTaWRg8eR NdGw== 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=d17BUbT9BeIhozRgLya99QrlVVsu5JDoV05HFzpYDyI=; b=pgIsGJfGWlFpGpSwnqRLcHrrjzUx9tXOWAgESfKTq+E7UJD70HbmGrtAW+54IFRvpf AhjUQleYRo+g8aThCYHmgPCr+6dot5kcX/2wuEr+XXO58BsDUZuROrs2XIgFqPQRao5D yiTaaAmuExLcZ8YlPqE4ApvdXkfg/cVquEIUlgoPVRbbwGMS8ZYJxsxCMR9LElEFvHcr pskgPunrfJWeCgKQ8EGbnvLhFrxO2smvQUv3bOZ9f0X51/hDN2k4rv2OgubExD253XWo lHh/uYIHlzVyYENgQKrwBkizA9p25FLlg8db4arC6QhoJ9PcvqHuomUJAjKS1wJ0F4Ci YEJQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=tX4PPsoA; 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 z14si4672552oih.89.2020.02.23.23.21.02; Sun, 23 Feb 2020 23:21:14 -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; dkim=pass header.i=@linaro.org header.s=google header.b=tX4PPsoA; 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 S1727276AbgBXHUm (ORCPT + 99 others); Mon, 24 Feb 2020 02:20:42 -0500 Received: from mail-pf1-f195.google.com ([209.85.210.195]:33777 "EHLO mail-pf1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727275AbgBXHUk (ORCPT ); Mon, 24 Feb 2020 02:20:40 -0500 Received: by mail-pf1-f195.google.com with SMTP id n7so4903751pfn.0 for ; Sun, 23 Feb 2020 23:20:40 -0800 (PST) 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=d17BUbT9BeIhozRgLya99QrlVVsu5JDoV05HFzpYDyI=; b=tX4PPsoAZ93qYdTGJqfLDnzMCWiEL3N5LumrMh2+TNF6m+7oLL1F/EyrLxp8necb50 lRiepTn9LHb9aWKxBomyH/Iaa5/v51oKIB//XnqfstKAsBTut8pSKd8fdWs8xwQHuUzg 8o8wlUgtf2HJvHwcJejj/aPFf+g3iMDcY0O67nMuaj7aUtWswClNLW6mdlG5ThzeAwGH 0hDVabld3B5XHbNQebcc4dJ/nHLD0T+lP0B+OHv/3fY0gKFH+tcRw0zKkySPCCZ5OM9d f8Z8PibHVvKo9ab7zuC/u8JhdzJ33I3KimAGvdJenvKTatQ6EbleVbIYNofJR8XYYF1O FALw== 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=d17BUbT9BeIhozRgLya99QrlVVsu5JDoV05HFzpYDyI=; b=ZG/TgVDBWpe3jCjTtwDwtdmAaeUUaqO3bcq5aBAnXngfQ1bTA8Ljw7N7KkDsjebY1o 1ExkmErSWLZ8e2X7ZZYPaeFVCmLlN0b/5+ICg/Bop1FwLzCwjm1jthjJcc0Llc2+9tmW S9CE+2DpzpUdiTA4h3QAWtD2Yj1gYwluYVjrquCESdfL97TJCyTXR9QGhsfuheIp+rWP riacUwm0v4dDL42Qjp462IOnmFdqV4Cmaunc0/30779RjNe5Ab828tIp0lOV6u8uO7NH mKGqossog/eHtiCNFhsbYNebrq9wsmyYlufQrZGLdi1lUY+5VeohrSVU71W0Lh7ocWc7 IRRw== X-Gm-Message-State: APjAAAWzdHCsui8mJP9TpvreMEPwhrUs+uwlcjQuZ+GCO9LTLq+OTW1k p6+bfaapTPo5p1copx1y4y8kEDdMs/4= X-Received: by 2002:aa7:86c2:: with SMTP id h2mr50096222pfo.45.1582528839386; Sun, 23 Feb 2020 23:20:39 -0800 (PST) Received: from localhost ([45.127.44.57]) by smtp.gmail.com with ESMTPSA id p24sm11375421pff.69.2020.02.23.23.20.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 23 Feb 2020 23:20:38 -0800 (PST) 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: [RFC PATCH v5 2/3] dt-bindings: thermal: Add yaml bindings for thermal cooling-devices Date: Mon, 24 Feb 2020 12:50:26 +0530 Message-Id: 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 | 114 ++++++++++++++++++ 1 file changed, 114 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..6aafca25af9b --- /dev/null +++ b/Documentation/devicetree/bindings/thermal/thermal-cooling-devices.yaml @@ -0,0 +1,114 @@ +# SPDX-License-Identifier: (GPL-2.0 OR MIT) +# 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. + +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