From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: barebox@lists.infradead.org
Subject: [PATCH 0/8] atmtel: fix spi driver + rm9200
Date: Tue, 6 Nov 2012 20:30:10 +0100 [thread overview]
Message-ID: <20121106193010.GE25679@game.jcrosoft.org> (raw)
HI,
The following changes since commit d74bef2b04a3ccf7339ba916e56830bb2feae957:
mount: add compatibility to old mount command (2012-11-02 21:26:29 +0100)
are available in the git repository at:
git://git.jcrosoft.org/barebox.git tags/atmel_spi_fix
for you to fetch changes up to 7e7b7aa81cdf7e47a8f828818f1e453a27046c38:
at91rm9200: fix spi cs support (2012-11-06 04:39:09 +0800)
----------------------------------------------------------------
atmel spi support fix
The current drivers for atmel have a lot of issues but we are lucky
enough if you use it one device + one master instance it will work on
most of the spi device
but this will not work on mmc spi or multi-master instance or multi-device
so now fix all those issues
- fix the cs support
- fix setup setup support
- do not call setup before each transfert
- add sanity check
now the atmel spi work on rm9200, mmc spi and at24, at45, eeprom
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
----------------------------------------------------------------
Jean-Christophe PLAGNIOL-VILLARD (8):
atmel_spi: use device id as bus num
atmel_spi: split transfert to atmel_spi_do_xfer
atmel_spi: after setup the cs need to be disable
atmel_spi: add sanity check in setup
atmel_spi: fix cs support
atmel_spi: drop setup during transfer
atmel_spi: add cs change support
at91rm9200: fix spi cs support
arch/arm/mach-at91/at91rm9200_devices.c | 7 ++++++-
drivers/spi/atmel_spi.c | 260 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------------------------------------------------
2 files changed, 196 insertions(+), 71 deletions(-)
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2012-11-06 19:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 19:30 Jean-Christophe PLAGNIOL-VILLARD [this message]
2012-11-06 19:33 ` [PATCH 1/8] atmel_spi: use device id as bus num Jean-Christophe PLAGNIOL-VILLARD
2012-11-06 19:33 ` [PATCH 2/8] atmel_spi: split transfert to atmel_spi_do_xfer Jean-Christophe PLAGNIOL-VILLARD
2012-11-13 14:45 ` Thomas Petazzoni
2012-11-06 19:33 ` [PATCH 3/8] atmel_spi: after setup the cs need to be disable Jean-Christophe PLAGNIOL-VILLARD
2012-11-06 19:33 ` [PATCH 4/8] atmel_spi: add sanity check in setup Jean-Christophe PLAGNIOL-VILLARD
2012-11-06 19:33 ` [PATCH 5/8] atmel_spi: fix cs support Jean-Christophe PLAGNIOL-VILLARD
2012-11-06 19:33 ` [PATCH 6/8] atmel_spi: drop setup during transfer Jean-Christophe PLAGNIOL-VILLARD
2012-11-06 19:33 ` [PATCH 7/8] atmel_spi: add cs change support Jean-Christophe PLAGNIOL-VILLARD
2012-11-06 19:33 ` [PATCH 8/8] at91rm9200: fix spi cs support Jean-Christophe PLAGNIOL-VILLARD
2012-11-12 7:36 ` [PATCH 0/8] atmtel: fix spi driver + rm9200 Sascha Hauer
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=20121106193010.GE25679@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=barebox@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