From: Hannu Hartikainen <hannu@hrtk.in>
To: "Lars-Peter Clausen" <lars@metafoo.de>,
"Sa, Nuno" <Nuno.Sa@analog.com>,
"Antti Keränen" <detegr@rbx.email>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Cc: "Hennerich, Michael" <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>
Subject: Re: [RESEND PATCH] iio: adis: set GPIO reset pin direction
Date: Wed, 07 Jul 2021 16:30:51 +0300 [thread overview]
Message-ID: <60e5ac8c.1c69fb81.c69f0.abab@mx.google.com> (raw)
In-Reply-To: <f82dcd9f-c7f1-1619-9ff2-95066b82c77f@metafoo.de>
On Wed, 7 Jul 2021 14:25:06 +0200, Lars-Peter Clausen <lars@metafoo.de> wrote:
> GPIOD_OUT_LOW does not mean that the GPIO is active low. OUT_LOW just
> means that the GPIO is configured as output in the non-asserted
> state[1]. Whether it is active low or active high is configured through
> the flags associated with the GPIO descriptor. E.g. when using
> devicetree this is typically the field after the GPIO offset.
Oh, I misunderstood that. Thanks for pointing it out and sorry for the
confusion!
Your original suggestion of using GPIOD_OUT_HIGH sounds good to me,
then.
Hannu
next prev parent reply other threads:[~2021-07-07 13:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 9:29 [RESEND PATCH] iio: adis: set GPIO reset pin direction Antti Keränen
2021-07-07 8:18 ` Lars-Peter Clausen
2021-07-07 8:36 ` Sa, Nuno
2021-07-07 11:53 ` Hannu Hartikainen
2021-07-07 12:25 ` Lars-Peter Clausen
2021-07-07 13:30 ` Hannu Hartikainen [this message]
2021-07-08 9:54 ` [PATCH v2] " Antti Keränen
2021-07-08 10:05 ` Sa, Nuno
2021-07-10 17:35 ` Jonathan Cameron
2021-07-13 17:53 ` Jonathan Cameron
2021-07-14 10:04 ` Antti Keränen
2021-07-14 12:40 ` Jonathan Cameron
2021-07-14 18:25 ` Antti Keränen
2021-07-17 17:41 ` Jonathan Cameron
2021-07-07 12:32 ` [RESEND PATCH] " Sa, Nuno
2021-07-07 12:32 ` Lars-Peter Clausen
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=60e5ac8c.1c69fb81.c69f0.abab@mx.google.com \
--to=hannu@hrtk.in \
--cc=Michael.Hennerich@analog.com \
--cc=Nuno.Sa@analog.com \
--cc=detegr@rbx.email \
--cc=jic23@kernel.org \
--cc=lars@metafoo.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 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.