public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Antonio Ospite <ospite@studenti.unina.it>
To: spi-devel-general@lists.sourceforge.net
Cc: Grant Likely <grant.likely@secretlab.ca>,
	linux-mmc@vger.kernel.org, Ernst Schwab <eschwab@online.de>,
	Ned Forrester <nforrester@whoi.edu>,
	David Brownell <dbrownell@users.sourceforge.net>,
	Anton Vorontsov <cbouatmailru@gmail.com>,
	openezx-devel@lists.openezx.org
Subject: Re: Request for SPI testing
Date: Sat, 3 Jul 2010 19:05:04 +0200	[thread overview]
Message-ID: <20100703190504.693fe8fa.ospite@studenti.unina.it> (raw)
In-Reply-To: <AANLkTimVajsJq9lRSLbv8_lzu7g_CL5ptmV5OLG6dBds@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2044 bytes --]

On Tue, 29 Jun 2010 21:30:34 -0600
Grant Likely <grant.likely@secretlab.ca> wrote:

> I've pushed out Ernst's spi bus locking API patches to the following
> branch.  Before I push them into linux-next, I'd like to get some
> testing.  Can I have some volunteers please to pull this branch and
> give it a spin?  Bonus points for people who have mmc cards
> multiplexed with other devices on their SPI bus.
>

From a quick test it works for me too, I have both the MMC and the PMIC
(battery, regulators) attached to spi, this is Motorola A910 phone
(pxa27x). Just FYI I applied the patches to 2.6.34 and tested with this
kernel, without the patches I cannot make mmc_spi work reliably (lots
of I/O errors, due to conflict with the PMIC) with these patches I can
finally use the MMC card.

Thanks a lot,
   Antonio

> Cheers,
> g.
> 
> The following changes since commit 5904b3b81d25166e5e39b9727645bb47937618e3:
>   Linus Torvalds (1):
>         Merge branch 'perf-fixes-for-linus' of
> git://git.kernel.org/.../tip/linux-2.6-tip
> 
> are available in the git repository at:
> 
>   git://git.secretlab.ca/git/linux-2.6 spi/test
> 
> Cory Maccarrone (1):
>       SPI100k: Fix 8-bit and RX-only transfers
> 
> Ernst Schwab (2):
>       spi/mmc_spi: SPI bus locking API, using mutex
>       spi/mmc_spi: mmc_spi adaptations for SPI bus locking API
> 
>  drivers/mmc/host/mmc_spi.c  |   59 ++---------
>  drivers/spi/omap_spi_100k.c |   23 +++--
>  drivers/spi/spi.c           |  225 ++++++++++++++++++++++++++++++++++++-------
>  include/linux/spi/spi.h     |   12 +++
>  4 files changed, 227 insertions(+), 92 deletions(-)
> 
> -- 
> Grant Likely, B.Sc., P.Eng.
> Secret Lab Technologies Ltd.
> 


-- 
Antonio Ospite
http://ao2.it

PGP public key ID: 0x4553B001

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2010-07-03 17:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-30  3:30 Request for SPI testing Grant Likely
2010-06-30 11:57 ` Matt Fleming
2010-06-30 12:44 ` Ernst Schwab
2010-07-03 17:05 ` Antonio Ospite [this message]
2010-07-04  4:51   ` 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=20100703190504.693fe8fa.ospite@studenti.unina.it \
    --to=ospite@studenti.unina.it \
    --cc=cbouatmailru@gmail.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=eschwab@online.de \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-mmc@vger.kernel.org \
    --cc=nforrester@whoi.edu \
    --cc=openezx-devel@lists.openezx.org \
    --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