From: "Rafał Miłecki" <zajec5@gmail.com>
To: Zhang Rui <rui.zhang@intel.com>, Eduardo Valentin <edubezval@gmail.com>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Scott Branden" <sbranden@broadcom.com>,
"Stephen Warren" <swarren@wwwdotorg.org>,
"Ray Jui" <rjui@broadcom.com>,
linux-pm@vger.kernel.org, "Lee Jones" <lee@kernel.org>,
"Eric Anholt" <eric@anholt.net>,
"Rob Herring" <robh+dt@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
"Rafał Miłecki" <rafal@milecki.pl>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] dt-bindings: thermal: add support for Raspberry Pi thermal
Date: Sat, 18 Mar 2017 01:01:31 +0100 [thread overview]
Message-ID: <20170318000132.9212-1-zajec5@gmail.com> (raw)
From: Rafał Miłecki <rafal@milecki.pl>
This commit documents binding for BCM2835 SoC thermal used in Raspberry
Pi devices.
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
---
.../bindings/thermal/raspberrypi,bcm2835-thermal | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
create mode 100644 Documentation/devicetree/bindings/thermal/raspberrypi,bcm2835-thermal
diff --git a/Documentation/devicetree/bindings/thermal/raspberrypi,bcm2835-thermal b/Documentation/devicetree/bindings/thermal/raspberrypi,bcm2835-thermal
new file mode 100644
index 000000000000..fbffa9291ba9
--- /dev/null
+++ b/Documentation/devicetree/bindings/thermal/raspberrypi,bcm2835-thermal
@@ -0,0 +1,17 @@
+* Broadcom BCM2835 SoC Raspberry Pi Thermal
+
+This binding describes thermal sensor that is part of BCM2835 SoC.
+
+Required properties:
+- compatible : Must be "raspberrypi,bcm2835-thermal"
+- firmware : Reference to the Raspberry Pi firmware device node, see
+ raspberrypi,bcm2835-firmware for details
+- #thermal-sensor-cells : Should be <0>
+
+Example:
+
+thermal {
+ compatible = "raspberrypi,bcm2835-thermal";
+ firmware = <&firmware>;
+ #thermal-sensor-cells = <0>;
+};
--
2.11.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2017-03-18 0:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 0:01 Rafał Miłecki [this message]
2017-03-18 0:01 ` [PATCH 2/2] thermal: broadcom: add Raspberry Pi thermal driver Rafał Miłecki
[not found] ` <20170318000132.9212-1-zajec5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-03-18 0:06 ` [PATCH V2 1/2] dt-bindings: thermal: add support for Raspberry Pi thermal Rafał Miłecki
[not found] ` <20170318000603.10158-1-zajec5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-03-18 0:06 ` [PATCH V2 2/2] thermal: broadcom: add Raspberry Pi thermal driver Rafał Miłecki
2017-03-18 0:09 ` [PATCH 1/2] dt-bindings: thermal: add support for Raspberry Pi thermal Eric Anholt
2017-03-18 8:58 ` Rafał Miłecki
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=20170318000132.9212-1-zajec5@gmail.com \
--to=zajec5@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=rafal@milecki.pl \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=sbranden@broadcom.com \
--cc=swarren@wwwdotorg.org \
/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).