[PATCH] Kernel panic when MMC driver is built in

[GoogleCodeExporter]

When the omap-hsmmc driver is built into the kernel (not a module) it tries to 
make use of the omap cpufreq driver. However, this driver is loaded with 
late_initcall which means it isn't available when the platform devices are set 
up. This leads to a null pointer dereference.

What steps will reproduce the problem?
1. Compile 2.8.28.NIT.06 with MMC driver set to "y"
2. Boot this kernel
3. Kernel panic before framebuffer init

What is your device, RootFS, Multiboot and kernel versions?
N900, 0.0.6, None, 2.6.28.NIT.06

What was installation method?
Unpack rootfs to MMC card, build kernel as stated, install modules, put uImage 
on first fat partition, boot with u-boot.

Please provide any additional information below. Logs (logcat, dmesg) are
highly appreciated. (log collector available @
http://downloads.nitdroid.com/android-log-collector-1.1.0.apk)
No logs available due to early kernel panic before any output devices are 
initialized.

I am not sure why nokia chose to configure cpufreq with late_initcall instead 
of arch_initcall. However, it does not seem to affect anything. But I don't 
know for sure if there is a good reason why this was done. Attached patch 
changes it to arch_initcall so it will be registered at the same time as the 
other platform drivers, that is, before the platform devices try to use it.

Original issue reported on code.google.com by a.j.bux...@gmail.com on 8 Sep 2010 at 7:56

Attachments:

• 0001-Fix-CPU-frequency-driver-so-that-it-loads-before-the.patch

[GoogleCodeExporter]

Patch applied and commited: 
https://gitorious.org/android-n900/nitdroid-kernel/commit/84cf9b5379536ef14357db
b90c5ad6cf779c3264
Thanks.

Original comment by alexey.r...@gmail.com on 20 Apr 2011 at 8:29

• Changed state: Started

[GoogleCodeExporter]

Original comment by alexey.r...@gmail.com on 14 Feb 2012 at 7:45

• Changed state: Fixed