1. 19 4月, 2013 1 次提交
    • A
      ARM: exynos: enable multiplatform support · bd51de53
      Arnd Bergmann 提交于
      This makes it possible to enable the exynos platform as part of a
      multiplatform kernel, in addition to keeping the single-platform
      exynos support.
      
      The multiplatform variant has a number of limitations at the moment:
      
      * It only supports DT-enabled machines. This is not a problem in
        the long run, as non-DT machines for exynos are going away.
        The main problem here is that the gpio code and the exynos_eint
        irqchip are not multiplatform capable but still required for
        ATAGS based boot.
      * The watchdog driver is still missing a conversion.
      * sparsemem and memory_holes are currently not supported in
        multiplatform.
      
      The the multiplatform aware ARCH_EXYNOS Kconfig symbol is disabled
      for now, as dependent patches are still pending in other
      subsystem trees. We will enable it once everything comes together.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      bd51de53
  2. 04 2月, 2013 1 次提交
  3. 28 11月, 2012 1 次提交
  4. 22 12月, 2011 1 次提交
    • K
      arm: convert sysdev_class to a regular subsystem · 4a858cfc
      Kay Sievers 提交于
      After all sysdev classes are ported to regular driver core entities, the
      sysdev implementation will be entirely removed from the kernel.
      
      Cc: Kukjin Kim <kgene.kim@samsung.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Ben Dooks <ben-linux@fluff.org>
      Cc: Vinod Koul <vinod.koul@intel.com>
      Cc: Boojin Kim <boojin.kim@samsung.com>
      Cc: Linus Walleij <linus.walleij@linaro.org>
      Cc: Lucas De Marchi <lucas.demarchi@profusion.mobi>
      Cc: Heiko Stuebner <heiko@sntech.de>
      Signed-off-by: NKay Sievers <kay.sievers@vrfy.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      4a858cfc
  5. 10 12月, 2011 1 次提交
    • M
      ARM: S3C64XX: Implement basic power domain support · c656c306
      Mark Brown 提交于
      The S3C64xx SoCs contain a set of gateable power domains which can be
      enabled and disabled at runtime in order to save power.  Use the generic
      power domain code to implement support for these in software, enabling
      runtime control of most domains:
      
       - ETM (not supported in mainline).
       - Domain G: 3D acceleration (no mainline support).
       - Domain V: MFC (no mainline support).
       - Domain I: JPEG and camera interface (no mainline support).
       - Domain P: 2D acceleration, TV encoder and scaler (no mainline support)
       - Domain S: Security (no mainline support).
       - Domain F: LCD (driver already uses runtime PM), post processing and
         rotation (no mainline support).
      
      The IROM domain is marked as always enabled as we should arrange for it
      to be enabled when we suspend which will need a bit more work.
      
      Due to all the conditional device registration that the platform does
      wrap s3c_pm_init() with s3c64xx_pm_init() which actually puts the device
      into the power domain after the machines have registered, looking for
      platform data to tell if the device was registered. Since currently only
      Cragganmore actually sets up PM that is the only machine updated.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Acked-by: NKukjin Kim <kgene.kim@samsung.com>
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      c656c306
  6. 21 9月, 2011 1 次提交
    • K
      ARM: SAMSUNG: Update the name of regarding Samsung GPIO · 782d8a3c
      Kukjin Kim 提交于
      According to gpio-samsung.c, this patch updates the name of
      regarding Samsung GPIO. Basically the samsung_xxx prefix is
      used in gpio-samsung.c instead of s3c_xxx, because unified
      name can reduce its complexity.
      
      Note: some s3c_xxx stil remains because it is used widely.
      It will be updated next time.
      
      Cc: Ben Dooks <ben-linux@fluff.org>
      Signed-off-by: NKukjin Kim <kgene.kim@samsung.com>
      782d8a3c
  7. 02 7月, 2011 1 次提交
    • R
      ARM: pm: allow suspend finisher to return error codes · 29cb3cd2
      Russell King 提交于
      There are SoCs where attempting to enter a low power state is ignored,
      and the CPU continues executing instructions with all state preserved.
      It is over-complex at that point to disable the MMU just to call the
      resume path.
      
      Instead, allow the suspend finisher to return error codes to abort
      suspend in this circumstance, where the cpu_suspend internals will then
      unwind the saved state on the stack.  Also omit the tlb flush as no
      changes to the page tables will have happened.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      29cb3cd2
  8. 24 6月, 2011 1 次提交
  9. 25 4月, 2011 1 次提交
  10. 23 2月, 2011 1 次提交
  11. 11 2月, 2011 1 次提交
  12. 30 12月, 2010 1 次提交
  13. 23 2月, 2010 1 次提交
  14. 21 1月, 2010 1 次提交
  15. 07 5月, 2009 2 次提交
  16. 10 3月, 2009 1 次提交
    • B
      [ARM] S3C: Tidy sleep code path to fix call flow · fff94cd9
      Ben Dooks 提交于
      As noted by Russell King, the sleep code path is not
      elegant and makes use of leaving items on the stack
      between calls.
      
      Change the code that does the following:
      
              if (s3c_cpu_save(regs_save) == 0) {
                      flush_cache_all();
                      S3C_PMDBG("preparing to sleep\n");
                      pm_cpu_sleep();
              }
      
      to simply call s3c_cpu_save, and let that do the
      necessary calls to quiesce and sleep the system.
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      fff94cd9
  17. 08 3月, 2009 9 次提交
  18. 08 10月, 2008 1 次提交
  19. 12 2月, 2007 1 次提交
  20. 25 9月, 2006 3 次提交
  21. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4