From: Jonathan Cameron <jic23@kernel.org>
To: Slawomir Stepien <sst@poczta.fm>
Cc: Chris Coffey <cmc@babblebit.net>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Peter Rosin <peda@axentia.se>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: potentiometer: Add Microchip MCP41xxx/42xxx
Date: Fri, 16 Nov 2018 18:02:18 +0000 [thread overview]
Message-ID: <20181116180218.61aabbe5@archlinux> (raw)
In-Reply-To: <20181114100141.GA1214@x220.localdomain>
On Wed, 14 Nov 2018 11:01:41 +0100
Slawomir Stepien <sst@poczta.fm> wrote:
> On lis 14, 2018 09:52, Chris Coffey wrote:
> > This patch adds device tree documentation for the Microchip
> > MCP41xxx/42xxx family of digital potentiometers.
>
> Hi
>
> One note inline.
>
> > Signed-off-by: Chris Coffey <cmc@babblebit.net>
> > ---
> > .../bindings/iio/potentiometer/mcp41010.txt | 29 ++++++++++++++++++++++
> > 1 file changed, 29 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/iio/potentiometer/mcp41010.txt
> >
> > diff --git a/Documentation/devicetree/bindings/iio/potentiometer/mcp41010.txt b/Documentation/devicetree/bindings/iio/potentiometer/mcp41010.txt
> > new file mode 100644
> > index 0000000000..17565acace
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/iio/potentiometer/mcp41010.txt
> > @@ -0,0 +1,29 @@
> > +* Microchip MCP41010/41050/41100/42010/42050/42100 Digital Potentiometer
> > + driver
> > +
> > +Datasheet publicly available at:
> > +http://ww1.microchip.com/downloads/en/devicedoc/11195c.pdf
> > +
> > +The node for this driver must be a child node of a SPI controller, hence
> > +all mandatory properties described in
> > +
> > + Documentation/devicetree/bindings/spi/spi-bus.txt
> > +
> > +must be specified.
> > +
> > +Required properties:
> > + - compatible: Must be one of the following, depending on the
> > + model:
> > + "microchip,mcp41010"
> > + "microchip,mcp41050"
> > + "microchip,mcp41100"
> > + "microchip,mcp42010"
> > + "microchip,mcp42050"
> > + "microchip,mcp42100"
> > +
> > +Example:
> > +mcp41010: potentiometer@0 {
> > + compatible = "mcp41010";
>
> Missing company name in compatible.
Also don't need (or want) the precursor
mcp41010: for an example.
potentiometer@0 {
compatible = "microchip,mcp41010";
reg = <0>;
spi-max-frequency = <500000>;
};
>
> > + reg = <0>;
> > + spi-max-frequency = <500000>;
> > +};
>
next prev parent reply other threads:[~2018-11-16 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 9:52 [PATCH v2 0/2] Add support for Microchip MCP41xxx/42xxx potentiometers Chris Coffey
2018-11-14 9:52 ` [PATCH v2 1/2] dt-bindings: iio: potentiometer: Add Microchip MCP41xxx/42xxx Chris Coffey
2018-11-14 10:01 ` Slawomir Stepien
2018-11-16 18:02 ` Jonathan Cameron [this message]
2018-11-17 20:25 ` Chris Coffey
2018-11-14 9:52 ` [PATCH v2 2/2] iio: potentiometer: Add driver for " Chris Coffey
2018-11-14 10:30 ` Slawomir Stepien
2018-11-16 18:10 ` Jonathan Cameron
2018-11-17 20:31 ` Chris Coffey
2018-11-19 13:48 ` Jonathan Cameron
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=20181116180218.61aabbe5@archlinux \
--to=jic23@kernel.org \
--cc=cmc@babblebit.net \
--cc=devicetree@vger.kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peda@axentia.se \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=sst@poczta.fm \
/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).