From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: t-kristo@ti.com
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Tony Lindgren <tony@atomide.com>, Rajendra Nayak <rnayak@ti.com>,
Archit Taneja <archit@ti.com>,
"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: OMAP4430 produces boot warnings
Date: Thu, 22 Nov 2012 16:44:43 +0200 [thread overview]
Message-ID: <50AE3A5B.5040603@ti.com> (raw)
In-Reply-To: <1353594842.786.45.camel@sokoban>
[-- Attachment #1.1: Type: text/plain, Size: 1401 bytes --]
On 2012-11-22 16:34, Tero Kristo wrote:
> I guess you checked that DSS pwrdm is switching between RET and ON in
> your setup?
Yes:
# cat /debug/pm_debug/count |grep dss
[ 35.356567] pwrdm state mismatch(l3init_pwrdm) 3 != 1
[ 35.361938] pwrdm state mismatch(cam_pwrdm) 3 != 0
[ 35.366973] pwrdm state mismatch(ivahd_pwrdm) 3 != 1
[ 35.372253] pwrdm state mismatch(tesla_pwrdm) 3 != 1
[ 35.377532] pwrdm state mismatch(abe_pwrdm) 3 != 1
dss_pwrdm (RET),OFF:1,RET:11,INA:0,ON:11,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0
l3_dss_clkdm->dss_pwrdm (0)
then I load and unload the dss modules, and then:
# cat /debug/pm_debug/count |grep dss
[ 60.813629] pwrdm state mismatch(l3init_pwrdm) 3 != 1
[ 60.819000] pwrdm state mismatch(cam_pwrdm) 3 != 0
[ 60.824127] pwrdm state mismatch(ivahd_pwrdm) 3 != 1
[ 60.829376] pwrdm state mismatch(tesla_pwrdm) 3 != 1
[ 60.834625] pwrdm state mismatch(abe_pwrdm) 3 != 1
dss_pwrdm (ON),OFF:1,RET:21,INA:0,ON:22,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0
l3_dss_clkdm->dss_pwrdm (0)
>> Does the pwrdm mistakenly think that in RET state the DSS still keeps
>> the register contents?
>
> This might be the case, however the pwrdm code should be generic and
> handle all domains properly. What is the tree / branch / commit you are
> using for testing this stuff? I can take a look at this also.
arm-soc/for-next
Tomi
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: tomi.valkeinen@ti.com (Tomi Valkeinen)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP4430 produces boot warnings
Date: Thu, 22 Nov 2012 16:44:43 +0200 [thread overview]
Message-ID: <50AE3A5B.5040603@ti.com> (raw)
In-Reply-To: <1353594842.786.45.camel@sokoban>
On 2012-11-22 16:34, Tero Kristo wrote:
> I guess you checked that DSS pwrdm is switching between RET and ON in
> your setup?
Yes:
# cat /debug/pm_debug/count |grep dss
[ 35.356567] pwrdm state mismatch(l3init_pwrdm) 3 != 1
[ 35.361938] pwrdm state mismatch(cam_pwrdm) 3 != 0
[ 35.366973] pwrdm state mismatch(ivahd_pwrdm) 3 != 1
[ 35.372253] pwrdm state mismatch(tesla_pwrdm) 3 != 1
[ 35.377532] pwrdm state mismatch(abe_pwrdm) 3 != 1
dss_pwrdm (RET),OFF:1,RET:11,INA:0,ON:11,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0
l3_dss_clkdm->dss_pwrdm (0)
then I load and unload the dss modules, and then:
# cat /debug/pm_debug/count |grep dss
[ 60.813629] pwrdm state mismatch(l3init_pwrdm) 3 != 1
[ 60.819000] pwrdm state mismatch(cam_pwrdm) 3 != 0
[ 60.824127] pwrdm state mismatch(ivahd_pwrdm) 3 != 1
[ 60.829376] pwrdm state mismatch(tesla_pwrdm) 3 != 1
[ 60.834625] pwrdm state mismatch(abe_pwrdm) 3 != 1
dss_pwrdm (ON),OFF:1,RET:21,INA:0,ON:22,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0
l3_dss_clkdm->dss_pwrdm (0)
>> Does the pwrdm mistakenly think that in RET state the DSS still keeps
>> the register contents?
>
> This might be the case, however the pwrdm code should be generic and
> handle all domains properly. What is the tree / branch / commit you are
> using for testing this stuff? I can take a look at this also.
arm-soc/for-next
Tomi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 899 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121122/54916d83/attachment.sig>
next prev parent reply other threads:[~2012-11-22 14:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 23:03 OMAP4430 produces boot warnings Russell King - ARM Linux
2012-11-21 23:03 ` Russell King - ARM Linux
2012-11-22 12:42 ` Archit Taneja
2012-11-22 12:42 ` Archit Taneja
2012-11-22 13:42 ` Tomi Valkeinen
2012-11-22 13:42 ` Tomi Valkeinen
2012-11-22 14:34 ` Tero Kristo
2012-11-22 14:34 ` Tero Kristo
2012-11-22 14:44 ` Tomi Valkeinen [this message]
2012-11-22 14:44 ` Tomi Valkeinen
2012-11-23 9:34 ` Tero Kristo
2012-11-23 9:34 ` Tero Kristo
2012-11-26 6:48 ` Archit Taneja
2012-11-26 6:48 ` Archit Taneja
2012-11-26 12:14 ` Archit Taneja
2012-11-26 12:14 ` Archit Taneja
2012-11-27 11:23 ` Tomi Valkeinen
2012-11-27 11:23 ` Tomi Valkeinen
2012-11-27 11:56 ` Archit Taneja
2012-11-27 11:56 ` Archit Taneja
2012-11-27 12:21 ` Tomi Valkeinen
2012-11-27 12:21 ` Tomi Valkeinen
2012-11-27 12:31 ` Tero Kristo
2012-11-27 12:31 ` Tero Kristo
2012-11-28 10:44 ` Archit Taneja
2012-11-28 10:44 ` Archit Taneja
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=50AE3A5B.5040603@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=archit@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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.