All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauri Sandberg <sandberg@mailfence.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Drew Fustini <drew@beagleboard.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] gpio: driver for the NXP 74HC153 chip
Date: Mon, 5 Apr 2021 10:25:05 +0200 (CEST)	[thread overview]
Message-ID: <10440931.720197.1617611104977@ichabod.co-bxl> (raw)
In-Reply-To: <CAHp75VcG7Uj-cDhbxDL23w0zNDG7eVqedw_eN5J6XPmVTECbvQ@mail.gmail.com>



> ----------------------------------------
> From: Andy Shevchenko <andy.shevchenko@gmail.com>
> On Sun, Apr 4, 2021 at 6:36 PM Drew Fustini <drew@beagleboard.org> wrote:
> > Do you think TI SN74HC153N should be ok for testing the gpio input
> > multiplexer patch [1]?
> 
> Functionally all those *4xxx153yyy are all analogous.
> You even may try soviet copy of it, i.e. 555КП11 (cyrillic letters!,
> 555 can be 1533 or a few more variants).

I really do hope so. The reason for going for [1] is that it should provide a generic mechanism and
be manufacturer independent. :)

> > [1] https://lore.kernel.org/linux-gpio/20210325122832.119147-1-sandberg@mailfence.com/

  reply	other threads:[~2021-04-05  8:25 UTC|newest]

Thread overview: 14+ 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-02-23 23:22     ` kernel test robot
2021-04-03  9:39     ` Andy Shevchenko
2021-04-03  9:39       ` Andy Shevchenko
2021-02-23 23:47   ` kernel test robot
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
2021-04-04 17:17         ` Andy Shevchenko
2021-04-05  8:25           ` Mauri Sandberg [this message]
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=10440931.720197.1617611104977@ichabod.co-bxl \
    --to=sandberg@mailfence.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=drew@beagleboard.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.