From: Rob Herring <robh@kernel.org>
To: Logan Shaw <logan.shaw@alliedtelesis.co.nz>
Cc: linux@roeck-us.net, jdelvare@suse.com,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Joshua.Scott@alliedtelesis.co.nz,
Chris.Packham@alliedtelesis.co.nz
Subject: Re: [PATCH v6 2/2] dt-bindings: hwmon: (adt7475) Added missing adt7475 documentation
Date: Mon, 27 Jan 2020 09:48:00 -0600 [thread overview]
Message-ID: <20200127154800.GA7023@bogus> (raw)
In-Reply-To: <20200126221014.2978-3-logan.shaw@alliedtelesis.co.nz>
On Mon, Jan 27, 2020 at 11:10:14AM +1300, Logan Shaw wrote:
> Added a new file documenting the adt7475 devicetree and added the four
> new properties to it.
>
> Signed-off-by: Logan Shaw <logan.shaw@alliedtelesis.co.nz>
> ---
> ---
> .../devicetree/bindings/hwmon/adt7475.yaml | 95 +++++++++++++++++++
> 1 file changed, 95 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/hwmon/adt7475.yaml
>
> diff --git a/Documentation/devicetree/bindings/hwmon/adt7475.yaml b/Documentation/devicetree/bindings/hwmon/adt7475.yaml
> new file mode 100644
> index 000000000000..450da5e66e07
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/hwmon/adt7475.yaml
> @@ -0,0 +1,95 @@
> +# SPDX-License-Identifier: GPL-2.0
Dual license new bindings please:
(GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/adt7475.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: ADT7475 hwmon sensor
> +
> +maintainers:
> + - Jean Delvare <jdelvare@suse.com>
> +
> +description: |
> + The ADT7473, ADT7475, ADT7476, and ADT7490 are thermal monitors and multiple
> + PWN fan controllers.
> +
> + They support monitoring and controlling up to four fans (the ADT7490 can only
> + control up to three). They support reading a single on chip temperature
> + sensor and two off chip temperature sensors (the ADT7490 additionally
> + supports measuring up to three current external temperature sensors with
> + series resistance cancellation (SRC)).
> +
> + Datasheets:
> + https://www.onsemi.com/pub/Collateral/ADT7473-D.PDF
> + https://www.onsemi.com/pub/Collateral/ADT7475-D.PDF
> + https://www.onsemi.com/pub/Collateral/ADT7476-D.PDF
> + https://www.onsemi.com/pub/Collateral/ADT7490-D.PDF
> +
> + Description taken from omsemiconductors specification sheets, with minor
omsemi?
^
> + rephrasing.
> +
> +properties:
> + compatible:
> + enum:
> + - adi,adt7473
> + - adi,adt7475
> + - adi,adt7476
> + - adi,adt7490
> +
> + reg:
> + maxItems: 1
> +
> + bypass-attenuator-in0:
Needs a vendor prefix and a type ref.
> + description: |
> + Configures bypassing the individual voltage input
> + attenuator, on in0. This is supported on the ADT7476 and ADT7490.
> + If set to a non-zero integer the attenuator is bypassed, if set to
> + zero the attenuator is not bypassed. If the property is absent then
> + the config register is not modified.
Sounds like this could be boolean? If not, define a schema for what are
valid values.
> + maxItems: 1
> +
> + bypass-attenuator-in1:
> + description: |
> + Configures bypassing the individual voltage input
> + attenuator, on in1. This is supported on the ADT7473, ADT7475,
> + ADT7476 and ADT7490. If set to a non-zero integer the attenuator
> + is bypassed, if set to zero the attenuator is not bypassed. If the
> + property is absent then the config register is not modified.
> + maxItems: 1
> +
> + bypass-attenuator-in3:
> + description: |
> + Configures bypassing the individual voltage input
> + attenuator, on in3. This is supported on the ADT7476 and ADT7490.
> + If set to a non-zero integer the attenuator is bypassed, if set to
> + zero the attenuator is not bypassed. If the property is absent then
> + the config register is not modified.
> + maxItems: 1
> +
> + bypass-attenuator-in4:
These 4 could be a single entry under patternProperties.
> + description: |
> + Configures bypassing the individual voltage input
> + attenuator, on in4. This is supported on the ADT7476 and ADT7490.
> + If set to a non-zero integer the attenuator is bypassed, if set to
> + zero the attenuator is not bypassed. If the property is absent then
> + the config register is not modified.
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> +
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + hwmon@2e {
> + compatible = "adi,adt7476";
> + reg = <0x2e>;
> + bypass-attenuator-in0 = <1>;
> + bypass-attenuator-in1 = <0>;
> + };
> + };
> +...
> --
> 2.25.0
>
next prev parent reply other threads:[~2020-01-27 15:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-26 22:10 [PATCH v6 0/2] hwmon: (adt7475) Added attenuator bypass support Logan Shaw
2020-01-26 22:10 ` [PATCH v6 1/2] " Logan Shaw
2020-01-26 22:10 ` [PATCH v6 2/2] dt-bindings: hwmon: (adt7475) Added missing adt7475 documentation Logan Shaw
2020-01-27 15:48 ` Rob Herring [this message]
2020-01-29 4:30 ` Logan Shaw
2020-01-29 9:51 ` Guenter Roeck
2020-01-29 17:27 ` Rob Herring
2020-01-29 23:52 ` Logan Shaw
2020-01-30 3:07 ` Logan Shaw
2020-02-05 0:48 ` Logan Shaw
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=20200127154800.GA7023@bogus \
--to=robh@kernel.org \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=Joshua.Scott@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=logan.shaw@alliedtelesis.co.nz \
/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;
as well as URLs for NNTP newsgroup(s).