From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: channing <chao.bi@intel.com>,
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
Subject: Re: [PATCH] SPI: SSP SPI Controller driver v3
Date: Mon, 7 Jan 2013 12:36:42 +0200 [thread overview]
Message-ID: <20130107103642.GQ13897@intel.com> (raw)
In-Reply-To: <CACRpkdZ9FctBE2zYA8xX3wgf1WOOvb-SMrXDTYDuguiLiUEwbw@mail.gmail.com>
On Mon, Jan 07, 2013 at 11:21:04AM +0100, Linus Walleij wrote:
> On Mon, Jan 7, 2013 at 9:05 AM, channing <chao.bi@intel.com> wrote:
>
> > Frankly I'm currently not sure whether they share same IP.. per your reminds, I tried to find but get
> > limited info about PXA SSP's IP, from the code, looks like they have part of registers the same.
> >
> > As far as I know, spi-pxa2xx.c is specific for SSP controller of PXA2XX/PXA3XX core, right?
>
> As pointed out by Mika it may very well be the same IP anyway. People copy/paste
> share and fork VHDL/Verilog/SystemC code just as much as they do with
> kernel code.
Yes, at least on Intel Lynxpoint it is the same IP with few additional
features. I'm about to send patches to spi-pxa2xx which enable the
Lynxpoint support shortly.
prev parent reply other threads:[~2013-01-07 10:33 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
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 [this message]
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=20130107103642.GQ13897@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.