From: David Brownell <david-b@pacbell.net>
To: Florian Fainelli <florian@openwrt.org>
Cc: Willy Tarreau <w@1wt.eu>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Samuel Ortiz <sameo@linux.intel.com>,
Miguel Gaio <miguel.gaio@efixo.com>,
Juhos Gabor <juhosg@openwrt.org>
Subject: Re: [PATCH v4] GPIO: add support for 74x164 serial-in/parallel-out 8-bit shift register
Date: Mon, 6 Sep 2010 17:41:42 -0700 (PDT) [thread overview]
Message-ID: <677002.54522.qm@web180309.mail.gq1.yahoo.com> (raw)
In-Reply-To: <201009011137.31938.florian@openwrt.org>
--- On Wed, 9/1/10, Florian Fainelli <florian@openwrt.org> wrote:
>
> Changes since v3:
> - support daisy-chaining of 74x164 up to 32 gpios
cool, a new feature!
I kind of dislike doing this after having
offereed feedback that you accepted, but I'm going
to NAK this driver for mainline.
The reasons are associated with a point I made in
my last feedback. The chip interface is SPI (but
it's not called that in the data sheets, true).
This driver is two things:
- maybe 85% looks like spi-over-gpio, cloning what
the spi-gpio.c driver does (a three-wire SPI mode,
using the NO_RX option, vs normal four-wire).
The rest is a small 74x164 driver.
So if there are spare GPIOs *this* driver can be
used, but not if there's just a spare SPI select.
If this were re-packaged as a small SPI protocol
driver and a small SPI-over-GPIO instance both of
the two components would be more reusable...
Your current hardware can handle the SPI-over-GPIO
approach, obviously.
I'd ack a small 74x164 SPI protocol driver, which is
what I expected when I saw the first post. But a
conglomerate driver -- no. Sorry.
- Dave
prev parent reply other threads:[~2010-09-07 0:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 23:18 [PATCH] GPIO: add support for NXP 74HC164 GPIO expander David Brownell
2010-08-29 10:10 ` Willy Tarreau
2010-08-29 15:37 ` [PATCH v2] GPIO: add support for 74HC164 serial-in/parallel-out 8-bit shift register Florian Fainelli
2010-08-30 23:43 ` David Brownell
2010-08-31 8:17 ` Florian Fainelli
2010-08-31 10:44 ` [PATCH v3] GPIO: add support for 74x164 " Florian Fainelli
2010-09-01 7:25 ` Florian Fainelli
2010-09-01 9:37 ` [PATCH v4] " Florian Fainelli
2010-09-07 0:41 ` David Brownell [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=677002.54522.qm@web180309.mail.gq1.yahoo.com \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=florian@openwrt.org \
--cc=juhosg@openwrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.gaio@efixo.com \
--cc=sameo@linux.intel.com \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®