linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mika.westerberg@linux.intel.com (Mika Westerberg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] spi/pxa2xx-pci: Add common clock framework support in PCI glue layer
Date: Thu, 7 Aug 2014 11:43:02 +0300	[thread overview]
Message-ID: <20140807084302.GO1657@lahna.fi.intel.com> (raw)
In-Reply-To: <D004FADD.9F315%dvhart@linux.intel.com>

On Mon, Aug 04, 2014 at 08:55:50AM -0700, Darren Hart wrote:
> On 7/29/14, 15:06, "Andrea Adami" <andrea.adami@gmail.com> wrote:
> 
> >On Tue, Jul 29, 2014 at 8:55 PM, Mark Brown <broonie@kernel.org> wrote:
> >> On Tue, Jul 29, 2014 at 06:13:06PM +0200, Andrea Adami wrote:
> >>
> >>> note that a previous version of the patch breaks spi on pxa machines:
> >>> tested on pxa250 poodle and pxa255 corgi.
> >>> The patch is included in linux-Yocto since 3.14.
> >>
> >> The interesting question is if this version works...
> >
> >Happy to report that I could finally test on poodle/pxa250 the current
> >v2 and the patch doesn't seem to disturb the probe.
> >Sorry for the noise.
> >
> >Andrea
> >
> 
> I tested this (v2) on the MinnowBoard-Max (Baytrail Atom E3825) in PCI
> mode and successfully attached an MCP32XX ADC and tested it's IIO
> interface.

Mark,

Any idea what happened to this patch? I didn't find it in linux-next and
it looks like it is not merged with mainline either.

  reply	other threads:[~2014-08-07  8:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 17:10 [PATCH v2] spi/pxa2xx-pci: Add common clock framework support in PCI glue layer chiau.ee.chew at intel.com
2014-07-25  5:32 ` Mika Westerberg
2014-07-29 16:13   ` Andrea Adami
2014-07-29 18:55     ` Mark Brown
2014-07-29 22:06       ` Andrea Adami
2014-08-04 15:55         ` Darren Hart
2014-08-07  8:43           ` Mika Westerberg [this message]
2014-08-13 11:59             ` Kweh, Hock Leong
2014-08-13 19:20               ` Mark Brown
2014-08-16 22:20 ` Mark Brown

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=20140807084302.GO1657@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).