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: Fri, 13 May 2011 14:50:37 +0530 [thread overview]
Message-ID: <4DCCF7E5.2090009@st.com> (raw)
In-Reply-To: <BANLkTik2OxGdQ7z1JBAsE+=gc5UCgx3wEA@mail.gmail.com>
On 05/13/2011 12:24 PM, Linus Walleij wrote:
> 2011/5/13 viresh kumar <viresh.kumar@st.com>:
>> Linus, Jamie,
>>
>> Have you ever seen this kind of issue? Which spi slave memories did you used for testing?
>> I am using standard pl0022 and m25p80 driver. Tried in all modes: polling, interrupt, dma.
>
> Not really. I'll throw in a few people on CC and see if they have some hints.
>
Thanks guys.
Issue is solved now, data must be latched on Rising Edge and i have passed phase as falling edge.
--
viresh
next prev parent reply other threads:[~2011-05-13 9:20 UTC|newest]
Thread overview: 7+ 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 7:17 ` Jamie Iles
2011-05-11 7:19 ` viresh kumar
2011-05-13 3:52 ` viresh kumar
2011-05-13 6:54 ` Linus Walleij
2011-05-13 9:20 ` viresh kumar [this message]
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=4DCCF7E5.2090009@st.com \
--to=viresh.kumar@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).