* Request for SPI testing
@ 2010-06-30 3:30 Grant Likely
2010-06-30 11:57 ` Matt Fleming
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: Grant Likely @ 2010-06-30 3:30 UTC (permalink / raw)
To: spi-devel-general, linux-mmc, Ernst Schwab, Antonio Ospite,
Ned Forrester
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.
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Request for SPI testing
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
2 siblings, 0 replies; 5+ messages in thread
From: Matt Fleming @ 2010-06-30 11:57 UTC (permalink / raw)
To: Grant Likely
Cc: spi-devel-general, linux-mmc, Ernst Schwab, Antonio Ospite,
Ned Forrester, David Brownell, Anton Vorontsov
On Tue, Jun 29, 2010 at 09:30:34PM -0600, Grant Likely 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.
I put these patches through some light testing by reading data from a
flash device and writing it to an mmc card, both over SPI. They seem
to hold up fine, but I can certainly try some other things if you have
anything specific in mind.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Request for SPI testing
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
2 siblings, 0 replies; 5+ messages in thread
From: Ernst Schwab @ 2010-06-30 12:44 UTC (permalink / raw)
To: Grant Likely, spi-devel-general, linux-mmc, Antonio Ospite,
"Ned Forrester" <nfor
Hi Grant,
> 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.
Thanks for bringing up this topic.
We are working with these two patches (except the
spin_lock_irqsave modification and the 'bool' datatype
for bus_lock_flag) for several months on our system
(powerpc, MPC8314, kernel 2.6.32.7 and 2.6.32.14)
that makes heavy use of several SPI devices: 9 x EEPROM,
3 x dataflash, MMC and 2 x MDIO-pseudo-SPI (with a special
SPI-to-MDIO bus driver).
The MMC is used rarely, but the rest is essential for
system operation. Until now, we observed no problems,
even when copying EEPROM data to MMC. So you may add
my 'tested-by'.
Best regards
Ernst
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Request for SPI testing
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
2010-07-04 4:51 ` Grant Likely
2 siblings, 1 reply; 5+ messages in thread
From: Antonio Ospite @ 2010-07-03 17:05 UTC (permalink / raw)
To: spi-devel-general
Cc: Grant Likely, linux-mmc, Ernst Schwab, Ned Forrester,
David Brownell, Anton Vorontsov, openezx-devel
[-- 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 --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Request for SPI testing
2010-07-03 17:05 ` Antonio Ospite
@ 2010-07-04 4:51 ` Grant Likely
0 siblings, 0 replies; 5+ messages in thread
From: Grant Likely @ 2010-07-04 4:51 UTC (permalink / raw)
To: Antonio Ospite
Cc: spi-devel-general, linux-mmc, Ernst Schwab, Ned Forrester,
David Brownell, Anton Vorontsov, openezx-devel, Matt Fleming
On Sat, Jul 3, 2010 at 11:05 AM, Antonio Ospite
<ospite@studenti.unina.it> wrote:
> 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
Thanks everyone who tested. I've pushed this out for linux-next
inclusion (next-spi branch)
g.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2010-07-04 4:51 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2010-07-04 4:51 ` Grant Likely
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).