From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
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 15:04:32 +0000 [thread overview]
Message-ID: <20110203150432.40cd74c4@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20110203132800.GA17825@sirena.org.uk>
On Thu, 3 Feb 2011 13:28:00 +0000
Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> 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?
The SSP has PCI configuration indicating how it is being assigned, which
is in vendor capability byte 6. The low 3 bits indicte the mode, where
mode 1 is an SPI master/slave, and in that case bit 6 is set for a slave.
The SSP/SPI driver will only grab ports that have been assigned to that
purpose as part of the system design.
I'm just putting the other bits from the generic driver back into the
more featured/tested specific driver that Russ posted.
Alan
next prev parent reply other threads:[~2011-02-03 15:02 UTC|newest]
Thread overview: 13+ 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-12 9:19 ` Grant Likely
2011-02-14 17:22 ` Gorby, Russ
2011-02-02 21:01 ` Russ Gorby
2011-02-02 21:01 ` [PATCH 1/1] spi: intel_mid_ssp_spi: new SPI driver for intel Medfield platform Russ Gorby
2011-02-02 21:01 ` Russ Gorby
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
2011-02-03 15:04 ` Alan Cox [this message]
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=20110203150432.40cd74c4@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=broonie@opensource.wolfsonmicro.com \
--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 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.