Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: linux-hwmon@vger.kernel.org
Cc: devicetree@vger.kernel.org, "Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	linux-kernel@vger.kernel.org, "Armin Wolf" <W_Armin@gmx.de>,
	"Thomas Weißschuh" <linux@weissschuh.net>,
	"René Rebe" <rene@exactcode.de>,
	"Guenter Roeck" <linux@roeck-us.net>
Subject: [PATCH v2 1/3] dt-bindings: hwmon: jedec,spd5118: Add bindings
Date: Thu, 30 May 2024 15:39:37 -0700	[thread overview]
Message-ID: <20240530223939.1027659-2-linux@roeck-us.net> (raw)
In-Reply-To: <20240530223939.1027659-1-linux@roeck-us.net>

Add device tree bindings for the SPD hub present in DDR5 modules.

Signed-off-by: Guenter Roeck <linux@roeck-us.net>
---
v2: Drop pec-enable property

 .../bindings/hwmon/jedec,spd5118.yaml         | 48 +++++++++++++++++++
 1 file changed, 48 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/hwmon/jedec,spd5118.yaml

diff --git a/Documentation/devicetree/bindings/hwmon/jedec,spd5118.yaml b/Documentation/devicetree/bindings/hwmon/jedec,spd5118.yaml
new file mode 100644
index 000000000000..05c39f7083db
--- /dev/null
+++ b/Documentation/devicetree/bindings/hwmon/jedec,spd5118.yaml
@@ -0,0 +1,48 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/hwmon/jedec,spd5118.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: JEDEC JESD300-5B (SPD5118) compatible DDR5 SPD hub
+
+maintainers:
+  - Guenter Roeck <linux@roeck-us.net>
+
+description: |
+  JEDEC JESD300-5B.01 SPD5118 Hub and Serial Presence Detect
+  https://www.jedec.org/standards-documents/docs/jesd300-5b01
+
+select:
+  properties:
+    compatible:
+      const: jedec,spd5118
+
+  required:
+    - compatible
+    - reg
+
+properties:
+  compatible:
+    const: jedec,spd5118
+
+  reg:
+    maxItems: 1
+
+required:
+  - compatible
+  - reg
+
+additionalProperties: false
+
+examples:
+  - |
+    i2c {
+        #address-cells = <1>;
+        #size-cells = <0>;
+
+        temp-sensor@51 {
+            compatible = "jedec,spd5118";
+            reg = <0x51>;
+        };
+    };
-- 
2.39.2


  reply	other threads:[~2024-05-30 22:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 22:39 [PATCH v2 2/3] hwmon: Add support for SPD5118 compliant temperature sensors Guenter Roeck
2024-05-30 22:39 ` Guenter Roeck [this message]
2024-05-31  8:15   ` [PATCH v2 1/3] dt-bindings: hwmon: jedec,spd5118: Add bindings Krzysztof Kozlowski
2024-05-31 13:09     ` Guenter Roeck
2024-05-31 13:14       ` Krzysztof Kozlowski
2024-05-30 22:39 ` [PATCH v2 2/3] hwmon: Add support for SPD5118 compliant temperature sensors Guenter Roeck
2024-05-30 22:39 ` [PATCH v2 3/3] hwmon: (spd5118) Add suspend/resume support Guenter Roeck
2024-05-30 22:51 ` [PATCH v2 2/3] hwmon: Add support for SPD5118 compliant temperature sensors 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=20240530223939.1027659-2-linux@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=W_Armin@gmx.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=rene@exactcode.de \
    --cc=robh@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