From: Hema Kalliguddi <hemahk@ti.com>
To: Hema Kalliguddi <hemahk@ti.com>, Felipe Balbi <balbi@ti.com>,
Jarkko Nikula <jhnikula@gmail.com>
Cc: OMAP Linux discussion <linux-omap@vger.kernel.org>
Subject: RE: What is missing from musb - linux-omap merge?
Date: Thu, 7 Apr 2011 18:31:41 +0530 [thread overview]
Message-ID: <254aac705c536b59ed64c6db922c1124@mail.gmail.com> (raw)
In-Reply-To: <4b3dcd4df940622c0f754669397c7482@mail.gmail.com>
Hi,
>-----Original Message-----
>From: Hema Kalliguddi [mailto:hemahk@ti.com]
>Sent: Thursday, April 07, 2011 6:29 PM
>To: balbi@ti.com; Jarkko Nikula
>Cc: OMAP Linux discussion
>Subject: RE: What is missing from musb - linux-omap merge?
>
>>-----Original Message-----
>>From: Felipe Balbi [mailto:balbi@ti.com]
>>Sent: Thursday, April 07, 2011 5:08 PM
>>To: Jarkko Nikula
>>Cc: Hema Kalliguddi; OMAP Linux discussion; Felipe Balbi
>>Subject: Re: What is missing from musb - linux-omap merge?
>>
>>On Thu, Apr 07, 2011 at 01:34:52PM +0300, Jarkko Nikula wrote:
>>> Hi
>>>
>>> On Thu, 7 Apr 2011 14:38:06 +0530
>>> Hema Kalliguddi <hemahk@ti.com> wrote:
>>>
>>> > I tried the core retention with v2.6.39-rc1 with
>>OMAP3630Zoom3 board
>>> > and don't observe any issues. Core is transitioning to
>>retention without
>>> > any issue,
>>> > with or without musb driver loaded.
>>> >
>>> > But on OMAP3430SDP I am observing the crash when try to do
>>> > echo mem > /sys/power/state.
>>> >
>>> > Attached is the fix for this issue and core transitions to
>>retention.
>>> >
>>> Hmm.. suspend/resume are fine on Nokia N900 with and without
>>the patch.
>>> Patch also didn't fix the idle retention.
>>>
>>> > When you say retention is not working can you please
>carify what is
>>> > happening?
>>> > are you trying in idle path retention or suspend/resume?
>>> >
>>> Sorry not being verbose enough, I was testing the idle retention.
>>>
>>> For me it looks these differencies are explained by different
>>> bootloaders. As Kevin told they may leave MUSB in a wrong
>>state. Was it
>>> so that before hwmod conversion the musb did IP reset etc
>>and now this
>>> feature is missing? So I'm thinking is this problem a regression or
>>> missing feature after hwmod conversion?
>>
>Hwmod will take care of restting the ip if the SYSC_HAS_SOFTRESET
>sysc_flag
>is set. And it is being set in the hwmod structure of OMAP3.
>
>I tested both idle path and suspend/resume retention and works fine
>on OMAP3430SDP.
Tested with OMAP3630Zoom3 board not with 3430SDP.
>I am wondering what might be the problem with N900. Is it
>works if you do
>the
>ip reset in the musb driver?
>
>Regards,
>Hema
>
>>it's possibly a regression. I remember we had softreset before. Should
>>be fixed.
>>
>>--
>>balbi
>>
>
prev parent reply other threads:[~2011-04-07 13:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 13:23 What is missing from musb - linux-omap merge? Jarkko Nikula
2011-04-06 13:34 ` Felipe Balbi
2011-04-06 14:51 ` Jarkko Nikula
2011-04-06 14:59 ` Kevin Hilman
2011-04-07 9:08 ` Hema Kalliguddi
2011-04-07 10:34 ` Jarkko Nikula
2011-04-07 11:38 ` Felipe Balbi
2011-04-07 12:59 ` Hema Kalliguddi
2011-04-07 13:01 ` Hema Kalliguddi [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=254aac705c536b59ed64c6db922c1124@mail.gmail.com \
--to=hemahk@ti.com \
--cc=balbi@ti.com \
--cc=jhnikula@gmail.com \
--cc=linux-omap@vger.kernel.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).