summaryrefslogtreecommitdiffstats
path: root/arch/arm/plat-omap/include/plat/omap_hwmod.h
diff options
context:
space:
mode:
authorPeter Ujfalusi2012-08-23 15:54:09 +0200
committerBenoit Cousson2012-09-06 14:21:16 +0200
commit3956a1a0d1e072c321fcf1b1136e35a22be12af5 (patch)
tree8931d206ebaaad50a72380d78d984ebf8bd72e40 /arch/arm/plat-omap/include/plat/omap_hwmod.h
parentarm/dts: Add tps65217 regulator DT data to am335x-bone.dts (diff)
downloadkernel-qcow2-linux-3956a1a0d1e072c321fcf1b1136e35a22be12af5.tar.gz
kernel-qcow2-linux-3956a1a0d1e072c321fcf1b1136e35a22be12af5.tar.xz
kernel-qcow2-linux-3956a1a0d1e072c321fcf1b1136e35a22be12af5.zip
ARM: OMAP: omap_device: Fix up resource names when booted with devicetree
When booted with some resource will have their name set to NULL. This can cause later kernel crash since this is not expected by the platform code. When we boot without DT the devices are created with platform_device_add() which itself fixes up the missing resource names: if (r->name == NULL) r->name = dev_name(&pdev->dev); The of core also fixes up the resource names when taking the information from DT data - in __of_address_to_resource(): r->name = name ? name : dev->full_name; When we boot OMAP with devicetree: of will create the devices based on the DT data so the resource names are guarantied to be not NULL. Since we have the 'ti,hwmod' tag, we remove the of created resources from the device and re-create them based on hwmod data. If the hwmod data does not specify a name for a resource it will be NULL. This can cause kernel crash if the driver uses platform_get_resource_byname() to get any resource. Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com> [b-cousson@ti.com: Change omap_hwmod to omap_device in subject] Signed-off-by: Benoit Cousson <b-cousson@ti.com>
Diffstat (limited to 'arch/arm/plat-omap/include/plat/omap_hwmod.h')
0 files changed, 0 insertions, 0 deletions