summaryrefslogtreecommitdiffstats
path: root/drivers/pwm/pwm-twl.c
diff options
context:
space:
mode:
authorMike Dunn <mikedunn@newsguy.com>2013-08-08 10:00:37 -0700
committerThierry Reding <thierry.reding@gmail.com>2013-09-03 13:09:17 +0200
commit1e185c7aafbb56580feaa5bdbc9e4b1d8efaf710 (patch)
tree802a9dd5436b907cb78355599674ac7e085d620a /drivers/pwm/pwm-twl.c
parentac872bc9ed4452dccfbcebe7d273350103464998 (diff)
downloadtalos-op-linux-1e185c7aafbb56580feaa5bdbc9e4b1d8efaf710.tar.gz
talos-op-linux-1e185c7aafbb56580feaa5bdbc9e4b1d8efaf710.zip
pwm: pxa: Use module_platform_driver
Commit 76abbdde2d95a3807d0dc6bf9f84d03d0dbd4f3d pwm: Add sysfs interface causes a kernel oops due to a null pointer dereference on PXA platforms. This happens because the class added by the patch is registered in a subsys_initcall (initcall4), but the pxa pwm driver is registered in arch_initcall (initcall3). If the class is not registered before the driver probe function runs, the oops occurs in device_add() when the uninitialized pointers in struct class are dereferenced. I don't see a reason that the driver must be an arch_initcall, so this patch makes it a regular module_platform_driver (initcall6), preventing the oops. Signed-off-by: Mike Dunn <mikedunn@newsguy.com> Acked-by: Robert Jarzmik <robert.jarzmik@free.fr> Acked-by: Marek Vasut <marex@denx.de> Signed-off-by: Thierry Reding <thierry.reding@gmail.com>
Diffstat (limited to 'drivers/pwm/pwm-twl.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud