From: Guenter Roeck <linux@roeck-us.net>
To: Mike Jones <michael-a1.jones@analog.com>
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
jdelvare@suse.com, robh+dt@kernel.org, corbet@lwn.net
Subject: Re: [PATCH 2/2] bindings: (hwmon/ltc2978.txt): add support for more parts.
Date: Mon, 10 Feb 2020 09:51:58 -0800 [thread overview]
Message-ID: <20200210175158.GA31186@roeck-us.net> (raw)
In-Reply-To: <1581032654-4330-2-git-send-email-michael-a1.jones@analog.com>
On Thu, Feb 06, 2020 at 04:44:14PM -0700, Mike Jones wrote:
> LTC2972, LTC2979, LTC3884, LTC3889, LTC7880, LTM4664, LTM4677,
> LTM4678, LTM4680, LTM4700.
>
> Signed-off-by: Mike Jones <michael-a1.jones@analog.com>
Conditionally applied to hwmon-next. We'll see if Rob would like to see
any adjustments.
Thanks,
Guenter
> ---
> .../devicetree/bindings/hwmon/ltc2978.txt | 22 ++++++++++++++++++----
> 1 file changed, 18 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/hwmon/ltc2978.txt b/Documentation/devicetree/bindings/hwmon/ltc2978.txt
> index b428a70..4e7f621 100644
> --- a/Documentation/devicetree/bindings/hwmon/ltc2978.txt
> +++ b/Documentation/devicetree/bindings/hwmon/ltc2978.txt
> @@ -2,20 +2,30 @@ ltc2978
>
> Required properties:
> - compatible: should contain one of:
> + * "lltc,ltc2972"
> * "lltc,ltc2974"
> * "lltc,ltc2975"
> * "lltc,ltc2977"
> * "lltc,ltc2978"
> + * "lltc,ltc2979"
> * "lltc,ltc2980"
> * "lltc,ltc3880"
> * "lltc,ltc3882"
> * "lltc,ltc3883"
> + * "lltc,ltc3884"
> * "lltc,ltc3886"
> * "lltc,ltc3887"
> + * "lltc,ltc3889"
> + * "lltc,ltc7880"
> * "lltc,ltm2987"
> + * "lltc,ltm4664"
> * "lltc,ltm4675"
> * "lltc,ltm4676"
> + * "lltc,ltm4677"
> + * "lltc,ltm4678"
> + * "lltc,ltm4680"
> * "lltc,ltm4686"
> + * "lltc,ltm4700"
> - reg: I2C slave address
>
> Optional properties:
> @@ -25,13 +35,17 @@ Optional properties:
> standard binding for regulators; see regulator.txt.
>
> Valid names of regulators depend on number of supplies supported per device:
> + * ltc2972 vout0 - vout1
> * ltc2974, ltc2975 : vout0 - vout3
> - * ltc2977, ltc2980, ltm2987 : vout0 - vout7
> + * ltc2977, ltc2979, ltc2980, ltm2987 : vout0 - vout7
> * ltc2978 : vout0 - vout7
> - * ltc3880, ltc3882, ltc3886 : vout0 - vout1
> + * ltc3880, ltc3882, ltc3884, ltc3886, ltc3887, ltc3889 : vout0 - vout1
> + * ltc7880 : vout0 - vout1
> * ltc3883 : vout0
> - * ltm4676 : vout0 - vout1
> - * ltm4686 : vout0 - vout1
> + * ltm4664 : vout0 - vout1
> + * ltm4675, ltm4676, ltm4677, ltm4678 : vout0 - vout1
> + * ltm4680, ltm4686 : vout0 - vout1
> + * ltm4700 : vout0 - vout1
>
> Example:
> ltc2978@5e {
next prev parent reply other threads:[~2020-02-10 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 23:44 [PATCH 1/2] hwmon: (pmbus/ltc2978): add support for more parts Mike Jones
2020-02-06 23:44 ` [PATCH 2/2] bindings: (hwmon/ltc2978.txt): " Mike Jones
2020-02-10 17:51 ` Guenter Roeck [this message]
2020-02-19 22:01 ` Rob Herring
2020-02-10 17:49 ` [PATCH 1/2] hwmon: (pmbus/ltc2978): " 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=20200210175158.GA31186@roeck-us.net \
--to=linux@roeck-us.net \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael-a1.jones@analog.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).