From: Conor Dooley <conor@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>,
patrick@stwcx.xyz, Jean Delvare <jdelvare@suse.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-i2c@vger.kernel.org, linux-hwmon@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: hwmon: Add lltc ltc4286 driver bindings
Date: Thu, 26 Oct 2023 16:26:13 +0100 [thread overview]
Message-ID: <20231026-poison-encrypt-1df55e023867@spud> (raw)
In-Reply-To: <fffa4330-8d01-8498-4c5f-772ebf2a6b5a@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 3129 bytes --]
On Thu, Oct 26, 2023 at 08:09:52AM -0700, Guenter Roeck wrote:
> On 10/26/23 07:25, Conor Dooley wrote:
> > Hey,
> >
> > On Thu, Oct 26, 2023 at 04:15:11PM +0800, Delphine CC Chiu wrote:
> > > Add a device tree bindings for ltc4286 driver.
> >
> > Bindings are for devices, not for drivers.
> >
> > >
> > > Signed-off-by: Delphine CC Chiu <Delphine_CC_Chiu@Wiwynn.com>
> > >
> > > Changelog:
> > > v2 - Revise vrange_select_25p6 to adi,vrange-select-25p6
> > > - Add type for adi,vrange-select-25p6
> > > - Revise rsense-micro-ohms to shunt-resistor-micro-ohms
> > > ---
> > > .../bindings/hwmon/lltc,ltc4286.yaml | 50 +++++++++++++++++++
> > > MAINTAINERS | 10 ++++
> > > 2 files changed, 60 insertions(+)
> > > create mode 100644 Documentation/devicetree/bindings/hwmon/lltc,ltc4286.yaml
> > >
> > > diff --git a/Documentation/devicetree/bindings/hwmon/lltc,ltc4286.yaml b/Documentation/devicetree/bindings/hwmon/lltc,ltc4286.yaml
> > > new file mode 100644
> > > index 000000000000..17022de657bb
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/hwmon/lltc,ltc4286.yaml
> > > @@ -0,0 +1,50 @@
> > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > > +%YAML 1.2
> > > +---
> > > +$id: http://devicetree.org/schemas/hwmon/lltc,ltc4286.yaml#
> > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > +
> > > +title: LTC4286 power monitors
> > > +
> > > +maintainers:
> > > + - Delphine CC Chiu <Delphine_CC_Chiu@Wiwynn.com>
> > > +
> > > +properties:
> > > + compatible:
> > > + enum:
> > > + - lltc,ltc4286
> > > + - lltc,ltc4287
> >
> > I don't recall seeing an answer to Guenter about this ltc4287 device:
> > https://lore.kernel.org/all/22f6364c-611c-ffb6-451c-9ddc20418d0a@roeck-us.net/
> >
>
> At least the chip does officially exist now, and a datasheet is available.
>
> https://www.analog.com/en/products/ltc4287.html
>
> It shows that coefficients for the telemetry commands are different,
> meaning that indeed both chips need to be explicitly referenced
> in the properties description (and handled in the driver, which proves
> my point of needing a datasheet before accepting such a driver).
Oh neat, would've been good if that'd been mentioned!
> > > +
> > > + reg:
> > > + maxItems: 1
> > > +
> > > + adi,vrange-select-25p6:
> > > + description:
> > > + This property is a bool parameter to represent the
> > > + voltage range is 25.6 or not for this chip.
> >
> > 25.6 what? Volts? microvolts?
> > What about Guenter's suggestion to name this so that it better matches
> > the other, similar properties?
> >
>
> I still would prefer one of the more common properties.
> I still prefer adi,vrange-high-enable.
I think, from reading the previous version, that this is actually the
lower voltage range, as there is a 102.x $unit range too that is the
default in the hardware. Obviously, the use of the property could be
inverted to match that naming however.
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-10-26 15:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 8:15 [PATCH v2 0/2] LTC4286 and LTC4287 driver support Delphine CC Chiu
2023-10-26 8:15 ` [PATCH v2 1/2] dt-bindings: hwmon: Add lltc ltc4286 driver bindings Delphine CC Chiu
2023-10-26 14:25 ` Conor Dooley
2023-10-26 15:09 ` Guenter Roeck
2023-10-26 15:26 ` Conor Dooley [this message]
2023-10-26 16:48 ` Guenter Roeck
2023-10-31 6:25 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2023-10-31 14:14 ` Guenter Roeck
2023-10-31 5:59 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2023-10-31 5:57 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2023-10-31 5:54 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2023-10-27 7:20 ` kernel test robot
2023-10-26 8:15 ` [PATCH v2 2/2] hwmon: pmbus: Add ltc4286 driver Delphine CC Chiu
2023-10-26 16:27 ` Guenter Roeck
2023-10-31 6:46 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2023-10-31 13:47 ` Guenter Roeck
2023-11-07 3:08 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2023-11-07 3:29 ` Guenter Roeck
2023-11-15 8:42 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2023-11-15 22:46 ` Guenter Roeck
2023-11-21 2:37 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2023-10-28 3:54 ` kernel test robot
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=20231026-poison-encrypt-1df55e023867@spud \
--to=conor@kernel.org \
--cc=Delphine_CC_Chiu@wiwynn.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=patrick@stwcx.xyz \
--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).