From: David Brownell <david-b@pacbell.net>
To: Linus Walleij <linus.ml.walleij@gmail.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
broonie@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org, rpurdie@rpsys.net,
Cyril Chemparathy <cyril@ti.com>,
spi-devel-general@lists.sourceforge.net,
linux-arm-kernel@lists.infradead.org, lrg@slimlogic.co.uk
Subject: Re: [PATCH v4 08/12] gpio: add ti-ssp gpio driver
Date: Wed, 3 Nov 2010 05:35:54 -0700 (PDT) [thread overview]
Message-ID: <129498.93810.qm@web180302.mail.gq1.yahoo.com> (raw)
In-Reply-To: <AANLkTin=3K0H+YdNM2Nhz63c3+Upp+rwApo-Ww4p5qH6@mail.gmail.com>
--- On Wed, 11/3/10, Linus Walleij <linus.ml.walleij@gmail.com> wrote:
\
> Date: Wednesday, November 3, 2010, 3:18 AM
> 2010/11/3 David Brownell <david-b@pacbell.net>:
>
> > That seems like
> > a better structure for various vendors' "SSP"
> > hardware (multifunction serial interface logic)
>
> Incidentally the ARM PrimeCell PL022 is called SSP,
> "Synchronous Serial Port" and is not multifunction at all.
ISTR coming across that IP module; are you sure
that it only supports a single serial protocol,
instead of just a "small" variety" (multi)?
Unless the hardware only supports one protocol,
my point holds.
I wasn't implying that modules named SSP have
more in common than tending to support
more than a single serial protocol. If they
only support one, they get names like"USART"
or sometimes CODEC.
- Dave
next prev parent reply other threads:[~2010-11-03 12:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 20:18 [PATCH v4 00/12] tnetv107x ssp driver stack Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 01/12] misc: add driver for sequencer serial port Cyril Chemparathy
2010-10-28 15:49 ` Linus Walleij
2010-10-28 16:09 ` Cyril Chemparathy
2010-10-28 18:14 ` Linus Walleij
2010-10-26 20:18 ` [PATCH v4 02/12] davinci: add tnetv107x ssp platform device Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 03/12] davinci: add ssp config for tnetv107x evm board Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 04/12] spi: add ti-ssp spi master driver Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 05/12] davinci: add spi devices on tnetv107x evm Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 06/12] regulator: add driver for tps6524x regulator Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 07/12] davinci: add tnetv107x evm regulators Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 08/12] gpio: add ti-ssp gpio driver Cyril Chemparathy
2010-11-03 2:15 ` David Brownell
2010-11-03 10:18 ` Linus Walleij
2010-11-03 12:35 ` David Brownell [this message]
2010-11-03 16:24 ` Linus Walleij
2010-11-10 4:45 ` Grant Likely
2010-11-10 6:16 ` David Brownell
2010-11-10 6:23 ` Grant Likely
2010-11-10 14:34 ` Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 09/12] davinci: add tnetv107x evm ti-ssp gpio device Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 10/12] backlight: add support for tps6116x controller Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 11/12] davinci: add tnetv107x evm backlight device Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 12/12] davinci: add tnetv107x evm i2c eeprom device Cyril Chemparathy
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=129498.93810.qm@web180302.mail.gq1.yahoo.com \
--to=david-b@pacbell.net \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cyril@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linus.ml.walleij@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=rpurdie@rpsys.net \
--cc=spi-devel-general@lists.sourceforge.net \
/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®