From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: jdelvare@suse.com, robh+dt@kernel.org, mark.rutland@arm.com,
corbet@lwn.net, afd@ti.com, linux-hwmon@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v5 1/2] dt-bindings: hwmon: Add ina3221 documentation
Date: Tue, 25 Sep 2018 20:08:58 -0700 [thread overview]
Message-ID: <20180926030857.GA458@Asurada-Nvidia.nvidia.com> (raw)
In-Reply-To: <4f16baf7-b1bc-c7d2-3dd9-ed10b78d59b6@roeck-us.net>
Hello Guenter,
On Tue, Sep 25, 2018 at 06:52:29PM -0700, Guenter Roeck wrote:
> > +2) child nodes
> > + Required properties:
> > + - reg: Must be 0, 1 or 2, corresponding to IN1, IN2 or IN3 port of INA3221
> > +
> > + Optional properties:
> > + - label: Name of the input source
> > + - shunt-resistor-micro-ohms: Shunt resistor value in micro-Ohm
> > + - status: Should be "disabled" if no input source
> > +
> > + Example:
> > +
> > + input@0 {
> > + reg = <0x0>;
> > + status = "disabled";
>
> I kind of feel embarrassed that I asked for the reg change ... especially while
> saying at the same time that I would like to see this work for other chips
> as well.
Well, though I didn't mention it, yet I changed it to "reg" is more
likely an agreement than a compromise: I searched in the mail list
and then found this mail (a year ago though):
https://www.spinics.net/lists/kernel/msg2455439.html
I feel it very similar to my case. So rather than betting Rob won't
tell me the same, changing to "reg" may reduce a turnaround time :)
> Other chips have different kinds of sensors. Voltage, current, power, temperature,
> and others. Whatever we come up with should support that.
>
> I see two possibilities right now. We can stick with reg and add a "type" property,
> or we can make the index something like
> {voltage,current,power,temperature,humidity}-{id,index}
One small concern is a case of being multi-type. For example, I saw
ina2xx driver having voltage, current and power at the same time...
> I personally prefer "type", but I don't really have a strong opinion.
> What do you think ?
I also like this over "reg" -- "reg" requires two extra properties,
and itself sounds slightly unnatural to me for situations like this
one where we don't use it as a register address, although I know it
is convenient and common to use.
> Or maybe we should really wait for feedback from Rob.
Personally I don't mind it all to change the doc and code and then
send a v6. But eventually we'll still need the final Acked-by from
Rob right? Then I guess it's the only option.
By the way, I have two ina3221 hwmon patches that rebase upon this
binding series. And I'd like to send them out to go through review
first, but I am not sure if you'd be okay for it -- I don't really
like to change their rebase order as it might mess up something.
Thanks
Nicolin
next prev parent reply other threads:[~2018-09-26 3:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 22:59 [PATCH v5 0/2] Add an initial DT binding doc for ina3221 Nicolin Chen
2018-09-25 22:59 ` [PATCH v5 1/2] dt-bindings: hwmon: Add ina3221 documentation Nicolin Chen
2018-09-26 1:52 ` Guenter Roeck
2018-09-26 3:08 ` Nicolin Chen [this message]
2018-09-26 3:40 ` Guenter Roeck
2018-09-26 6:14 ` Nicolin Chen
2018-09-27 17:42 ` Rob Herring
2018-09-27 17:44 ` Rob Herring
2018-09-27 18:39 ` Nicolin Chen
2018-09-25 22:59 ` [PATCH v5 2/2] hwmon: ina3221: Read channel input source info from DT Nicolin Chen
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=20180926030857.GA458@Asurada-Nvidia.nvidia.com \
--to=nicoleotsuka@gmail.com \
--cc=afd@ti.com \
--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=linux@roeck-us.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.