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,
afd@ti.com, linux-hwmon@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: hwmon: Add ina3221 documentation
Date: Thu, 20 Sep 2018 18:24:48 -0700 [thread overview]
Message-ID: <20180921012447.GB23354@Asurada-Nvidia.nvidia.com> (raw)
In-Reply-To: <d744da89-ebd3-6059-31bf-e65e4c3d2ea4@roeck-us.net>
On Thu, Sep 20, 2018 at 05:45:07PM -0700, Guenter Roeck wrote:
> On 09/20/2018 05:07 PM, Nicolin Chen wrote:
> > +- ti,channel1-name:
> > +- ti,channel2-name:
> > +- ti,channel3-name:
> > + The names of the input sources (described in the schematics)
> > + Set the names with "NC" to indicate not-connected channels
> > +
>
> I don't really think this is a good idea - first to specify sensor
> names this way, and much less specifying that "NC" means that a sensor
> shall be disconnected/disabled.
I will replace the NC with a bool property for disconnection.
> Also, if we define devicetree support for this chip, it should include
> all configuration options required to configure it. This should at
> the very least include shunt resistor values.
I plan to add them too but am doing it incrementally. I can
try to include them in the next version.
Thanks
Nicolin
next prev parent reply other threads:[~2018-09-21 1:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 0:07 [PATCH 0/2] Add an initial DT binding doc for ina3221 Nicolin Chen
2018-09-21 0:07 ` [PATCH 1/2] dt-bindings: hwmon: Add ina3221 documentation Nicolin Chen
2018-09-21 0:45 ` Guenter Roeck
2018-09-21 1:24 ` Nicolin Chen [this message]
2018-09-21 0:07 ` [PATCH 2/2] hwmon: ina3221: Get channel names from DT node Nicolin Chen
2018-09-21 0:41 ` Guenter Roeck
2018-09-21 1:20 ` Nicolin Chen
2018-09-21 9:18 ` Nicolin Chen
2018-09-21 12:56 ` Guenter Roeck
2018-09-21 17:43 ` 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=20180921012447.GB23354@Asurada-Nvidia.nvidia.com \
--to=nicoleotsuka@gmail.com \
--cc=afd@ti.com \
--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=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