From: Matthias Fuchs <matthias.fuchs@esd.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx28: fix i.MX28 spi driver
Date: Sun, 15 Jan 2012 19:36:19 +0100 [thread overview]
Message-ID: <4F131CA3.4060702@esd.eu> (raw)
In-Reply-To: <CAOMZO5BduoFoOm4wx35OgJS5R3=-Cq5HyrA64qyZKpTYbLpZvw@mail.gmail.com>
On 01/15/2012 04:28 PM, Fabio Estevam wrote:
> On Sun, Jan 15, 2012 at 10:10 AM, Matthias Fuchs <matthias.fuchs@esd.eu> wrote:
>
>> That's what I also tried. But from the ref manual I got no idea.
>> When we do not find a hy to deassert the chip select manually, we cannot
>> avoid this read.
>
> I was assuming that the chip select deassertion was correctly being
> handled by the
> mxs_spi_end_xfer function.
>
> This function handles the LOCK_CS and IGNORE_CRC bits that are
> responsible for chip select assertion/deassertion.
>
> From the MX28 Reference Manual:
>
> "IGNORE_CRC bit: In SPI/SSI modes: When set to 1, deassert the chip
> select (SSn) pin after the command is executed."
Exactly. That's the point. It says "... after the command ...". So you need
a transfer after calling mxs_spi_end_xfer(). That's why the current code calls
it before transferring the final byte.
Matthias
>
> Then I tought that mxs_spi_end_xfer should be also called in the case
> where bitlen==0. In current code this does not happen.
>
>> It seems that the mainline linux only implements a GPIO based SPI driver.
>> So we cannot take it for reference.
>
> There is no mxs spi driver in the mainline kernel yet.
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
next prev parent reply other threads:[~2012-01-15 18:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 12:25 [U-Boot] [PATCH] mx28: fix i.MX28 spi driver Matthias Fuchs
2012-01-14 14:10 ` Marek Vasut
2012-01-14 18:37 ` Matthias Fuchs
2012-01-16 23:33 ` Alexander Keller
2012-01-17 19:34 ` Fabio Estevam
2012-01-14 18:46 ` Fabio Estevam
2012-01-14 18:53 ` Fabio Estevam
2012-01-14 18:54 ` Fabio Estevam
2012-01-14 20:09 ` Matthias Fuchs
2012-01-14 20:14 ` Fabio Estevam
2012-01-15 12:10 ` Matthias Fuchs
2012-01-15 15:28 ` Fabio Estevam
2012-01-15 18:36 ` Matthias Fuchs [this message]
2012-01-23 19:52 ` Fabio Estevam
2012-01-23 19:53 ` Marek Vasut
2012-01-24 8:40 ` Stefano Babic
2012-01-28 22:08 ` Fabio Estevam
2012-01-29 9:12 ` Stefano Babic
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=4F131CA3.4060702@esd.eu \
--to=matthias.fuchs@esd.eu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.