devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Rob Herring <robh+dt@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Guenter Roeck <linux@roeck-us.net>
Subject: [RFC PATCH] dt/bindings: Add bindings for JC-42.4 compatible temperature sensors
Date: Sat,  2 Jul 2016 10:05:42 -0700	[thread overview]
Message-ID: <1467479142-8249-1-git-send-email-linux@roeck-us.net> (raw)

Provide generic bindings for all Jedec JC-42.4 compatible temperature
sensor chips.

Signed-off-by: Guenter Roeck <linux@roeck-us.net>
---
RFC to address:
- Is "jc-42-4" ok to use for JC-42.4 ?
- JC42.4 really specifies an SPD EEPROM with included temperature sensor.
  Is "jedec,jc42-4" appropriate, or should it rather be something like
  "jedec,jc-42-4-sensor" ?

 Documentation/devicetree/bindings/hwmon/jc42.txt | 42 ++++++++++++++++++++++++
 1 file changed, 42 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/hwmon/jc42.txt

diff --git a/Documentation/devicetree/bindings/hwmon/jc42.txt b/Documentation/devicetree/bindings/hwmon/jc42.txt
new file mode 100644
index 000000000000..2bd604a93430
--- /dev/null
+++ b/Documentation/devicetree/bindings/hwmon/jc42.txt
@@ -0,0 +1,42 @@
+Properties for Jedec JC-42.4 compatible temperature sensors
+
+Required properties:
+- compatible: May include a device-specific string consisting of the
+	      manufacturer and the name of the chip. A list of supported
+	      chip names follows.
+	      Must include "jedec,jc-42-4" for any Jedec JC-42.4 compatible
+	      temperature sensor.
+
+	      Supported chip names:
+		adt7408
+		at30ts00
+		at30tse004
+		cat6095
+		cat34ts02
+		max6604
+		mcp9804
+		mcp9805
+		mcp9808
+		mcp98243
+		mcp98244
+		mcp9843
+		se97
+		se98
+		stts2002
+		stts2004
+		stts3000
+		stts424
+		stts424e
+		tse2002
+		tse2004
+		ts3000
+		ts3001
+
+- reg: I2C address
+
+Example:
+
+temp-sensor@1a {
+	compatible = "jedec,jc-42-4";
+	reg = <0x18>;
+};
-- 
2.5.0

             reply	other threads:[~2016-07-02 17:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-02 17:05 Guenter Roeck [this message]
     [not found] ` <1467479142-8249-1-git-send-email-linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-07-05 15:48   ` [RFC PATCH] dt/bindings: Add bindings for JC-42.4 compatible temperature sensors Rob Herring
2016-07-05 16:30     ` 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=1467479142-8249-1-git-send-email-linux@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.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).