On Tue, Mar 17, 2020 at 11:01 AM Tim Harvey <tharvey@xxxxxxxxxxxxx> wrote:
>
> This patch adds documentation of device-tree bindings for the
> Gateworks System Controller (GSC).
>
> Signed-off-by: Tim Harvey <tharvey@xxxxxxxxxxxxx>
> ---
> v6:
> - fix commit message typo
> - drop invalid description from #interrupt-cells property
> - fix adc pattern property
> - add unit suffix
> - replace hwmon/adc with adc/channel
> - changed adc type to gw,mode
> - add unit suffix and drop ref for voltage-divider
> - add unit suffix for voltage-offset
> - moved fan to its own subnode with base register
>
> v5:
> - resolve dt_binding_check issues
>
> v4:
> - move to using pwm<n>_auto_point<m>_{pwm,temp} for FAN PWM
> - remove unncessary resolution/scaling properties for ADCs
> - update to yaml
> - remove watchdog
>
> v3:
> - replaced _ with -
> - remove input bindings
> - added full description of hwmon
> - fix unit address of hwmon child nodes
> ---
> .../devicetree/bindings/mfd/gateworks-gsc.yaml | 172 +++++++++++++++++++++
> 1 file changed, 172 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mfd/gateworks-gsc.yaml
>
> diff --git a/Documentation/devicetree/bindings/mfd/gateworks-gsc.yaml b/Documentation/devicetree/bindings/mfd/gateworks-gsc.yaml
> new file mode 100644
> index 00000000..e921e67
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/gateworks-gsc.yaml
> @@ -0,0 +1,172 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mfd/gateworks-gsc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Gateworks System Controller multi-function device
> +
> +description: |
> + The GSC is a Multifunction I2C slave device with the following submodules:
> + - Watchdog Timer
> + - GPIO
> + - Pushbutton controller
> + - Hardware Monitor with ADC's for temperature and voltage rails and
> + fan controller
> +
> +maintainers:
> + - Tim Harvey <tharvey@xxxxxxxxxxxxx>
> + - Robert Jones <rjones@xxxxxxxxxxxxx>
> +
> +properties:
> + $nodename:
> + pattern: "gsc@[0-9a-f]{1,2}"
> + compatible:
> + const: gw,gsc
> +
> + reg:
> + description: I2C device address
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + interrupt-controller: true
> +
> + "#interrupt-cells":
> + const: 1
> +
> + adc:
> + type: object
> + description: Optional Hardware Monitoring module
> +
> + properties:
> + compatible:
> + const: gw,gsc-adc
> +
> + "#address-cells":
> + const: 1
> +
> + "#size-cells":
> + const: 0
> +
> + patternProperties:
> + "^channel@[0-9]+$":
> + type: object
> + description: |
> + Properties for a single ADC which can report cooked values
> + (ie temperature sensor based on thermister), raw values
> + (ie voltage rail with a pre-scaling resistor divider).
> +
> + properties:
> + reg:
> + description: Register of the ADC
> + maxItems: 1
> +
> + label:
> + description: Name of the ADC input
> +
> + gw,mode:
> + description: |
> + conversion mode:
> + 0 - temperature, in C*10
> + 1 - pre-scaled voltage value
> + 2 - scaled voltage based on an optional resistor divider
> + and optional offset
> + allOf:
> + - $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [0, 1, 2]
> +
> + gw,voltage-divider-milli-ohms:
> + description: values of resistors for divider on raw ADC input
> + items:
> + - description: R1
> + - description: R2
Aren't there some constraints on the values? You could do something like this:
maxItems: 2
items:
minimum: 1
maximum: 2000
I know I said the way you have it is fine, but the example fails with
it like this. It's related to how we encode the DT data for validation
and some schema fixups we do to cut down on some boilerplate. We could
just fix the example (with <> around each value), but having
constraints is better.
> +
> + gw,voltage-offset-microvolt:
> + $ref: /schemas/types.yaml#/definitions/uint32
Can drop this as .*-microvolt has a defined type.
Are there some constraints?
> + description: |
> + A positive voltage offset to apply to a raw ADC
> + (ie to compensate for a diode drop).
> +
> + required:
> + - gw,mode
> + - reg
> + - label
> +
> + required:
> + - compatible
> + - "#address-cells"
> + - "#size-cells"
> +
> + fan:
fan-controller
Save 'fan' for if/when we have a node representing the fan itself.
> + type: object
> + description: Optional FAN controller
> +
> + properties:
> + compatible:
> + const: gw,gsc-fan
> +
> + base:
What happened to 'reg'? While inconsistent that adc doesn't have an
address, better that than inventing your own address property.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: The fan controller base address
> + maxItems: 1
> +
> + required:
> + - compatible
> + - base
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - interrupt-controller
> + - "#interrupt-cells"
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + gsc@20 {
> + compatible = "gw,gsc";
> + reg = <0x20>;
> + interrupt-parent = <&gpio1>;
> + interrupts = <4 GPIO_ACTIVE_LOW>;
> + interrupt-controller;
> + #interrupt-cells = <1>;
> +
> + adc {
> + compatible = "gw,gsc-adc";
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + channel@0 { /* A0: Board Temperature */
> + gw,mode = <0>;
> + reg = <0x00>;
> + label = "temp";
> + };
> +
> + channel@2 { /* A1: Input Voltage (raw ADC) */
> + gw,mode = <1>;
> + reg = <0x02>;
> + label = "vdd_vin";
> + gw,voltage-divider-milli-ohms = <22100 1000>;
> + gw,voltage-offset-microvolt = <800000>;
> + };
> +
> + channel@b { /* A2: Battery voltage */
> + gw,mode = <1>;
> + reg = <0x0b>;
> + label = "vdd_bat";
> + };
> + };
> +
> + fan {
> + compatible = "gw,gsc-fan";
> + base = <0x2c>;
> + };
> + };
> + };
> --
> 2.7.4
>
