From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: linux-omap mailing list <linux-omap@vger.kernel.org>
Subject: OMAP4 hwmod problem when unloading omapdss
Date: Fri, 20 Jan 2012 12:09:53 +0200 [thread overview]
Message-ID: <1327054193.1921.37.camel@deskari> (raw)
[-- Attachment #1: Type: text/plain, Size: 3438 bytes --]
Hi Benoit,
I see the below WARNING on v3.3-rc1, running on OMAP4460 Panda, when I
unload the DSS modules. This didn't happen on v3.2, or linux-next from a
few weeks ago.
Tomi
[ 29.667572] ------------[ cut here ]------------
[ 29.667572] WARNING: at arch/arm/mach-omap2/omap_hwmod.c:1604 _idle+0x164/0x17c()
[ 29.674774] omap_hwmod: dss_hdmi: idle state can only be entered from enabled state
[ 29.688293] Modules linked in: cfbimgblt cfbfillrect cfbcopyarea omapdss(-) [last unloaded: panel
_dvi]
[ 29.693084] [<c001b614>] (unwind_backtrace+0x0/0xf0) from [<c0041d70>] (warn_slowpath_common+0x4c
/0x64)
[ 29.703918] [<c0041d70>] (warn_slowpath_common+0x4c/0x64) from [<c0041e1c>] (warn_slowpath_fmt+0x
30/0x40)
[ 29.717987] [<c0041e1c>] (warn_slowpath_fmt+0x30/0x40) from [<c0027fdc>] (_idle+0x164/0x17c)
[ 29.724670] [<c0027fdc>] (_idle+0x164/0x17c) from [<c0028850>] (omap_hwmod_idle+0x24/0x40)
[ 29.729461] [<c0028850>] (omap_hwmod_idle+0x24/0x40) from [<c003b670>] (omap_device_idle_hwmods+0
x24/0x3c)
[ 29.745086] [<c003b670>] (omap_device_idle_hwmods+0x24/0x3c) from [<c003b860>] (_omap_device_deac
tivate+0x9c/0x138)
[ 29.745086] [<c003b860>] (_omap_device_deactivate+0x9c/0x138) from [<c003c270>] (omap_device_idle
+0x28/0x54)
[ 29.745086] [<c003c270>] (omap_device_idle+0x28/0x54) from [<c003c2b8>] (_od_runtime_suspend+0x1c
/0x24)
[ 29.776672] [<c003c2b8>] (_od_runtime_suspend+0x1c/0x24) from [<c02b5a68>] (__rpm_callback+0x70/0
x98)
[ 29.786346] [<c02b5a68>] (__rpm_callback+0x70/0x98) from [<c02b5f08>] (rpm_suspend+0x240/0x6c0)
[ 29.786346] [<c02b5f08>] (rpm_suspend+0x240/0x6c0) from [<c02b734c>] (__pm_runtime_suspend+0x5c/0
x74)
[ 29.799774] [<c02b734c>] (__pm_runtime_suspend+0x5c/0x74) from [<c02b2ec4>] (pm_generic_runtime_i
dle+0x44/0x4c)
[ 29.807586] [<c02b2ec4>] (pm_generic_runtime_idle+0x44/0x4c) from [<c02b5a68>] (__rpm_callback+0x
70/0x98)
[ 29.807586] [<c02b5a68>] (__rpm_callback+0x70/0x98) from [<c02b64fc>] (rpm_idle+0x100/0x228)
[ 29.831085] [<c02b64fc>] (rpm_idle+0x100/0x228) from [<c02b66f4>] (__pm_runtime_idle+0x5c/0x74)
[ 29.843658] [<c02b66f4>] (__pm_runtime_idle+0x5c/0x74) from [<c02ae6a4>] (__device_release_driver
+0x50/0xc0)
[ 29.846649] [<c02ae6a4>] (__device_release_driver+0x50/0xc0) from [<c02aed0c>] (driver_detach+0xb
4/0xb8)
[ 29.863891] [<c02aed0c>] (driver_detach+0xb4/0xb8) from [<c02ae580>] (bus_remove_driver+0x7c/0xc0
)
[ 29.870086] [<c02ae580>] (bus_remove_driver+0x7c/0xc0) from [<bf0000f0>] (omap_dss_remove+0x14/0x
6c [omapdss])
[ 29.877929] [<bf0000f0>] (omap_dss_remove+0x14/0x6c [omapdss]) from [<c02afe60>] (platform_drv_re
move+0x18/0x1c)
[ 29.893463] [<c02afe60>] (platform_drv_remove+0x18/0x1c) from [<c02ae6c4>] (__device_release_driv
er+0x70/0xc0)
[ 29.901489] [<c02ae6c4>] (__device_release_driver+0x70/0xc0) from [<c02aed0c>] (driver_detach+0xb
4/0xb8)
[ 29.901489] [<c02aed0c>] (driver_detach+0xb4/0xb8) from [<c02ae580>] (bus_remove_driver+0x7c/0xc0
)
[ 29.924499] [<c02ae580>] (bus_remove_driver+0x7c/0xc0) from [<bf020e98>] (omap_dss_exit+0x48/0x58
[omapdss])
[ 29.932586] [<bf020e98>] (omap_dss_exit+0x48/0x58 [omapdss]) from [<c0098f54>] (sys_delete_module
+0x164/0x254)
[ 29.940399] [<c0098f54>] (sys_delete_module+0x164/0x254) from [<c0013c80>] (ret_fast_syscall+0x0/
0x3c)
[ 29.955139] ---[ end trace 52be023ca95d7e20 ]---
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2012-01-20 10:09 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=1327054193.1921.37.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=b-cousson@ti.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