From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pali =?utf-8?q?Roh=C3=A1r?= Subject: Re: v3.19: Nokia N900 (qemu) - omap_aes error Date: Wed, 18 Feb 2015 22:36:41 +0100 Message-ID: <201502182236.41771@pali> References: <201501311629.36431@pali> <201502091225.00497@pali> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5917903.8il0gUBShX"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <201502091225.00497@pali> Sender: linux-kernel-owner@vger.kernel.org To: linux-omap@vger.kernel.org Cc: Tony Lindgren , linux-kernel@vger.kernel.org, Pavel Machek , Sebastian Reichel , Aaro Koskinen , Ivaylo Dimitrov , Felipe Balbi , Nishanth Menon List-Id: linux-omap@vger.kernel.org --nextPart5917903.8il0gUBShX Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Monday 09 February 2015 12:25:00 Pali Roh=C3=A1r wrote: > On Saturday 31 January 2015 16:29:36 Pali Roh=C3=A1r wrote: > > Hello, > >=20 > > when I enable problematic omap_aes.ko driver (also in DT) > > for Nokia N900 machine in qemu (it emulates OMAP GP device, > > not HS) I get this error message in dmesg at modprobe time: > >=20 > > [ 37.660339] ------------[ cut here ]------------ > > [ 37.663940] WARNING: CPU: 0 PID: 173 at arch/arm/mach- > > omap2/omap_hwmod.c:2182 _idle+0x28/0x64() > > [ 37.668762] omap_hwmod: aes: idle state can only be > > entered from enabled state > > [ 37.672271] Modules linked in: omap_aes(+) > > [ 37.675933] CPU: 0 PID: 173 Comm: modprobe Not tainted > > 3.19.0- rc5+ #299 > > [ 37.679534] Hardware name: Nokia RX-51 board > > [ 37.683227] [] (unwind_backtrace) from > > [] (show_stack+0x10/0x14) > > [ 37.686920] [] (show_stack) from [] > > (warn_slowpath_common+0x84/0xac) > > [ 37.690765] [] (warn_slowpath_common) from > > [] (warn_slowpath_fmt+0x2c/0x3c) > > [ 37.694366] [] (warn_slowpath_fmt) from > > [] (_idle+0x28/0x64) > > [ 37.698791] [] (_idle) from [] > > (omap_hwmod_idle+0x30/0x78) > > [ 37.702636] [] (omap_hwmod_idle) from > > [] (omap_device_idle+0x48/0x6c) > > [ 37.707153] [] (omap_device_idle) from > > [] (_od_runtime_suspend+0x1c/0x24) > > [ 37.710723] [] (_od_runtime_suspend) from > > [] (__rpm_callback+0x8c/0xdc) > > [ 37.714385] [] (__rpm_callback) from > > [] (rpm_callback+0x70/0x88) > > [ 37.717987] [] (rpm_callback) from [] > > (rpm_suspend+0x2e8/0x5a4) > > [ 37.721710] [] (rpm_suspend) from [] > > (__pm_runtime_idle+0x58/0x9c) > > [ 37.725402] [] (__pm_runtime_idle) from > > [] (omap_aes_probe+0x15c/0x448 [omap_aes]) > > [ 37.733489] [] (omap_aes_probe [omap_aes]) from > > [] (platform_drv_probe+0x48/0x90) > > [ 37.740936] [] (platform_drv_probe) from > > [] (really_probe+0xac/0x1e0) > > [ 37.745025] [] (really_probe) from [] > > (driver_probe_device+0x30/0x48) > > [ 37.749847] [] (driver_probe_device) from > > [] (__driver_attach+0x60/0x84) > > [ 37.753601] [] (__driver_attach) from > > [] (bus_for_each_dev+0x50/0x84) > > [ 37.758422] [] (bus_for_each_dev) from > > [] (bus_add_driver+0xac/0x1bc) > > [ 37.762207] [] (bus_add_driver) from > > [] (driver_register+0x9c/0xe0) > > [ 37.765899] [] (driver_register) from > > [] (do_one_initcall+0x100/0x1b0) > > [ 37.769653] [] (do_one_initcall) from > > [] (do_init_module+0x34/0x158) > > [ 37.773590] [] (do_init_module) from > > [] (SyS_init_module+0x54/0x64) > > [ 37.777252] [] (SyS_init_module) from > > [] (ret_fast_syscall+0x0/0x30) > > [ 37.780975] ---[ end trace 86c3e025b92e700d ]--- > > [ 37.784667] omap-aes 480c5000.aes: OMAP AES hw accel rev: > > 0.0 [ 37.789794] of_dma_request_slave_channel: dma-names > > property of node '/ocp/aes@480c5000' missing or empty > > [ 37.797668] omap-aes 480c5000.aes: Unable to request in > > DMA channel > > [ 37.801391] omap_aes_dma_init: error: -12 > >=20 > > Error is not fatal, kernel does not crash and qemu emulation > > working fine. But error is there. > >=20 > > I'm sure that qemu does not support omap aes hw emulation > > and so I except error message about missing hw part (or > > something else). But not above unwind_backtrace error > > message. > >=20 > > Any idea why it happens? It is probably not related to AES > > but to DMA. It is for OMAP GP device (but emulated), so can > > TI comment this problem (as this is not HS under NDA)? >=20 > Hello, >=20 > what does that error line means? >=20 > [ 37.668762] omap_hwmod: aes: idle state can only be entered > from enabled state >=20 > Is not it bug in omap_hwmod.c code? In qemu dmesg log I see this debug line: [ 0.297851] omap_hwmod: aes: cannot be enabled for reset (3) So aes is in disabled state. Should not omap-aes driver check for aes state if is enabled? =2D-=20 Pali Roh=C3=A1r pali.rohar@gmail.com --nextPart5917903.8il0gUBShX Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEABECAAYFAlTlBekACgkQi/DJPQPkQ1LOLACfeuR6Fm/8lskc0p4gtg3ujvrn d1oAnjfW7crw8Uq4LDpeLHV/YTCaVuGB =IyXU -----END PGP SIGNATURE----- --nextPart5917903.8il0gUBShX--