From: Li-hao Kuo <lhjeff911@gmail.com>
To: rafael@kernel.org, daniel.lezcano@linaro.org, amitk@kernel.org,
rui.zhang@intel.com, robh+dt@kernel.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: wells.lu@sunplus.com, lh.kuo@sunplus.com,
Li-hao Kuo <lhjeff911@gmail.com>
Subject: [PATCH v3 2/2] devicetree: bindings THERMAL Add bindings doc for Sunplus SP7021
Date: Tue, 4 Jan 2022 10:58:57 +0800 [thread overview]
Message-ID: <e1466d52cd4c3971292ec8230df27faf372c2044.1641264908.git.lhjeff911@gmail.com> (raw)
In-Reply-To: <cover.1641264908.git.lhjeff911@gmail.com>
In-Reply-To: <cover.1641264908.git.lhjeff911@gmail.com>
Add devicetree bindings THERMAL Add bindings doc for Sunplus SP7021
Signed-off-by: Li-hao Kuo <lhjeff911@gmail.com>
---
Changes in v3:
- Modify Theraml driver
.../bindings/thermal/sunplus_thermal.yaml | 49 ++++++++++++++++++++++
MAINTAINERS | 1 +
2 files changed, 50 insertions(+)
create mode 100644 Documentation/devicetree/bindings/thermal/sunplus_thermal.yaml
diff --git a/Documentation/devicetree/bindings/thermal/sunplus_thermal.yaml b/Documentation/devicetree/bindings/thermal/sunplus_thermal.yaml
new file mode 100644
index 0000000..e0290fa
--- /dev/null
+++ b/Documentation/devicetree/bindings/thermal/sunplus_thermal.yaml
@@ -0,0 +1,49 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+# Copyright (C) Sunplus Co., Ltd.
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/thermal/sunplus_thermal.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Sunplus Thermal controller
+
+maintainers:
+ - Li-hao Kuo <lhjeff911@gmail.com>
+
+properties:
+ compatible:
+ enum:
+ - sunplus,sp7021-thermal
+
+ reg:
+ maxItems: 1
+
+ reg-names:
+ items:
+ - const: reg
+ - const: moon4
+
+ nvmem-cells:
+ maxItems: 1
+
+ nvmem-cell-names:
+ const: therm_calib
+
+required:
+ - compatible
+ - reg
+ - reg-names
+ - nvmem-cells
+ - nvmem-cell-names
+
+additionalProperties: false
+
+examples:
+ - |
+ thermal@9c000280 {
+ compatible = "sunplus,sp7021-thermal";
+ reg = <0x9c000280 0x80>;
+ nvmem-cells = <&therm_calib>;
+ nvmem-cell-names = "therm_calib";
+ };
+...
diff --git a/MAINTAINERS b/MAINTAINERS
index 4b02628..dd1b7bf 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -18246,6 +18246,7 @@ SUNPLUS THERMAL DRIVER
M: Li-hao Kuo <lhjeff911@gmail.com>
L: linux-pm@vger.kernel.org
S: Maintained
+F: Documentation/devicetree/bindings/thermal/sunplus_thermal.yaml
F: drivers/thermal/sunplus_thermal.c
SUPERH
--
2.7.4
next prev parent reply other threads:[~2022-01-04 2:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 2:58 [PATCH v3 0/2] Add THERMAL control driver for Sunplus SP7021 SoC Li-hao Kuo
2022-01-04 2:58 ` [PATCH v3 1/2] THERMAL: Add THERMAL driver for Sunplus SP7021 Li-hao Kuo
2022-01-04 2:58 ` Li-hao Kuo [this message]
2022-01-11 23:09 ` [PATCH v3 2/2] devicetree: bindings THERMAL Add bindings doc " Rob Herring
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=e1466d52cd4c3971292ec8230df27faf372c2044.1641264908.git.lhjeff911@gmail.com \
--to=lhjeff911@gmail.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=lh.kuo@sunplus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=wells.lu@sunplus.com \
/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;
as well as URLs for NNTP newsgroup(s).