An error occurred fetching the project authors.
  1. 16 May, 2011 1 commit
  2. 28 Apr, 2011 2 commits
  3. 23 Apr, 2011 4 commits
  4. 12 Apr, 2011 1 commit
  5. 11 Apr, 2011 1 commit
    • Rafael J. Wysocki's avatar
      PM / Hibernate: Introduce CONFIG_HIBERNATE_CALLBACKS · 1f112cee
      Rafael J. Wysocki authored
      Xen save/restore is going to use hibernate device callbacks for
      quiescing devices and putting them back to normal operations and it
      would need to select CONFIG_HIBERNATION for this purpose.  However,
      that also would cause the hibernate interfaces for user space to be
      enabled, which might confuse user space, because the Xen kernels
      don't support hibernation.  Moreover, it would be wasteful, as it
      would make the Xen kernels include a substantial amount of code that
      they would never use.
      
      To address this issue introduce new power management Kconfig option
      CONFIG_HIBERNATE_CALLBACKS, such that it will only select the code
      that is necessary for the hibernate device callbacks to work and make
      CONFIG_HIBERNATION select it.  Then, Xen save/restore will be able to
      select CONFIG_HIBERNATE_CALLBACKS without dragging the entire
      hibernate code along with it.
      Signed-off-by: default avatarRafael J. Wysocki <rjw@sisk.pl>
      Tested-by: default avatarShriram Rajagopalan <rshriram@cs.ubc.ca>
      1f112cee
  6. 22 Oct, 2010 4 commits
  7. 21 Oct, 2010 1 commit
    • Grant Likely's avatar
      of/device: Rework to use common platform_device_alloc() for allocating devices · 7096d042
      Grant Likely authored
      The current code allocates and manages platform_devices created from
      the device tree manually.  It also uses an unsafe shortcut for
      allocating the platform_device and the resource table at the same
      time. (which I added in the last rework; sorry).
      
      This patch refactors the code to use platform_device_alloc() for
      allocating new devices.  This reduces the amount of custom code
      implemented by of_platform, eliminates the unsafe alloc trick, and has
      the side benefit of letting the platform_bus code manage freeing the
      device data and resources when the device is freed.
      Signed-off-by: default avatarGrant Likely <grant.likely@secretlab.ca>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Greg Kroah-Hartman <gregkh@suse.de>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Michal Simek <monstr@monstr.eu>
      7096d042
  8. 05 Aug, 2010 3 commits
  9. 24 Jul, 2010 2 commits
    • Grant Likely's avatar
      of: Merge of_platform_bus_type with platform_bus_type · eca39301
      Grant Likely authored
      of_platform_bus was being used in the same manner as the platform_bus.
      The only difference being that of_platform_bus devices are generated
      from data in the device tree, and platform_bus devices are usually
      statically allocated in platform code.  Having them separate causes
      the problem of device drivers having to be registered twice if it
      was possible for the same device to appear on either bus.
      
      This patch removes of_platform_bus_type and registers all of_platform
      bus devices and drivers on the platform bus instead.  A previous patch
      made the of_device structure an alias for the platform_device structure,
      and a shim is used to adapt of_platform_drivers to the platform bus.
      
      After all of of_platform_bus drivers are converted to be normal platform
      drivers, the shim code can be removed.
      Signed-off-by: default avatarGrant Likely <grant.likely@secretlab.ca>
      Acked-by: default avatarDavid S. Miller <davem@davemloft.net>
      eca39301
    • Grant Likely's avatar
      drivercore/of: Add OF style matching to platform bus · 05212157
      Grant Likely authored
      As part of the merge between platform bus and of_platform bus, add the
      ability to do of-style matching to the platform bus.
      Signed-off-by: default avatarGrant Likely <grant.likely@secretlab.ca>
      Acked-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      CC: Michal Simek <monstr@monstr.eu>
      CC: Grant Likely <grant.likely@secretlab.ca>
      CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      CC: Stephen Rothwell <sfr@canb.auug.org.au>
      CC: linux-kernel@vger.kernel.org
      CC: microblaze-uclinux@itee.uq.edu.au
      CC: linuxppc-dev@ozlabs.org
      CC: devicetree-discuss@lists.ozlabs.org
      05212157
  10. 21 May, 2010 1 commit
  11. 17 May, 2010 1 commit
  12. 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
  13. 10 May, 2010 1 commit
  14. 29 Mar, 2010 1 commit
  15. 19 Mar, 2010 2 commits
  16. 10 Mar, 2010 1 commit
    • 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
  17. 08 Mar, 2010 3 commits
  18. 23 Dec, 2009 1 commit
  19. 11 Dec, 2009 1 commit
    • Magnus Damm's avatar
      Driver Core: Early platform driver buffer · c60e0504
      Magnus Damm authored
      Add early_platform_init_buffer() support and update the
      early platform driver code to allow passing parameters
      to the driver on the kernel command line.
      
      early_platform_init_buffer() simply allows early platform
      drivers to provide a pointer and length to a memory area
      where the remaining part of the kernel command line option
      will be stored.
      
      Needed to pass baud rate and other serial port options
      to the reworked early serial console code on SuperH.
      Signed-off-by: default avatarMagnus Damm <damm@opensource.se>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      c60e0504
  20. 30 Oct, 2009 1 commit
  21. 15 Sep, 2009 1 commit
  22. 22 Aug, 2009 1 commit
  23. 10 Aug, 2009 1 commit
    • Magnus Damm's avatar
      PM / Driver Core: Kill dev_pm_ops platform warning for now · 651b1f12
      Magnus Damm authored
      Commit 783ea7d4
      (Driver Core: Rework platform suspend/resume, print warning)
      added a warning message printed for platform drivers that use the
      legacy PM callbacks rather than struct dev_pm_ops.  Unfortunately,
      this resulted in some confusion and made some people try to convert
      drivers by replacing the old callbacks with struct dev_pm_ops in
      automatic way, which generally is not a good idea.
      
      Remove the platform device runtime dev_pm_ops warning for now,
      because it's annoying to users and it's not really necessary right
      now.
      
      [rjw: Modified the changelog to be more informative.]
      Signed-off-by: default avatarMagnus Damm <damm@igel.co.jp>
      Acked-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      Signed-off-by: default avatarRafael J. Wysocki <rjw@sisk.pl>
      651b1f12
  24. 25 Jul, 2009 1 commit
  25. 23 Jul, 2009 1 commit
  26. 21 Jul, 2009 1 commit
  27. 16 Jun, 2009 1 commit