From: Kate Alhola <kate@iti.fi>
To: Wolfgang Denk <wd@denx.de>
Cc: David Jander <david.jander@protonic.nl>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: MPX8xx: MMC over SPI....
Date: Wed, 10 Mar 2004 01:23:19 +0200 [thread overview]
Message-ID: <404E51E7.4070909@iti.fi> (raw)
In-Reply-To: <20040309152515.A912DC0655@atlas.denx.de>
Wolfgang Denk wrote:
>>I am going to write a SPI driver and on top of that a MMC driver for linux for
>>the MPC852T, unless there is something already out there.
>>Anyone tried this before and has some sources to share? Or pointers to
>>sources?
>>
>>
I am just doing same thing for mpc5200 ( http://www.iti.fi/iti5200.php )
board.
In this board there is MMC connector connected to PSC
>
>The SPI driver is there, but I don't recommend to use it for any type
>of data transfers that require any significant bandwidth. Motorola
>writes:
>
>
There is simple spi driver arch/ppc/8260_io/cpm_spi.c but i think that
one like
i2c subsystem will be much more usefull. I have been planning make one based
on i2c driver.
I am plannigg 3-layer model like in i2c or USB. interface-HW-driver in
lowest level,
then subsystem driver and then target HW driver. Like in this case
PSC_SPI-> SPI_subsystem->MMC ---->FS
> The SPI was not designed to be a high-bandwidth channel. It
> can run very quickly for bursts of up to 16-bits. But the
> peripheral has no FIFO and low priority in the MPC860 and
> thus you cannot burst lots of data quickly through the
> interface.
> ...
> Note that the SPI is of lower priority internally than the
> SCCs, thus, the SPI will be the first device to be "starved".
> Since it has no FIFO, it is especially sensitive to underruns.
> The best way to prevent this is to use a buffer size of 1
> "character" (of size programmed in the mode register).
> ...
>
>
>
There is same problem in mpc5200 SPI and for this reason i am planning to
use PSC in SPI mode. Then i will have fifo etc. I am also considering to
use bestcom DMA. I just have heard that there is lot of problems with it
when used with I2S. What is actually causing the problems ?
Bestcom API library ? Should it be better to use directly bestcom HW
without library ?
>Also, you should be aware that the SPI protocol is implemented as
>microcode running on the CPM, so any high-speed data transfers will
>suck up CPM performance.
>
>
Of cource it does not give best performance but it is also wery simple
glueless
interface to cheap small low cost mass media. If we like to have full fast
MMC/SD interface then we should consider some FPGA implementation
but in most cases simpler will give enough proformace.
Kate
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-09 23:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 13:18 MPX8xx: MMC over SPI David Jander
2004-03-09 13:41 ` Jaap-Jan Boor
2004-03-09 15:25 ` Wolfgang Denk
2004-03-09 23:23 ` Kate Alhola [this message]
2004-03-09 23:59 ` Wolfgang Denk
2004-03-10 8:32 ` Jaap-Jan Boor
2004-03-13 13:37 ` Kate Alhola
2004-03-14 5:01 ` some LINUX boot-up message loss song sam
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=404E51E7.4070909@iti.fi \
--to=kate@iti.fi \
--cc=david.jander@protonic.nl \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wd@denx.de \
/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).