From: Kevin Hilman <khilman@deeprootsystems.com>
To: Gregory CLEMENT <gclement00@gmail.com>
Cc: spi-devel-general <spi-devel-general@lists.sourceforge.net>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/2] Put OMAP2 SPI CS in unactive state when return from suspend
Date: Thu, 12 Aug 2010 07:28:29 -0700 [thread overview]
Message-ID: <87tymzucqa.fsf@deeprootsystems.com> (raw)
In-Reply-To: <AANLkTinPbOR2OUyfiCLkkbV6gCjxib+-mmMKNf9mzeDC@mail.gmail.com> (Gregory CLEMENT's message of "Thu, 12 Aug 2010 10:54:00 +0200")
Gregory CLEMENT <gclement00@gmail.com> writes:
> 2010/8/11 Kevin Hilman <khilman@deeprootsystems.com>
>>
>> Gregory CLEMENT <gclement00@gmail.com> writes:
>>
>> > We notice that when system wake up from OFF mode, then CS is in
>> > unactive state until the first SPI transfert.
>> > For our design it lead to some conflict on this I/O.
>> > Unactive state for CS when there is no transfert shoudl be the correct
>> > behaviour: this is the purpose of these patches.
>>
>> This approach handles an off-mode transition during suspend, but if
>> off-mode is enabled, you can also have an off-mode transition during
>> idle.
>>
>
> Well maybe I didn't use the correct words.
> During the system life, I monitored the CS behaviour using a oscilloscope.
> I also activate debug in omap2_mcspi, so I see when driver disable the
> clocks and restore context when device is not used.
> Each time the CS is in the correct state. It is only when there is a
> suspend with the following configuration that on resume the CS is in
> wrong state( ie activated)
OK, that should be more clear in the changelog. The way I understood
your description, the problem was related to an off-mode transition.
>
> echo 1 > /mnt/pm_debug/enable_off_mode
> echo 0 > /mnt/pm_debug/core_pwrdm/suspend
fyi... this part isn't needed. You're telling the OMAP PM core that
you want the CORE powerdomain to go into off-mode, but you've you've
already done that by the 'enable_off_mode' flag, which enables *all*
powerdomains to hit off mode.
> echo 1 > /mnt/pm_debug/voltage_off_while_idle
>
>
>>
>> Since you didn't describe what the conflicts you're seeing are, I would
>> assume that you'll have the same problems in idle as in suspend, and
>> this series doesn't address the idle case.
>
> I didn't see any problem in idle case, just when system resume from a
> suspend to ram (echo mem > /sys/power/state)
OK, I'd recommend you update the changelog to make that more clear.
Then, I'll leave it to the SPI folks to review your patch.
Kevin
prev parent reply other threads:[~2010-08-12 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 14:42 [PATCH 0/2] Put OMAP2 SPI CS in unactive state when return from suspend Gregory CLEMENT
2010-08-11 18:21 ` Kevin Hilman
[not found] ` <871va52ent.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2010-08-12 8:43 ` Gregory CLEMENT
2010-08-12 8:54 ` Gregory CLEMENT
2010-08-12 14:28 ` Kevin Hilman [this message]
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=87tymzucqa.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=gclement00@gmail.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 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).