Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp2127379ybv; Sun, 23 Feb 2020 23:20:57 -0800 (PST) X-Google-Smtp-Source: APXvYqzD7EIRqvzuZDpk41p7mDRwDzvJQynBbQs7smCjGJwfNayhiiuYWwD2A5XZblXkSWW88ksp X-Received: by 2002:a9d:5e8b:: with SMTP id f11mr25879283otl.110.1582528857682; Sun, 23 Feb 2020 23:20:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582528857; cv=none; d=google.com; s=arc-20160816; b=h1HUo00b8pdhLF0xyDUNBk6AsqJ/TlHVArvTOohUr+ZriMQJpvBGULrCkHcb/aBAPB ieRR5fXG/SuwOXgt5Z1q8UNA4PhmYBen8A5E++3NLyplw8EJL1x61KO25kwUyWLe8oXn QZGEJ1b79vpBDGvKkofX1xxZQJ1TPWrcvaECZSSfKLhMOLVlrSGo9ev1JJDEoZhBCrGl E+aFSY7Ejrx5M69gInXrsF/pVPFld686Sbv8B+y20NqN7KxZZPFS4oUXknAq334JwKFZ qOQbs1jI5IZM8ybdFz36LDefFNAq6PaUyDo1Az6VmzTNzqemaXa4b8ZrNG2x732o0ty+ 6i9g== 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=Pp4OJKlkTUP/JKWBsfGX5IGPygvYeWUCLyYPIlFud78=; b=PNX8kTDVKTrlWmm6DbMyhb/sCUIYRJ8C66Xnfe+pKj6vnZ5x6BQOP3YvZ/pG+HsQA/ h0oy2p9fF6cuToYrst9esbY0AjfJPplRokZNQMxFrZH5XolGWnqV9TwaJR5gV40IcCe6 Usf1b9z13cUCQKwLJHQY52Odo8zOjkAFl0DvZpQbX41x6QRFiZxxNrPuTmiUuyvt3w+u yKCGIVDJeqjJd0mJx3kx2k7y+P+zw4VTYtsE7LIn6zvOv8/z5h24jZfaD/b54niIYBY0 vNLe2B5VCQhqACVxGVmy06LHdDBUKq4ctT/vhbL6WK33ADf27/xYtjQdweaLCHdQ0YQD /HyQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=IZOmGdk3; 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 m26si5751735otr.159.2020.02.23.23.20.44; Sun, 23 Feb 2020 23:20:57 -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=IZOmGdk3; 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 S1727168AbgBXHUe (ORCPT + 99 others); Mon, 24 Feb 2020 02:20:34 -0500 Received: from mail-pj1-f65.google.com ([209.85.216.65]:50375 "EHLO mail-pj1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726709AbgBXHUe (ORCPT ); Mon, 24 Feb 2020 02:20:34 -0500 Received: by mail-pj1-f65.google.com with SMTP id r67so3781326pjb.0 for ; Sun, 23 Feb 2020 23:20:32 -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=Pp4OJKlkTUP/JKWBsfGX5IGPygvYeWUCLyYPIlFud78=; b=IZOmGdk3jvbALg78q+Ogcc/os8rR7kNvGziTpMuqqxVshDSb7T0/n5kLOgxiYvrD6L FsaIT/opnfyAbJqctDkl/nSg+/poz+r/XpgrWrCj0upAr29DF+L7hRl6W4XhxLudNiZy mQLaah2Y3ds1XjtYfOSm9hQLGA8Fp+1cwAg+ZoVnIAJkSf+i0RN6yxwnEfj9WAoj1QP9 3cCkaSDjwRYAy9gTaNUU81Rp+oHJn4ppYGFivh0T0knTRTQnKpNsuGoto8fVCwI2NNKS N78wCh30Yi+vNrdi6ujUkU1bDTZ7+FjVlQRwtYpE3nNUngzpsG5Jp9vpFUfwl1Z8H12w 8FnQ== 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=Pp4OJKlkTUP/JKWBsfGX5IGPygvYeWUCLyYPIlFud78=; b=oiFjbJ4UCR8GjQKVcfcXVZe+WPcuOzMzuJRdQox7HOrZTY19My+ElfvE69U4zlZArr X8LaHS65v8+grb4BT1BA019U5L/yYgsgesZu/Ru5v3XMBXmQkNyOulQ1SMRoI9iR/uKu 4M640sQjflQyY0+TAPGNjahcVWXM4hbRFy98BY3FJB8FlJ2SNUodhjzxvXM7JVEBws5l 98JzWVvKqHWkCqZJ9p2ZBFrdU10AZ8UxUvF7KXYdrzLOeuGwAvNwiXWfycuXpmv3KsHx bq+b7lRxUX21zC/7UlfP1tXwpPkWP2Tu/bohrAJjLjQ3+lap1TRRJl9tuOM4+E+JEPQR U+og== X-Gm-Message-State: APjAAAXSTD28LUgDqCb11MoKsuXrHeW4/qdwYw2M0zOCp08WwBoIisjE oON2z3r/jdy9rgR8VVRGZbbV/38tBXI= X-Received: by 2002:a17:90b:4396:: with SMTP id in22mr18082228pjb.83.1582528831644; Sun, 23 Feb 2020 23:20:31 -0800 (PST) Received: from localhost ([45.127.44.57]) by smtp.gmail.com with ESMTPSA id p23sm11452767pgn.92.2020.02.23.23.20.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 23 Feb 2020 23:20:30 -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 v5 0/3] Convert thermal bindings to yaml Date: Mon, 24 Feb 2020 12:50:24 +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