From: Rob Herring <robh+dt@kernel.org>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Mark Rutland <mark.rutland@arm.com>,
Logan Shaw <logan.shaw@alliedtelesis.co.nz>,
Linux HWMON List <linux-hwmon@vger.kernel.org>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/5] dt-bindings: hwmon: Document adt7475 bypass-attenuator property
Date: Thu, 20 Feb 2020 14:01:32 -0600 [thread overview]
Message-ID: <CAL_JsqK-zD+_gBw-HqzSfz8_r8wY041DcewKJYm7BZj4ToHeZw@mail.gmail.com> (raw)
In-Reply-To: <20200217234657.9413-3-chris.packham@alliedtelesis.co.nz>
On Mon, Feb 17, 2020 at 5:47 PM Chris Packham
<chris.packham@alliedtelesis.co.nz> wrote:
>
> From: Logan Shaw <logan.shaw@alliedtelesis.co.nz>
>
> Add documentation for the bypass-attenuator-in[0-4] property.
>
> Signed-off-by: Logan Shaw <logan.shaw@alliedtelesis.co.nz>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
> .../devicetree/bindings/hwmon/adt7475.yaml | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/hwmon/adt7475.yaml b/Documentation/devicetree/bindings/hwmon/adt7475.yaml
> index 2252499ea201..61da90c82649 100644
> --- a/Documentation/devicetree/bindings/hwmon/adt7475.yaml
> +++ b/Documentation/devicetree/bindings/hwmon/adt7475.yaml
> @@ -39,6 +39,17 @@ properties:
> reg:
> maxItems: 1
>
> +patternProperties:
> + "^bypass-attenuator-in[0-4]$":
> + maxItems: 1
> + minimum: 0
> + maximum: 1
The errors here are because you are mixing array and scalar constraints.
You also need a vendor prefix and a type $ref.
> + description: |
> + Configures bypassing the individual voltage input attenuator. If
> + set to 1 the attenuator is bypassed if set to 0 the attenuator is
> + not bypassed. If the property is absent then the attenuator
> + retains it's configuration from the bios/bootloader.
> +
> required:
> - compatible
> - reg
> @@ -52,6 +63,8 @@ examples:
> 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-02-20 20:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 23:46 [PATCH 0/5] hwmon: (adt7475) attenuator bypass and pwm invert Chris Packham
2020-02-17 23:46 ` [PATCH 1/5] dt-bindings: hwmon: Document adt7475 binding Chris Packham
2020-02-17 23:46 ` [PATCH 2/5] dt-bindings: hwmon: Document adt7475 bypass-attenuator property Chris Packham
2020-02-18 20:24 ` Rob Herring
2020-02-18 20:52 ` Chris Packham
2020-02-18 23:24 ` Chris Packham
2020-02-20 20:01 ` Rob Herring [this message]
2020-02-17 23:46 ` [PATCH 3/5] dt-bindings: hwmon: Document adt7475 invert-pwm property Chris Packham
2020-02-17 23:46 ` [PATCH 4/5] hwmon: (adt7475) Add attenuator bypass support Chris Packham
2020-02-17 23:46 ` [PATCH 5/5] hwmon: (adt7475) Add support for inverting pwm output Chris Packham
2020-02-18 0:32 ` [PATCH 0/5] hwmon: (adt7475) attenuator bypass and pwm invert Guenter Roeck
2020-02-18 0:43 ` Chris Packham
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=CAL_JsqK-zD+_gBw-HqzSfz8_r8wY041DcewKJYm7BZj4ToHeZw@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=chris.packham@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 \
--cc=mark.rutland@arm.com \
/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).