Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp2130898ybv; Sun, 23 Feb 2020 23:26:01 -0800 (PST) X-Google-Smtp-Source: APXvYqzOgY9cyPV9W0NkZnsU/wdXlGHHGnWm4bVtfcpmnqT4Y5kSniOYq3++6BFAbpANlAjClC+h X-Received: by 2002:a05:6830:15c2:: with SMTP id j2mr21981290otr.351.1582529161326; Sun, 23 Feb 2020 23:26:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582529161; cv=none; d=google.com; s=arc-20160816; b=QaJ/U9ADaIx28wkOpAP1jfSA460OuMG7anl6MUmH0A/Yzl0xAbwhDlfDN6JJsK0hiY oMSxdFQRcKhA62TImLq7hrwmFCDZANhuzuwoI9fBxZ0/R0Y+YHgFwY35lSahbEnkryWp O3xB7gZHtBLsl0Qzj8os3R+I5WRVx++08EvtTrbAGZKFFCI9uvIAA6Wt+sAU1iAyLmFI AyLVXkCC8YDAAU97YI3CSAZ8j9kt1YbWMai93x07u0UfCfx2IMrK9cI8Rgmz20dMNwse i/gPwk2UFgydAuHzdZRv6hZOelRiqqBHpNFLeQya55EBXYjnHWvGhyzqtchejVfhk30A QMPQ== 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 :message-id:date:subject:cc:to:from:dkim-signature; bh=Pjmsw2c59UnP8bQTcR0v67l8n2Do0c3ipHd2w0BLgDw=; b=TFJeudTKvhRomVgzosCvh61TtfIs8OWOTPkq1jy+0MsvhFnBEtpDbmtHCPx2VWMgvH SbNP3VyZsCHENpN5K9NQOVbDyjqmuNOmrt9APHAI6qijdwFywaW4+QfxPBOtwXCfz5lP vOkjBb5Si1g2qdvdoQ/cTRzq7lsne7F5fql45AOhLVmSzB6vxTlWPNoM6gNGohWjns16 +QlbrcE141W1b8CaWX2ihERuu6xun1BT4AH8k4kGffm62GMbb4VyG/c9blpIki/BtEf1 91/4xOud8T7UI4Gpe4gXn1Z9BPc4R39miUvVrKSat4D9fXLaoJQdMsE3vonRCk9TZbxJ 49fQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=UAvCFsUk; 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 i5si4941148oif.211.2020.02.23.23.25.48; Sun, 23 Feb 2020 23:26:01 -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=UAvCFsUk; 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 S1727185AbgBXHZn (ORCPT + 99 others); Mon, 24 Feb 2020 02:25:43 -0500 Received: from mail-pl1-f195.google.com ([209.85.214.195]:41877 "EHLO mail-pl1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726778AbgBXHZn (ORCPT ); Mon, 24 Feb 2020 02:25:43 -0500 Received: by mail-pl1-f195.google.com with SMTP id t14so3682284plr.8 for ; Sun, 23 Feb 2020 23:25:43 -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:mime-version :content-transfer-encoding; bh=Pjmsw2c59UnP8bQTcR0v67l8n2Do0c3ipHd2w0BLgDw=; b=UAvCFsUkzi4NHTluHdWcn5wDT40ImYUMrkXDGvP+rlkh34aMNX7VR3G6cWJsG+C5kv VBXTaD07DS2Ntcv58V5c1jaoS+2kQSHxDDmLxOZ4MhBqVL+l7ozf3PlwOJYLy9Axl8QC raFopR/h6T4KN2OeT8yN+bdaxAvNCupz0mfDAv5/sdtuZjq7mSeAPkLD8VokSpzm3FSb XlfPvxQm2Rcbvwm+AusMJbH6xWMYEGJCldE481V0edXktO8xO3HyvQgC/Ni7+Jtb6wZh 3MJ2Y9HI9QOABI4QjFkzEWy5Tglwf/5nGxtvr+SywIIkbcHru4PQnZ5rnMLXFcBXTTup ePPA== 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:mime-version :content-transfer-encoding; bh=Pjmsw2c59UnP8bQTcR0v67l8n2Do0c3ipHd2w0BLgDw=; b=bqiu2JZlGDKZy4YTBYEN1f8DX4CT9szDZEmheNkEc1RF5HRPSRcs14HrzfOGu+6IEX QHHoy5EMexjr4jP9i/F4G6qicrq0o7Y/iaHZx5ln9Fk9mWKAVqS8MjtZffy4fBqiFA0X 6LKO3hwgX85FjE63cvt28PCE6L0Us+1S0n+I/pf8NIz2ne3nzN8obaYHEigGbTnEB4AN 7c5oL/+E/3WJLUARri7CBL5iXmrz1qxIIfGxW8AH+6zgLiXPrv6aKD5v7ITjQZuj/YmO oeUsjdDBrFEEu+7cMzEXfcvxH9GyQ/EoEEIsn/6oD08RjF+HA9GK2+89qfI7T2nmnI1k H4Ew== X-Gm-Message-State: APjAAAXkpuY5Fh5wWM+ageXSL8J8guNjyUnmNoB9YmqYdrJEoLYrVVuo nfCAgxnqx7117EEFiWmhadfc8ZsdeCM= X-Received: by 2002:a17:90a:d801:: with SMTP id a1mr19064921pjv.34.1582529142409; Sun, 23 Feb 2020 23:25:42 -0800 (PST) Received: from localhost ([45.127.44.57]) by smtp.gmail.com with ESMTPSA id e6sm11360185pfh.32.2020.02.23.23.25.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 23 Feb 2020 23:25:41 -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: devicetree@vger.kernel.org, linux-pm@vger.kernel.org Subject: [RFC PATCH v1 0/3] Convert thermal bindings to yaml Date: Mon, 24 Feb 2020 12:55:34 +0530 Message-Id: X-Mailer: git-send-email 2.20.1 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 Hi all, Here is a series splitting up the thermal bindings into 3 separate bindings in YAML, one each of the sensor, cooling-device and the thermal zones. Since I was learning about YAML parsers while creating these bindings, there are bound to be some issues. I have to add that the bindings as they exist today, don't really follow the "describe the hardware" model of devicetree. e.g. the entire thermal-zone binding is a software abstraction to tie arbitrary, board-specific trip points to cooling strategies. This doesn't fit well into the model where the same SoC in two different form-factor devices e.g. mobile and laptop, will have fairly different thermal profiles and might benefit from different trip points and mitigation heuristics. I've started some experiments with moving the thermal zone data to a board-specific platform data that is used to initialise a "thermal zone driver". In any case, if we ever move down that path, it'll probably end up being v2 of the binding, so this series is still relevant. Please help review. Regards, Amit Amit Kucheria (3): dt-bindings: thermal: Add yaml bindings for thermal sensors dt-bindings: thermal: Add yaml bindings for thermal cooling-devices dt-bindings: thermal: Add yaml bindings for thermal zones .../thermal/thermal-cooling-devices.yaml | 114 +++++++ .../bindings/thermal/thermal-sensor.yaml | 70 ++++ .../bindings/thermal/thermal-zones.yaml | 302 ++++++++++++++++++ 3 files changed, 486 insertions(+) create mode 100644 Documentation/devicetree/bindings/thermal/thermal-cooling-devices.yaml create mode 100644 Documentation/devicetree/bindings/thermal/thermal-sensor.yaml create mode 100644 Documentation/devicetree/bindings/thermal/thermal-zones.yaml -- 2.20.1