On 12/03/2013 03:05 PM, Tobias Jakobi wrote: > Hello, > > here a newly introduced one: > https://bugzilla.kernel.org/show_bug.cgi?id=66441 [1] solves the issue However, digging further, the root of the crash starts here: "platform 4b501000.aes: Cannot lookup hwmod 'aes'" with this, the following happens: a) omap_device does not register a pm_domain (since it cannot find hwmod entry). b) driver does not know about (a), does a pm_runtime_get_sync which never fails c) tries to read the revision register (as part of probe) without clock. generates the issue mentioned above. Now, there are three issues here: a) hwmod entries are not present -> this is addressed in [1] b) omap_device pm_domain is not handled - fixed in [2] c) aes driver needs to handle error case when pm_runtime_get_sync fails. addressed in [3]. [1] http://marc.info/?l=linux-kernel&m=138541593010221&w=2 + http://marc.info/?l=linux-kernel&m=138541603810300&w=2 [2] https://patchwork.kernel.org/patch/3280531/ [3] https://patchwork.kernel.org/patch/3280571/ -- Regards, Nishanth Menon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
