From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: chao bi <chao.bi@intel.com>
Cc: grant.likely@secretlab.ca, linux-kernel@vger.kernel.org,
sylvain.centelles@intel.com, ken.k.mills@intel.com,
jun.d.chen@intel.com, alan@linux.intel.com,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] SPI: SSP SPI Controller driver v3
Date: Wed, 19 Dec 2012 11:56:17 +0200 [thread overview]
Message-ID: <20121219095616.GV2261@intel.com> (raw)
In-Reply-To: <1355818296.11831.287.camel@bichao>
On Tue, Dec 18, 2012 at 04:11:36PM +0800, chao bi wrote:
>
> This patch is to implement SSP SPI controller driver, which has been applied and
> validated on intel Moorestown & Medfield platform. The patch are originated by
> Ken Mills <ken.k.mills@intel.com> and Sylvain Centelles <sylvain.centelles@intel.com>,
> migrating to lateset Linux mainline SPI framework by Channing <chao.bi@intel.com>
> and Chen Jun <jun.d.chen@intel.com> according to their integration & validation
> on Medfield platform.
This is the same IP block as used in PXA, right? With few modifications
here and there. Is there a reason not to use spi-pxa2xx.c?
I have a set of patches for spi-pxa2xx.c that adds support for Lynxpoint
LPSS, DMA engine and ACPI enumeration. I'm hoping to send those soon (once
-rc1 is released) to the list.
Maybe we can co-operate to get the Medfield support there as well?
next prev parent reply other threads:[~2012-12-19 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 8:11 [PATCH] SPI: SSP SPI Controller driver v3 chao bi
2012-12-19 9:56 ` Mika Westerberg [this message]
2013-01-06 23:36 ` Linus Walleij
2013-01-07 8:05 ` channing
2013-01-07 10:21 ` Linus Walleij
2013-01-07 10:36 ` Mika Westerberg
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=20121219095616.GV2261@intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=chao.bi@intel.com \
--cc=grant.likely@secretlab.ca \
--cc=jun.d.chen@intel.com \
--cc=ken.k.mills@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sylvain.centelles@intel.com \
/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.