Re: [PATCH v9 07/12] dt-bindings: mfd: Add a document for PECI client MFD
From: Lee Jones <hidden>
Date: 2018-12-21 14:48:03
Also in:
linux-doc, linux-hwmon, lkml, openbmc
On Tue, 18 Dec 2018, Jae Hyun Yoo wrote:
quoted hunk ↗ jump to hunk
This commit adds a dt-bindings document for PECI client MFD. Cc: Lee Jones <redacted> Cc: Rob Herring <robh+dt@kernel.org> Cc: Mark Rutland <mark.rutland@arm.com> Cc: Andrew Jeffery <redacted> Cc: James Feist <redacted> Cc: Jason M Biils <redacted> Cc: Joel Stanley <joel@jms.id.au> Cc: Vernon Mauery <redacted> Signed-off-by: Jae Hyun Yoo <redacted> Reviewed-by: Rob Herring <robh@kernel.org> --- .../bindings/mfd/intel-peci-client.txt | 34 +++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 Documentation/devicetree/bindings/mfd/intel-peci-client.txtdiff --git a/Documentation/devicetree/bindings/mfd/intel-peci-client.txt b/Documentation/devicetree/bindings/mfd/intel-peci-client.txt new file mode 100644 index 000000000000..5d1d5d0a552f --- /dev/null +++ b/Documentation/devicetree/bindings/mfd/intel-peci-client.txt@@ -0,0 +1,34 @@ +* Intel PECI client bindings + +PECI (Platform Environment Control Interface) is a one-wire bus interface that +provides a communication channel from PECI clients in Intel processors and +chipset components to external monitoring or control devices. PECI is designed +to support the following sideband functions: + +- Processor and DRAM thermal management +- Platform Manageability +- Processor Interface Tuning and Diagnostics +- Failure Analysis + +Required properties: +- compatible : Should be "intel,peci-client". +- reg : Should contain address of a client CPU. According to the PECI + specification, client addresses start from 0x30. + +Example: + peci-bus@0 { + compatible = "vendor,soc-peci"; + reg = <0x0 0x1000>; + #address-cells = <1>; + #size-cells = <0>; + + peci-client@30 { + compatible = "intel,peci-client"; + reg = <0x30>; + }; + + peci-client@31 { + compatible = "intel,peci-client"; + reg = <0x31>; + };
The PECI Client driver (masquerading as an MFD driver in this set) doesn't actually do anything special. Instead of detailing it here, register the child devices directly instead. -- Lee Jones [李琼斯] Linaro Services Technical Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog