1. 29 Mar, 2010 6 commits
  2. 10 Mar, 2010 5 commits
    • Paul Mundt's avatar
      serial: sh-sci: clkdev updates for MSTP gating. · c7ed1ab3
      Paul Mundt authored
      This fixes up some of the I/D/F clock ambiguity in the sh-sci driver.
      The interface clock in most cases just wraps back to the peripheral
      clock, while the function clock wraps in to the MSTP bits. As the logic
      was somewhat inverted, this cleans that up, and also enables all CPUs
      with SCI MSTP bits to match function clocks through clkdev lookup.
      
      As a result, this gets rid of the clk string abuse on the sh side, and
      the clock string will be killed off once the ARM code has had a chance to
      sync up. This also enables MSTP gating on CPUs like 7786 which had never
      wired it up before. Impacted CPUs are primarily all SH-Mobiles, SH7785,
      and SH7786.
      Signed-off-by: default avatarPaul Mundt <lethal@linux-sh.org>
      c7ed1ab3
    • Paul Mundt's avatar
      Merge branch 'sh/driver-core' into sh/clkfwk · d28c145d
      Paul Mundt authored
      d28c145d
    • 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
  3. 09 Mar, 2010 2 commits
  4. 08 Mar, 2010 27 commits