From: viresh kumar <viresh.kumar@st.com>
To: Jamie Iles <jamie@jamieiles.com>
Cc: Dinesh Kumar SHARMA <dinesh.sharma@st.com>,
Linus WALLEIJ <linus.walleij@stericsson.com>,
Armando VISCONTI <armando.visconti@st.com>,
Shiraz HASHIM <shiraz.hashim@st.com>,
"spi-devel-general@lists.sourceforge.net"
<spi-devel-general@lists.sourceforge.net>,
Vikas MANOCHA <vikas.manocha@st.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [QUERY] Behavior of spi slave memories w.r.t chip select signal.
Date: Wed, 11 May 2011 12:49:42 +0530 [thread overview]
Message-ID: <4DCA388E.5060003@st.com> (raw)
In-Reply-To: <20110511071754.GN26703@pulham.picochip.com>
On 05/11/2011 12:47 PM, Jamie Iles wrote:
> What SPI controller are you using? I've seen a similar issue with the
> Synopsys DesignWare SPI controller where the controller manages the chip
> select itself, and once the FIFO is emptied the CS goes away, but the
> flash chip requires it to stay high for the whole transaction. In this
> case the workaround is to use a GPIO as a chip select and there are
> other controllers that do the same thing for the same reason (I think
> that pxa2xx_spi is one of them).
I am using amba pl022 controller and using external gpio's to control
chip select signal. cs is kept low for entire message, but still i am facing
this issue.
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@st.com (viresh kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [QUERY] Behavior of spi slave memories w.r.t chip select signal.
Date: Wed, 11 May 2011 12:49:42 +0530 [thread overview]
Message-ID: <4DCA388E.5060003@st.com> (raw)
In-Reply-To: <20110511071754.GN26703@pulham.picochip.com>
On 05/11/2011 12:47 PM, Jamie Iles wrote:
> What SPI controller are you using? I've seen a similar issue with the
> Synopsys DesignWare SPI controller where the controller manages the chip
> select itself, and once the FIFO is emptied the CS goes away, but the
> flash chip requires it to stay high for the whole transaction. In this
> case the workaround is to use a GPIO as a chip select and there are
> other controllers that do the same thing for the same reason (I think
> that pxa2xx_spi is one of them).
I am using amba pl022 controller and using external gpio's to control
chip select signal. cs is kept low for entire message, but still i am facing
this issue.
--
viresh
next prev parent reply other threads:[~2011-05-11 7:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 4:07 [QUERY] Behavior of spi slave memories w.r.t chip select signal viresh kumar
2011-05-11 4:07 ` viresh kumar
2011-05-11 7:17 ` Jamie Iles
2011-05-11 7:17 ` Jamie Iles
2011-05-11 7:19 ` viresh kumar [this message]
2011-05-11 7:19 ` viresh kumar
[not found] ` <4DCA0B77.8060700-qxv4g6HH51o@public.gmane.org>
2011-05-13 3:52 ` viresh kumar
2011-05-13 3:52 ` viresh kumar
[not found] ` <4DCCAB19.2020302-qxv4g6HH51o@public.gmane.org>
2011-05-13 6:54 ` Linus Walleij
2011-05-13 6:54 ` Linus Walleij
[not found] ` <BANLkTik2OxGdQ7z1JBAsE+=gc5UCgx3wEA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-13 9:20 ` viresh kumar
2011-05-13 9:20 ` viresh kumar
2011-05-13 9:04 ` Jamie Iles
2011-05-13 9:04 ` Jamie Iles
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=4DCA388E.5060003@st.com \
--to=viresh.kumar@st.com \
--cc=armando.visconti@st.com \
--cc=dinesh.sharma@st.com \
--cc=jamie@jamieiles.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=shiraz.hashim@st.com \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=vikas.manocha@st.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.