From: nicolas saenz julienne <nicolassaenzj@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH] gpio: 74x164: add dt support for nxp's 74x594
Date: Tue, 22 Mar 2016 11:42:08 +0100 [thread overview]
Message-ID: <20160322104207.GA2842@marie-Aspire-5600> (raw)
In-Reply-To: <CAMuHMdW5Owzv06wnV34W3cYp=ibrONcfBVV6WST5VyvQ1ENjsA@mail.gmail.com>
Hi sorry for the late response but I was on vacation.
>
> Why did you choose the "lvc" variant?
Well to be honest the HW people did and it's all I could test with. I don't
know much about these naming schemes, apart from the intuition it has to do
with frequency and line levels.
> Ideally, you want to put the oldest "manuf,74x594" variant here.
What do you mean by oldest? What would you suggest? it's funny because the chip
is going to be used on a new product that is meant to be produced for years.
> I once read it was Motorola who invented the 7459x parts, to interface with
> SPI.
>
> Gr{oetje,eeting}s,
>
> Geert
>
Thanks for your comments!
Nicolas
next prev parent reply other threads:[~2016-03-22 10:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 23:32 [PATCH] gpio: 74x164: add dt support for nxp's 74x594 Nicolas Saenz Julienne
[not found] ` <1457998330-8070-1-git-send-email-nicolassaenzj-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-15 15:27 ` Geert Uytterhoeven
2016-03-22 10:42 ` nicolas saenz julienne [this message]
2016-03-22 10:56 ` Geert Uytterhoeven
[not found] ` <CAMuHMdWTteucxUgBU=d6=bckaZrn0vmr8LYW08UdULEtQYFzpg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-22 23:16 ` Nicolas Saenz Julienne
2016-03-18 20:26 ` Rob Herring
2016-03-31 8:26 ` Linus Walleij
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=20160322104207.GA2842@marie-Aspire-5600 \
--to=nicolassaenzj@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=geert@linux-m68k.org \
--cc=gnurou@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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).