From: Guenter Roeck <linux@roeck-us.net>
To: Tim Harvey <tharvey@gateworks.com>
Cc: Lee Jones <lee.jones@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mark Brown <broonie@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Wim Van Sebroeck <wim@iguana.be>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-hwmon@vger.kernel.org, linux-input@vger.kernel.org,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v3 1/4] dt-bindings: mfd: Add Gateworks System Controller bindings
Date: Wed, 28 Mar 2018 09:24:16 -0700 [thread overview]
Message-ID: <20180328162416.GB25325@roeck-us.net> (raw)
In-Reply-To: <1522250043-8065-2-git-send-email-tharvey@gateworks.com>
On Wed, Mar 28, 2018 at 08:14:00AM -0700, Tim Harvey wrote:
> This patch adds documentation of device-tree bindings for the
> Gateworks System Controller (GSC).
>
> Signed-off-by: Tim Harvey <tharvey@gateworks.com>
> ---
> v3:
> - replaced _ with -
> - remove input bindings
> - added full description of hwmon
> - fix unit address of hwmon child nodes
>
> ---
> .../devicetree/bindings/mfd/gateworks-gsc.txt | 135 +++++++++++++++++++++
> 1 file changed, 135 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mfd/gateworks-gsc.txt
>
> diff --git a/Documentation/devicetree/bindings/mfd/gateworks-gsc.txt b/Documentation/devicetree/bindings/mfd/gateworks-gsc.txt
> new file mode 100644
> index 0000000..8f530ed
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/gateworks-gsc.txt
> @@ -0,0 +1,135 @@
> +Gateworks System Controller multi-function device
> +
> +The GSC is a Multifunction I2C slave device with the following submodules:
> +- WDT
> +- GPIO
> +- Pushbutton controller
> +- HWMON
> +
> +Required properties:
> +- compatible : Must be "gw,gsc"
> +- reg: I2C address of the device
> +- interrupts: interrupt triggered by GSC_IRQ# signal
> +- interrupt-parent: Interrupt controller GSC is connected to
> +- #interrupt-cells: should be <1>, index of the interrupt within the
> + controller, in accordance with the "one cell" variant of
> + <devicetree/bindings/interrupt-controller/interrupt.txt>
> +
> +Optional nodes:
> +* watchdog:
> +The GSC provides a Watchdog monitor which can power cycle the board's
> +primary power supply on most board models when tripped.
> +
> +Required watchdog properties:
> +- compatible: must be "gw,gsc-watchdog"
> +
> +* hwmon:
> +The GSC provides a set of Analog to Digitcal Converter (ADC) pins used for
> +temperature and/or voltage monitoring.
> +
> +Required hwmon properties:
> +- compatible: must be "gw,gsc-hwmon"
> +
"hwmon" is a very Linux specific term. It might make sense to find a more
generic term.
> +Optional hwmon properties:
> +- gw,reference-voltage: ADC reference voltage (mV) used in scaling raw ADCs
AFAIK devicetree likes to specify voltages in uV.
> +- gw,resolution: ADC resolution (ie 4096) used in scaling raw ADCs
> +
4096 what ?
> +Each hwmon child node defines an ADC input on the chip which the GSC may
> +report cooked values (ie temperature sensor based on thermister), raw values,
> +(ie voltage rail with a pre-scaling resistor divider), or a fan controller
> +setpoint.
> +
> +Required hwmon child properties:
> +- type: one of the following ADC types:
> + "gw,hwmon-temperature" - reports temperature in C*10
> + "gw,hwmon-voltage" - reports a pre-scaled voltage value
> + "gw,hwmon-voltage-raw" - reports a raw ADC that is scaled with
> + vreference, resolution, and optional resistor divider
> + "gw,hwmon-fan" - a fan temperature setpoint in C*10
What is a "fan temperature setpoint" ?
> +- reg: offset of the ADC register
> +- label: name of the ADC input or FAN setpoint
> +
> +Optional hwmon child properties:
> +- gw,voltage-divider: An array of two integers containing the resistor
> + values R1 and R2 of the optinal resistor divider on a raw ADC
> +- gw,voltage-offset: a mV voltage offset to apply to a raw ADC (ie to
> + compensate for a diode drop)
> +
> +Example:
> +
> + gsc: gsc@20 {
> + compatible = "gw,gsc";
> + reg = <0x20>;
> + interrupt-parent = <&gpio1>;
> + interrupts = <4 GPIO_ACTIVE_LOW>;
> + interrupt-controller;
> + #interrupt-cells = <1>;
> +
> + watchdog {
> + compatible = "gw,gsc-watchdog";
> + };
> +
> + hwmon {
> + compatible = "gw,gsc-hwmon";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + gw,reference-voltage = <2500>;
> + gw,resolution = <4096>;
> +
> + hwmon@0 { /* A0: Board Temperature */
> + type = "gw,hwmon-temperature";
> + reg = <0x00>;
> + label = "temp";
> + };
> +
> + hwmon@2 { /* A1: Input Voltage (raw ADC) */
> + type = "gw,hwmon-voltage-raw";
> + reg = <0x02>;
> + label = "vdd_vin";
> + gw,voltage-divider = <22100 1000>;
> + gw,voltage-offset = <800>;
> + };
> +
> + hwmon@b { /* A2: Battery voltage */
> + type = "gw,hwmon-voltage";
> + reg = <0x0b>;
> + label = "vdd_bat";
> + };
> +
> + hwmon@2c { /* fan temperature setpoint for 50% duty */
> + type = "gw,hwmon-fan";
> + reg = <0x2c>;
> + label = "fan_50p";
> + };
> +
> + hwmon@2e { /* fan1 */
> + type = "gw,hwmon-fan";
> + reg = <0x2e>;
> + label = "fan_60p";
> + };
> +
> + hwmon@30 { /* fan2 */
> + type = "gw,hwmon-fan";
> + reg = <0x30>;
> + label = "fan_70p";
> + };
> +
> + hwmon@32 { /* fan3 */
> + type = "gw,hwmon-fan";
> + reg = <0x32>;
> + label = "fan_80p";
> + };
> +
> + hwmon@34 { /* fan4 */
> + type = "gw,hwmon-fan";
> + reg = <0x34>;
> + label = "fan_90p";
> + };
> +
> + hwmon@36 { /* fan5 */
> + type = "gw,hwmon-fan";
> + reg = <0x36>;
> + label = "fan_100p";
> + };
No idea what this is supposed to be doing, but whatever it is,
it appears to be wrong. I'll comment more on it in the hwmon driver.
Guenter
> + };
> + };
> --
> 2.7.4
>
next prev parent reply other threads:[~2018-03-28 16:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 15:13 [PATCH v3 0/4] Add support for the Gateworks System Controller Tim Harvey
2018-03-28 15:14 ` [PATCH v3 1/4] dt-bindings: mfd: Add Gateworks System Controller bindings Tim Harvey
2018-03-28 16:24 ` Guenter Roeck [this message]
2018-03-28 19:17 ` Tim Harvey
2018-03-28 20:23 ` Guenter Roeck
2018-03-28 20:53 ` Tim Harvey
2018-04-09 19:24 ` Rob Herring
2018-03-28 15:14 ` [PATCH v3 2/4] mfd: add Gateworks System Controller core driver Tim Harvey
2018-04-03 15:48 ` Tim Harvey
2018-04-03 16:47 ` Andrew Lunn
2018-04-03 17:29 ` Tim Harvey
2018-04-04 13:12 ` Andrew Lunn
2018-04-04 14:41 ` Mark Brown
2018-03-28 15:14 ` [PATCH v3 3/4] hwmon: add Gateworks System Controller support Tim Harvey
2018-03-28 17:00 ` Guenter Roeck
2018-03-28 20:23 ` Tim Harvey
2018-03-28 20:33 ` Guenter Roeck
2018-03-28 15:14 ` [PATCH v3 4/4] watchdog: " Tim Harvey
2018-03-30 1:07 ` [v3,4/4] " Guenter Roeck
2018-03-30 17:48 ` Dmitry Torokhov
2018-03-30 17:49 ` Tim Harvey
2018-03-30 18:19 ` Guenter Roeck
2018-04-02 16:07 ` Tim Harvey
2018-04-02 16:32 ` Andrew Lunn
2018-04-04 16:57 ` Tim Harvey
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=20180328162416.GB25325@roeck-us.net \
--to=linux@roeck-us.net \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tharvey@gateworks.com \
--cc=wim@iguana.be \
/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
all inboxes | Powered by JetHome®