From: Wolfram Sang <wsa@the-dreams.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Rojhalat Ibrahim <imr@rtschenk.de>, Gerhard Sittig <gsi@denx.de>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Grant Likely <grant.likely@linaro.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 1/2][v5] gpiolib: allow simultaneous setting of multiple GPIO outputs
Date: Fri, 29 Aug 2014 10:15:14 +0200 [thread overview]
Message-ID: <20140829081514.GA1329@katana> (raw)
In-Reply-To: <CACRpkdZnzVqNm8EoKDSt_LsP0bta8FQYnif4ou+ngFyD-4x-YQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
> > So, Linus, would a patched version of one of the mentioned drivers qualify as
> > a user that would allow you to merge my patch?
>
> I think so. My concern is with code that doesn't get exercised, anywhere.
If we have a gpio-chardev somewhen, I know a bunch of industrial
customers who will love it. It always feels a bit awkward to tell them
they have to fiddle with bits individually if they want to read out an
ID byte or have paired GPIO for other reasons.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-08-29 8:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 13:51 [PATCH 1/2][v5] gpiolib: allow simultaneous setting of multiple GPIO outputs Rojhalat Ibrahim
2014-06-21 7:08 ` Alexandre Courbot
2014-06-21 20:24 ` Mark Brown
2014-07-07 15:23 ` Linus Walleij
2014-07-07 16:12 ` Rojhalat Ibrahim
2014-07-09 10:17 ` Linus Walleij
2014-07-30 9:12 ` Rojhalat Ibrahim
2014-07-30 10:41 ` Mark Brown
2014-07-30 11:04 ` Rojhalat Ibrahim
2014-07-31 2:35 ` Alexandre Courbot
2014-07-31 7:12 ` Gerhard Sittig
2014-07-31 8:42 ` Rojhalat Ibrahim
2014-08-06 12:45 ` Gerhard Sittig
2014-08-06 19:39 ` Mark Brown
2014-08-07 9:52 ` Rojhalat Ibrahim
2014-08-29 5:21 ` Linus Walleij
2014-08-29 8:15 ` Wolfram Sang [this message]
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=20140829081514.GA1329@katana \
--to=wsa@the-dreams.de \
--cc=broonie@kernel.org \
--cc=gnurou@gmail.com \
--cc=grant.likely@linaro.org \
--cc=gsi@denx.de \
--cc=imr@rtschenk.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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.