From: Linus Walleij <linus.walleij@linaro.org>
To: Michael Hennerich <michael.hennerich@analog.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Alexandre Courbot" <gnurou@gmail.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Hartmut Knaack" <knaack.h@gmx.de>,
"Paul Cercueil" <paul.cercueil@analog.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Paweł Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v3] iio: dac: Add support for the AD5592R/AD5593R ADCs/DACs
Date: Tue, 22 Mar 2016 09:49:55 +0100 [thread overview]
Message-ID: <CACRpkdYFUUoG--47qFA_za9X07qukST1vMBEoVC6J4z2LHcs3w@mail.gmail.com> (raw)
In-Reply-To: <56EFFBB6.40806@analog.com>
On Mon, Mar 21, 2016 at 2:48 PM, Michael Hennerich
<michael.hennerich@analog.com> wrote:
> The thing is that the device directly supports an OPEN DRAIN mode.
>
> If the consumer asks for open drain mode - everything works as expected.
> However instead of utilizing the on-chip feature, GPIOLIB will emulate open
> drain behaviour by configuring the chip for input when someone writes logic
> high.
>
> So the comment above was really meant to say -
> remove on-chip OPEN DRAIN mode, consumers should use the GPIOLIB
> implementation if required.
This is very interesting.
So if a hardware has *real* open drain, i.e. a bit in hardware that says
"set me in open drain mode" we should manage this in gpiolib
and provide a special callback in the vtable for it, right? Because it
is certainly better to do this with hardware, if we can.
I'll send a draft patch and we can see if this is what you want.
Yours,
Linus Walleij
next prev parent reply other threads:[~2016-03-22 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 12:58 [PATCH v3] iio: dac: Add support for the AD5592R/AD5593R ADCs/DACs michael.hennerich
2016-03-05 4:29 ` Rob Herring
2016-03-07 12:26 ` Michael Hennerich
2016-03-05 14:32 ` Jonathan Cameron
2016-03-07 12:34 ` Michael Hennerich
2016-03-11 16:37 ` Linus Walleij
2016-03-21 13:48 ` Michael Hennerich
2016-03-22 8:49 ` Linus Walleij [this message]
2016-03-28 15:05 ` 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=CACRpkdYFUUoG--47qFA_za9X07qukST1vMBEoVC6J4z2LHcs3w@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michael.hennerich@analog.com \
--cc=paul.cercueil@analog.com \
--cc=pawel.moll@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;
as well as URLs for NNTP newsgroup(s).