Skip to content

L
linux
Switch branch/tag
  1. 13 May, 2010 1 commit
    • Paul Mundt's avatar
      driver core: Early dev_name() depends on slab_is_available(). · 06fe53be
      Paul Mundt authored 
      The early dev_name() setup needs to do an allocation which can only be
satisfied under slab_is_available() conditions. Some of the early
platform drivers may be initialized before this point, and those still
need to contend themselves with an empty dev_name.

This fixes up a regression with the SH earlyprintk which was bailing out
prior to hitting the early probe path due to not being able to satisfy
the early allocation. Other early platform drivers (such as the early
timers) that need to match the dev name are sufficiently late that
allocations are already possible.
Signed-off-by: default avatarPaul Mundt <lethal@linux-sh.org>
      06fe53be
  3. 29 Mar, 2010 1 commit
  5. 10 Mar, 2010 3 commits
    • Paul Mundt's avatar
      sh: Kill off all timer name clobbering. · ec0ffe2e
      Paul Mundt authored 
      Now that dev_name() can be used early, we no longer require a static
string. Kill off all of the superfluous timer names.
Signed-off-by: default avatarPaul Mundt <lethal@linux-sh.org>
      ec0ffe2e
    • Paul Mundt's avatar
      clocksource: Use dev_name() universally across the SH drivers. · 214a607a
      Paul Mundt authored 
      There is no need to copy in the name from the sh timer config now that
dev_name() is available early. We prefer the dev_name() variant for
consistent naming.
Signed-off-by: default avatarPaul Mundt <lethal@linux-sh.org>
      214a607a
    • Paul Mundt's avatar
      driver core: Early dev_name() support. · a636ee7f
      Paul Mundt authored 
      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: default avatarPaul Mundt <lethal@linux-sh.org>
Acked-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      a636ee7f
  7. 08 Mar, 2010 35 commits
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7