Chrome platform driver development
 help / color / mirror / Atom feed
From: Sung-Chi <lschyi@chromium.org>
Cc: Sung-Chi <lschyi@chromium.org>, "Lee Jones" <lee@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Benson Leung" <bleung@chromium.org>,
	"Guenter Roeck" <groeck@chromium.org>,
	"Thomas Weißschuh" <thomas@weissschuh.net>,
	"Jean Delvare" <jdelvare@suse.com>,
	devicetree@vger.kernel.org, chrome-platform@lists.linux.dev,
	linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org
Subject: [PATCH v2 2/2] dt-bindings: mfd: Add properties for thermal sensor cells
Date: Mon, 11 Nov 2024 17:50:31 +0800	[thread overview]
Message-ID: <20241111095045.1218986-2-lschyi@chromium.org> (raw)
In-Reply-To: <20241111095045.1218986-1-lschyi@chromium.org>

The cros_ec supports reading thermal values from thermal sensors
connect to it. Add the property '#thermal-sensor-cells' bindings, such
that thermal framework can recognize cros_ec as a valid thermal device.

Change-Id: I95a22c0f1a69de547fede5f0f9c43cbd60820789
Signed-off-by: Sung-Chi <lschyi@chromium.org>
---
 Changes in v2:
   - Add changes for DTS binding.
---
 Documentation/devicetree/bindings/mfd/google,cros-ec.yaml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml b/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
index aac8819bd00b..c7d63e3aacd2 100644
--- a/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
+++ b/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
@@ -96,6 +96,9 @@ properties:
   '#gpio-cells':
     const: 2
 
+  '#thermal-sensor-cells':
+    const: 1
+
   gpio-controller: true
 
   typec:
-- 
2.47.0.277.g8800431eea-goog


  reply	other threads:[~2024-11-11  9:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-11  7:49 [PATCH] hwmon: (cros_ec) register thermal sensors to thermal framework Sung-Chi, Li
2024-11-11  8:16 ` Thomas Weißschuh
2024-11-11  9:50 ` [PATCH v2] " Sung-Chi
2024-11-11  9:50   ` Sung-Chi [this message]
2024-11-11 20:08     ` [PATCH v2 2/2] dt-bindings: mfd: Add properties for thermal sensor cells Conor Dooley
2024-11-11 16:30   ` [PATCH v2] hwmon: (cros_ec) register thermal sensors to thermal framework Thomas Weißschuh
2024-11-11 17:01   ` Guenter Roeck
2024-11-12  7:42     ` Sung-Chi, Li
2024-11-13  2:39 ` [PATCH v3 1/2] " Sung-Chi, Li
2024-11-13  2:39   ` [PATCH v3 2/2] dt-bindings: mfd: Add properties for thermal sensor cells Sung-Chi, Li
2024-11-13  3:05     ` Guenter Roeck
2024-11-25  8:52       ` Krzysztof Kozlowski
2024-11-25  8:54         ` Krzysztof Kozlowski
2024-11-25 15:13         ` Guenter Roeck
2024-11-25 15:18           ` Krzysztof Kozlowski
2024-11-25 16:41             ` Guenter Roeck
2024-11-25 17:12               ` Krzysztof Kozlowski
2024-11-13  3:04   ` [PATCH v3 1/2] hwmon: (cros_ec) register thermal sensors to thermal framework Guenter Roeck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241111095045.1218986-2-lschyi@chromium.org \
    --to=lschyi@chromium.org \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=groeck@chromium.org \
    --cc=jdelvare@suse.com \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=thomas@weissschuh.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox