From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Russ Gorby <russ.gorby@intel.com>,
David Brownell <dbrownell@users.sourceforge.net>,
Grant Likely <grant.likely@secretlab.ca>,
"open list:SPI SUBSYSTEM"
<spi-devel-general@lists.sourceforge.net>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] spi: intel_mid_ssp_spi: new SPI driver for intel Medfield platform
Date: Thu, 3 Feb 2011 13:28:00 +0000 [thread overview]
Message-ID: <20110203132800.GA17825@sirena.org.uk> (raw)
In-Reply-To: <20110202224054.7916e7af@lxorguk.ukuu.org.uk>
On Wed, Feb 02, 2011 at 10:40:54PM +0000, Alan Cox wrote:
> And this is the unified one that handles all the devices, but I gather
> may need some fixing/test work on Medfield.
I've got the same question here as I had with Russ' patch: it looks like
there's some overlap with the SSP ports used for audio (it's just a
generic programmable serial port so even if it's not normally used for
audio that's a possiblity), how is that handled?
next prev parent reply other threads:[~2011-02-03 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH 0/1] Adding intel_mid_ssp_spi driver : 01/27/2011>
2011-02-02 21:01 ` [PATCH 0/1] Adding intel_mid_ssp_spi driver : 01/27/2011 Russ Gorby
2011-02-02 21:01 ` [PATCH 1/1] spi: intel_mid_ssp_spi: new SPI driver for intel Medfield platform Russ Gorby
[not found] ` <1296680512-2758-2-git-send-email-russ.gorby@intel.com>
2011-02-02 21:03 ` Mark Brown
2011-02-02 22:26 ` Alan Cox
2011-02-02 22:40 ` Alan Cox
2011-02-03 13:28 ` Mark Brown [this message]
2011-02-03 15:04 ` Alan Cox
2011-02-03 15:06 ` Mark Brown
2011-02-14 19:09 ` Grant Likely
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=20110203132800.GA17825@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dbrownell@users.sourceforge.net \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=russ.gorby@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).