From: Christoph Fritz <chf.fritz@googlemail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Vlad Dogaru <ddvlad@gmail.com>, Hartmut Knaack <knaack.h@gmx.de>,
linux-iio@vger.kernel.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] iio: sx9500: add final devicetree support
Date: Fri, 02 Sep 2016 17:04:31 +0200 [thread overview]
Message-ID: <1472828671.1929.32.camel@googlemail.com> (raw)
In-Reply-To: <CAOMZO5BeL1EKOQvZQoXXObttHSKxL7UQ1s2r8H4EOuROOb_YnQ@mail.gmail.com>
On Fri, 2016-09-02 at 11:53 -0300, Fabio Estevam wrote:
> On Fri, Sep 2, 2016 at 11:49 AM, Christoph Fritz
> <chf.fritz@googlemail.com> wrote:
>
> > +sx9500@28 {
> > + compatible = "semtech,sx9500";
> > + reg = <0x28>;
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pinctrl_sx9500>;
> > + interrupt-parent = <&gpio2>;
> > + interrupts = <16 IRQ_TYPE_LEVEL_LOW>;
> > + reset-gpios = <&gpio2 10 GPIO_ACTIVE_HIGH>;
>
> Datasheet says the reset is active low.
Here on my board I'm using the reset pin as an open-drain with external
pullup, so GPIO_ACTIVE_HIGH is valid.
As this is an example, I don't care if it says _HIGH or _LOW.
next prev parent reply other threads:[~2016-09-02 15:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 14:49 [PATCH] iio: sx9500: add final devicetree support Christoph Fritz
2016-09-02 14:53 ` Fabio Estevam
2016-09-02 15:04 ` Christoph Fritz [this message]
2016-09-02 15:12 ` Fabio Estevam
2016-09-02 15:23 ` Christoph Fritz
2016-09-02 16:16 ` Fabio Estevam
2016-09-02 16:47 ` Christoph Fritz
2016-09-02 18:25 ` Fabio Estevam
2016-09-03 10:30 ` [PATCH v2] " Christoph Fritz
2016-09-03 11:15 ` Fabio Estevam
2016-09-03 11:19 ` Vlad Dogaru
2016-09-03 14:27 ` Jonathan Cameron
2016-09-12 15:44 ` Rob Herring
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=1472828671.1929.32.camel@googlemail.com \
--to=chf.fritz@googlemail.com \
--cc=ddvlad@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=linux-iio@vger.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).