From: Drew Fustini <drew@beagleboard.org>
To: Mauri Sandberg <sandberg@mailfence.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] gpio: driver for the NXP 74HC153 chip
Date: Sun, 4 Apr 2021 08:35:49 -0700 [thread overview]
Message-ID: <CAPgEAj4Zd9FWL1UFkBLbiJRadBhGqc+NWdrKCxaTXyVeO3tSxA@mail.gmail.com> (raw)
In-Reply-To: <1306564766.662706.1617546604089@ichabod.co-bxl>
On Sun, Apr 4, 2021, 07:30 Mauri Sandberg <sandberg@mailfence.com> wrote:
>
> > ----------------------------------------
> > From: Drew Fustini <drew@beagleboard.org>
> > On Tue, Feb 23, 2021 at 11:56 AM Mauri Sandberg <sandberg@mailfence.com> wrote:
> > >
> > > Support for NXP 74HC153 Dual 4-input Multiplexer. This provides a GPIO
> > > interface supporting input mode only
> >
> > I would like to try this out. This seems like a commodity part so I
> > looked for it in a DIP package. I only see that from TI in the
> > SN74HC153N. Do you anticipate a different vendor being a problem?
>
> Oh I am so sorry you guys had to see this. This is based on something I found and assumed to be up to
> standards and thought of trying to upstream it with modifications to device tree functionality only. Soon
> afterwards I realised its shortcomings in the GPIO api department and being too specific and sent a proposal
> what's now known as 'gpio-mux-input'. No further efforts should be put into this.
>
> I do not know how to withdraw a patch. Also, maybe I should have used the same thread with v2 instead
> of sending a new patch with new title.
No problem, I should not have replied to this old email, I had just
searched for the mention of the IC.
Do you think TI SN74HC153N should be ok for testing the gpio input
multiplexer patch [1]?
Thanks,
Drew
[1] https://lore.kernel.org/linux-gpio/20210325122832.119147-1-sandberg@mailfence.com/
next prev parent reply other threads:[~2021-04-04 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 19:53 [RFC] Driver for the NXP 74HC153 chip Mauri Sandberg
2021-02-23 19:53 ` [PATCH] gpio: driver " Mauri Sandberg
2021-02-23 23:22 ` kernel test robot
2021-04-03 9:39 ` Andy Shevchenko
2021-02-23 23:47 ` kernel test robot
2021-04-02 20:27 ` Drew Fustini
2021-04-04 14:30 ` Mauri Sandberg
2021-04-04 15:35 ` Drew Fustini [this message]
2021-04-04 17:17 ` Andy Shevchenko
2021-04-05 8:25 ` Mauri Sandberg
2021-04-05 9:11 ` Andy Shevchenko
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=CAPgEAj4Zd9FWL1UFkBLbiJRadBhGqc+NWdrKCxaTXyVeO3tSxA@mail.gmail.com \
--to=drew@beagleboard.org \
--cc=andy.shevchenko@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=sandberg@mailfence.com \
/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).