linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Russ Gorby <russ.gorby@intel.com>
Cc: David Brownell <dbrownell@users.sourceforge.net> (maintainer:SPI
	SUBSYSTEM),
	Grant Likely <grant.likely@secretlab.ca> (maintainer:SPI
	SUBSYSTEM),
	spi-devel-general@lists.sourceforge.net (open list:SPI SUBSYSTEM),
	linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH 1/1] spi: intel_mid_ssp_spi: new SPI driver for intel Medfield platform
Date: Wed, 2 Feb 2011 22:26:52 +0000	[thread overview]
Message-ID: <20110202222652.6b811f56@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <1296680512-2758-2-git-send-email-russ.gorby@intel.com>

On Wed,  2 Feb 2011 13:01:52 -0800
Russ Gorby <russ.gorby@intel.com> wrote:

> SPI master controller driver for the Intel MID platform Medfield
> This driver uses the Penwell SSP controller and configures it to
> be a SPI device (spibus 3). This bus supports a single device -
> the 3G SPI modem that can operate up to 25Mhz.

NAK this.

We have an existing development driver that covers 0x0815, 0x0816, 0x0825,
0x0832 in a single driver which needs tidying up and double checking on
all the relevant Medfield and Moorestown devices and is based on work done
by Mathieu Soulard.

All these devices can be handled by a single driver, and should be.

Alan

  parent reply	other threads:[~2011-02-02 22:26 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 [this message]
2011-02-02 22:40   ` Alan Cox
2011-02-03 13:28     ` Mark Brown
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=20110202222652.6b811f56@lxorguk.ukuu.org.uk \
    --to=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).