* [RFC PATCH] dt/bindings: Add bindings for JC-42.4 compatible temperature sensors
@ 2016-07-02 17:05 Guenter Roeck
2016-07-05 15:48 ` Rob Herring
0 siblings, 1 reply; 5+ messages in thread
From: Guenter Roeck @ 2016-07-02 17:05 UTC (permalink / raw)
To: Rob Herring; +Cc: Mark Rutland, devicetree, linux-kernel, Guenter Roeck
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
^ permalink raw reply related [flat|nested] 5+ messages in thread* Re: [RFC PATCH] dt/bindings: Add bindings for JC-42.4 compatible temperature sensors
@ 2016-07-05 15:48 ` Rob Herring
0 siblings, 0 replies; 5+ messages in thread
From: Rob Herring @ 2016-07-05 15:48 UTC (permalink / raw)
To: Guenter Roeck; +Cc: Mark Rutland, devicetree, linux-kernel
On Sat, Jul 02, 2016 at 10:05:42AM -0700, Guenter Roeck wrote:
> 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.
That would be at a different address?
> Is "jedec,jc42-4" appropriate, or should it rather be something like
> "jedec,jc-42-4-sensor" ?
If yes, then probably the latter. Though I would do "temp" rather than
"sensor".
Also, "-42.4" is fine.
> 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
These are all vendor independent names?
> +
> +- reg: I2C address
> +
> +Example:
> +
> +temp-sensor@1a {
> + compatible = "jedec,jc-42-4";
> + reg = <0x18>;
> +};
> --
> 2.5.0
>
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [RFC PATCH] dt/bindings: Add bindings for JC-42.4 compatible temperature sensors
@ 2016-07-05 15:48 ` Rob Herring
0 siblings, 0 replies; 5+ messages in thread
From: Rob Herring @ 2016-07-05 15:48 UTC (permalink / raw)
To: Guenter Roeck
Cc: Mark Rutland, devicetree-u79uwXL29TY76Z2rM5mHXA,
linux-kernel-u79uwXL29TY76Z2rM5mHXA
On Sat, Jul 02, 2016 at 10:05:42AM -0700, Guenter Roeck wrote:
> Provide generic bindings for all Jedec JC-42.4 compatible temperature
> sensor chips.
>
> Signed-off-by: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
> ---
> 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.
That would be at a different address?
> Is "jedec,jc42-4" appropriate, or should it rather be something like
> "jedec,jc-42-4-sensor" ?
If yes, then probably the latter. Though I would do "temp" rather than
"sensor".
Also, "-42.4" is fine.
> 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
These are all vendor independent names?
> +
> +- reg: I2C address
> +
> +Example:
> +
> +temp-sensor@1a {
> + compatible = "jedec,jc-42-4";
> + reg = <0x18>;
> +};
> --
> 2.5.0
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [RFC PATCH] dt/bindings: Add bindings for JC-42.4 compatible temperature sensors
2016-07-05 15:48 ` Rob Herring
@ 2016-07-05 16:30 ` Guenter Roeck
-1 siblings, 0 replies; 5+ messages in thread
From: Guenter Roeck @ 2016-07-05 16:30 UTC (permalink / raw)
To: Rob Herring; +Cc: Mark Rutland, devicetree, linux-kernel
On 07/05/2016 08:48 AM, Rob Herring wrote:
> On Sat, Jul 02, 2016 at 10:05:42AM -0700, Guenter Roeck wrote:
>> 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.
>
> That would be at a different address?
>
Yes. The EEPROM is at address 0x5[0-7], the temperature sensor is at 0x1[8-f].
>> Is "jedec,jc42-4" appropriate, or should it rather be something like
>> "jedec,jc-42-4-sensor" ?
>
> If yes, then probably the latter. Though I would do "temp" rather than
> "sensor".
>
> Also, "-42.4" is fine.
>
Ok, I'll use "jedec,jc-42.4-temp".
>> 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
>
> These are all vendor independent names?
>
No. se97/se98 would be NXP, for example. I'll add the vendor prefixes.
Thanks,
Guenter
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [RFC PATCH] dt/bindings: Add bindings for JC-42.4 compatible temperature sensors
@ 2016-07-05 16:30 ` Guenter Roeck
0 siblings, 0 replies; 5+ messages in thread
From: Guenter Roeck @ 2016-07-05 16:30 UTC (permalink / raw)
To: Rob Herring
Cc: Mark Rutland, devicetree-u79uwXL29TY76Z2rM5mHXA,
linux-kernel-u79uwXL29TY76Z2rM5mHXA
On 07/05/2016 08:48 AM, Rob Herring wrote:
> On Sat, Jul 02, 2016 at 10:05:42AM -0700, Guenter Roeck wrote:
>> Provide generic bindings for all Jedec JC-42.4 compatible temperature
>> sensor chips.
>>
>> Signed-off-by: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
>> ---
>> 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.
>
> That would be at a different address?
>
Yes. The EEPROM is at address 0x5[0-7], the temperature sensor is at 0x1[8-f].
>> Is "jedec,jc42-4" appropriate, or should it rather be something like
>> "jedec,jc-42-4-sensor" ?
>
> If yes, then probably the latter. Though I would do "temp" rather than
> "sensor".
>
> Also, "-42.4" is fine.
>
Ok, I'll use "jedec,jc-42.4-temp".
>> 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
>
> These are all vendor independent names?
>
No. se97/se98 would be NXP, for example. I'll add the vendor prefixes.
Thanks,
Guenter
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2016-07-05 16:31 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-07-02 17:05 [RFC PATCH] dt/bindings: Add bindings for JC-42.4 compatible temperature sensors Guenter Roeck
2016-07-05 15:48 ` Rob Herring
2016-07-05 15:48 ` Rob Herring
2016-07-05 16:30 ` Guenter Roeck
2016-07-05 16:30 ` Guenter Roeck
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.