From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: linux-omap <linux-omap@vger.kernel.org>,
spi-devel-general <spi-devel-general@lists.sourceforge.net>
Cc: David Brownell <dbrownell@users.sourceforge.net>,
Grant Likely <grant.likely@secretlab.ca>,
Kevin Hilman <khilman@deeprootsystems.com>
Subject: [PATCH v3 0/1] Put the OMAP2 SPI CS in inactive state when returning from suspend
Date: Fri, 12 Nov 2010 17:45:16 +0100 [thread overview]
Message-ID: <4CDD6F1C.7030809@free-electrons.com> (raw)
We notice that when system wake up from OFF mode, then CS is in inactive
state until the first SPI transfer.
For our design it lead to some conflict on this I/O.
Inactive state for CS when there is no transfer should be the correct
behavior: this is the purpose of these patches.
* Change from v2:
Use directly resume function of spi_master instead of using function
from spi_device as Grant Likely pointed it out.
Force this transition explicitly for each CS used by a device.
Gregory CLEMENT (1):
OMAP2: Spi: Force CS to be in inactive state after off-mode
transition
drivers/spi/omap2_mcspi.c | 29 +++++++++++++++++++++++++++++
1 files changed, 29 insertions(+), 0 deletions(-)
reply other threads:[~2010-11-12 16:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4CDD6F1C.7030809@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=dbrownell@users.sourceforge.net \
--cc=grant.likely@secretlab.ca \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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.