From: Marek Vasut <marex@denx.de>
To: Trent Piepho <tpiepho@gmail.com>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
spi-devel-general@lists.sourceforge.net,
Shawn Guo <shawn.guo@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2 01/12] spi/mxs: Always set LOCK_CS
Date: Sun, 14 Apr 2013 20:01:52 +0200 [thread overview]
Message-ID: <201304142001.52391.marex@denx.de> (raw)
In-Reply-To: <1364905195-24286-1-git-send-email-tpiepho@gmail.com>
Hello Trent,
> There are two bits which control the CS line in the CTRL0 register:
> LOCK_CS and IGNORE_CRC. The latter would be better named DEASSERT_CS
> in SPI mode.
>
> LOCK_CS keeps CS asserted though the entire transfer. This should
> always be set. The DMA code will always set it, explicitly on the
> first segment of the first transfer, and then implicitly on all the
> rest by never clearing the bit from the value read from the ctrl0
> register.
>
> The only reason to not set LOCK_CS would be to attempt an altered
> protocol where CS pulses between each word. Though don't get your
> hopes up if you want to do this, as the hardware doesn't appear to do
> this in any sane manner.
>
> The code can be simplified by just setting LOCK_CS once and then not
> needing to deal with it in the PIO and DMA transfer functions.
>
> Signed-off-by: Trent Piepho <tpiepho@gmail.com>
> Cc: Marek Vasut <marex@denx.de>
> Cc: Fabio Estevam <fabio.estevam@freescale.com>
> Cc: Shawn Guo <shawn.guo@linaro.org>
Will we see a V3 of this stuff? I don't want to see this lost.
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 01/12] spi/mxs: Always set LOCK_CS
Date: Sun, 14 Apr 2013 20:01:52 +0200 [thread overview]
Message-ID: <201304142001.52391.marex@denx.de> (raw)
In-Reply-To: <1364905195-24286-1-git-send-email-tpiepho@gmail.com>
Hello Trent,
> There are two bits which control the CS line in the CTRL0 register:
> LOCK_CS and IGNORE_CRC. The latter would be better named DEASSERT_CS
> in SPI mode.
>
> LOCK_CS keeps CS asserted though the entire transfer. This should
> always be set. The DMA code will always set it, explicitly on the
> first segment of the first transfer, and then implicitly on all the
> rest by never clearing the bit from the value read from the ctrl0
> register.
>
> The only reason to not set LOCK_CS would be to attempt an altered
> protocol where CS pulses between each word. Though don't get your
> hopes up if you want to do this, as the hardware doesn't appear to do
> this in any sane manner.
>
> The code can be simplified by just setting LOCK_CS once and then not
> needing to deal with it in the PIO and DMA transfer functions.
>
> Signed-off-by: Trent Piepho <tpiepho@gmail.com>
> Cc: Marek Vasut <marex@denx.de>
> Cc: Fabio Estevam <fabio.estevam@freescale.com>
> Cc: Shawn Guo <shawn.guo@linaro.org>
Will we see a V3 of this stuff? I don't want to see this lost.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-04-14 18:01 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 12:19 [PATCH V2 01/12] spi/mxs: Always set LOCK_CS Trent Piepho
2013-04-02 12:19 ` Trent Piepho
[not found] ` <1364905195-24286-1-git-send-email-tpiepho-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-04-02 12:19 ` [PATCH V2 02/12] spi/mxs: Remove mxs_spi_enable and mxs_spi_disable Trent Piepho
2013-04-02 12:19 ` Trent Piepho
2013-04-02 12:19 ` [PATCH V2 03/12] spi/mxs: Change flag arguments in txrx functions to bit flags Trent Piepho
2013-04-02 12:19 ` Trent Piepho
[not found] ` <1364905195-24286-3-git-send-email-tpiepho-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-04-02 23:24 ` Marek Vasut
2013-04-02 23:24 ` Marek Vasut
2013-04-02 12:19 ` [PATCH V2 04/12] spi/mxs: Fix extra CS pulses and read mode in multi-transfer messages Trent Piepho
2013-04-02 12:19 ` Trent Piepho
2013-04-02 12:19 ` [PATCH V2 05/12] spi/mxs: Fix chip select control bits in DMA mode Trent Piepho
2013-04-02 12:19 ` Trent Piepho
[not found] ` <1364905195-24286-5-git-send-email-tpiepho-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-04-02 23:29 ` Marek Vasut
2013-04-02 23:29 ` Marek Vasut
2013-04-02 12:19 ` [PATCH V2 06/12] spi/mxs: Remove full duplex check, spi core already does it Trent Piepho
2013-04-02 12:19 ` Trent Piepho
2013-04-02 12:19 ` [PATCH V2 07/12] spi/mxs: Remove bogus setting of ssp clk rate field Trent Piepho
2013-04-02 12:19 ` Trent Piepho
2013-04-02 12:19 ` [PATCH V2 08/12] spi/mxs: Fix race in setup method Trent Piepho
2013-04-02 12:19 ` Trent Piepho
[not found] ` <1364905195-24286-8-git-send-email-tpiepho-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-04-02 23:31 ` Marek Vasut
2013-04-02 23:31 ` Marek Vasut
[not found] ` <201304030131.37782.marex-ynQEQJNshbs@public.gmane.org>
2013-04-03 2:12 ` Trent Piepho
2013-04-03 2:12 ` Trent Piepho
2013-04-03 2:27 ` Marek Vasut
2013-04-03 2:27 ` Marek Vasut
[not found] ` <201304030427.41297.marex-ynQEQJNshbs@public.gmane.org>
2013-04-03 6:08 ` Trent Piepho
2013-04-03 6:08 ` Trent Piepho
[not found] ` <CA+7tXih2r6YFE80y7z7Nj7c0Ytvh+v56-SrbS+VQ7kCW3KBRXA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-03 6:50 ` Marek Vasut
2013-04-03 6:50 ` Marek Vasut
[not found] ` <201304030850.31752.marex-ynQEQJNshbs@public.gmane.org>
2013-04-03 9:32 ` Trent Piepho
2013-04-03 9:32 ` Trent Piepho
2013-04-02 12:19 ` [PATCH V2 09/12] spi/mxs: Remove check of spi mode bits Trent Piepho
2013-04-02 12:19 ` Trent Piepho
2013-04-02 12:19 ` [PATCH V2 10/12] spi/mxs: Clean up setup_transfer function Trent Piepho
2013-04-02 12:19 ` Trent Piepho
[not found] ` <1364905195-24286-10-git-send-email-tpiepho-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-04-02 23:35 ` Marek Vasut
2013-04-02 23:35 ` Marek Vasut
2013-04-02 12:19 ` [PATCH V2 11/12] spi/mxs: Don't set clock for each xfer Trent Piepho
2013-04-02 12:19 ` Trent Piepho
[not found] ` <1364905195-24286-11-git-send-email-tpiepho-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-04-02 23:38 ` Marek Vasut
2013-04-02 23:38 ` Marek Vasut
2013-04-02 12:19 ` [PATCH V2 12/12] spi/mxs: Use u32 instead of uint32_t Trent Piepho
2013-04-02 12:19 ` Trent Piepho
2013-04-02 23:18 ` [PATCH V2 01/12] spi/mxs: Always set LOCK_CS Marek Vasut
2013-04-02 23:18 ` Marek Vasut
[not found] ` <201304030118.42976.marex-ynQEQJNshbs@public.gmane.org>
2013-07-10 13:49 ` Fabio Estevam
2013-07-10 13:49 ` Fabio Estevam
2013-07-10 15:29 ` Lothar Waßmann
2013-07-10 15:29 ` Lothar Waßmann
[not found] ` <20957.32214.721252.361301-VjFSrY7JcPWvSplVBqRQBQ@public.gmane.org>
2013-07-18 1:08 ` Trent Piepho
2013-04-03 1:41 ` Shawn Guo
2013-04-03 1:41 ` Shawn Guo
2013-04-14 18:01 ` Marek Vasut [this message]
2013-04-14 18:01 ` Marek Vasut
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=201304142001.52391.marex@denx.de \
--to=marex@denx.de \
--cc=fabio.estevam@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=shawn.guo@linaro.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=tpiepho@gmail.com \
/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.