summaryrefslogtreecommitdiff
path: root/drivers/clocksource
diff options
context:
space:
mode:
authorPaul Mundt <lethal@linux-sh.org>2010-03-09 06:57:53 +0000
committerPaul Mundt <lethal@linux-sh.org>2010-03-10 13:08:32 +0900
commita636ee7fb35b731ba2b331f6294e809bb6be09c8 (patch)
treecff3b2505cb6dcee3a8babbb6347dfab13f185cc /drivers/clocksource
parent57d54889cd00db2752994b389ba714138652e60c (diff)
downloadlinux-3.10-a636ee7fb35b731ba2b331f6294e809bb6be09c8.tar.gz
linux-3.10-a636ee7fb35b731ba2b331f6294e809bb6be09c8.tar.bz2
linux-3.10-a636ee7fb35b731ba2b331f6294e809bb6be09c8.zip
driver core: Early dev_name() support.
Presently early platform devices suffer from the fact they are unable to use dev_xxx() calls early on due to dev_name() and others being unavailable at the time ->probe() is called. This implements early init_name construction from the matched name/id pair following the semantics of the late device/driver match. As a result, matched IDs (inclusive of requested ones) are preserved when the handoff from the early platform code happens at kobject initialization time. Since we still require kmalloc slabs to be available at this point, using kstrdup() for establishing the init_name works fine. This subsequently needs to be tested from dev_name() prior to the init_name being cleared by the driver core. We don't kfree() since others will already have a handle on the string long before the kobject initialization takes place. This is also needed to permit drivers to use the clock framework early, without having to manually construct their own device IDs from the match id/name pair locally (needed by the early console and timer code on sh and arm). Signed-off-by: Paul Mundt <lethal@linux-sh.org> Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/clocksource')
0 files changed, 0 insertions, 0 deletions