From: Rob Herring <robh@kernel.org>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: jdelvare@suse.com, linux@roeck-us.net, robh+dt@kernel.org,
mark.rutland@arm.com, logan.shaw@alliedtelesis.co.nz,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: Re: [PATCH v5 3/5] dt-bindings: hwmon: Document adt7475 pwm-active-state property
Date: Mon, 2 Mar 2020 19:25:33 -0600 [thread overview]
Message-ID: <20200303012533.GA3454@bogus> (raw)
In-Reply-To: <20200227084642.7057-4-chris.packham@alliedtelesis.co.nz>
On Thu, 27 Feb 2020 21:46:40 +1300, Chris Packham wrote:
>
> Add binding information for the adi,pwm-active-state property.
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
>
> Notes:
> Changes in v5:
> - change to adi,pwm-active-state
> - uint32 array
>
> Changes in v4:
> - use $ref uint32 and enum
> - add adi vendor prefix
>
> Cahnges in v3:
> - new
>
> .../devicetree/bindings/hwmon/adt7475.yaml | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-03-03 1:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 8:46 [PATCH v5 0/5] hwmon: (adt7475) attenuator bypass and pwm invert Chris Packham
2020-02-27 8:46 ` [PATCH v5 1/5] dt-bindings: hwmon: Document adt7475 binding Chris Packham
2020-03-03 21:00 ` Guenter Roeck
2020-02-27 8:46 ` [PATCH v5 2/5] dt-bindings: hwmon: Document adt7475 bypass-attenuator property Chris Packham
2020-03-03 21:00 ` Guenter Roeck
2020-02-27 8:46 ` [PATCH v5 3/5] dt-bindings: hwmon: Document adt7475 pwm-active-state property Chris Packham
2020-03-03 1:25 ` Rob Herring [this message]
2020-03-03 21:01 ` Guenter Roeck
2020-02-27 8:46 ` [PATCH v5 4/5] hwmon: (adt7475) Add attenuator bypass support Chris Packham
2020-03-03 21:05 ` Guenter Roeck
2020-02-27 8:46 ` [PATCH v5 5/5] hwmon: (adt7475) Add support for inverting pwm output Chris Packham
2020-03-03 21:08 ` Guenter Roeck
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=20200303012533.GA3454@bogus \
--to=robh@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 \
--cc=robh+dt@kernel.org \
/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).