From: Michael Walle <michael@walle.cc>
To: u-boot@lists.denx.de
Subject: [U-Boot] FSL eSPI driver is a mess, hack attached.
Date: Fri, 14 Mar 2014 22:45:20 +0100 [thread overview]
Message-ID: <201403142245.20222.michael@walle.cc> (raw)
In-Reply-To: <1394790386-21410-1-git-send-email-Joakim.Tjernlund@transmode.se>
Am Freitag, 14. M?rz 2014, 10:46:26 schrieb Joakim Tjernlund:
> The fsl_espi.c is wreck w.r.t large TX data.
> Below is what I had to hack to load a FPGA over SPI and
> what is the malloc hack good for? This does not work
> well for TXing several MB data.
>
> The driver needs to be rewritten and I do not have the
> time so I post what I got in the hope it can help someone
> else or trigger a rewrite.
although this is a bit harsh, i'm inclined to agree. last time i tried this
driver, apart from reading from a spi flash, nothing else was working. even a
spi unlock was broken. if you actually capture the spi pins on a scope you see
that mostly garbage is transmitted in some cases (eg. using the raw spi
commands on the cli). fun fact: the spi unlock actually resulted in a spi lock
;)
i guess freescale haven't put much love into this one ;)
-michael
next prev parent reply other threads:[~2014-03-14 21:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 9:46 [U-Boot] FSL eSPI driver is a mess, hack attached Joakim Tjernlund
2014-03-14 21:45 ` Michael Walle [this message]
2014-03-15 11:33 ` Joakim Tjernlund
2014-03-17 12:13 ` Michael Walle
2014-04-16 21:09 ` York Sun
2014-04-17 3:48 ` Mingkai.Hu at freescale.com
-- strict thread matches above, loose matches on Subject: below --
2014-07-23 11:27 Eliot Dudley
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=201403142245.20222.michael@walle.cc \
--to=michael@walle.cc \
--cc=u-boot@lists.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