Skip to content
  1. Nov 12, 2014
    • Daniel Lezcano's avatar
      cpuidle: Invert CPUIDLE_FLAG_TIME_VALID logic · b82b6cca
      Daniel Lezcano authored
      
      
      The only place where the time is invalid is when the ACPI_CSTATE_FFH entry
      method is not set. Otherwise for all the drivers, the time can be correctly
      measured.
      
      Instead of duplicating the CPUIDLE_FLAG_TIME_VALID flag in all the drivers
      for all the states, just invert the logic by replacing it by the flag
      CPUIDLE_FLAG_TIME_INVALID, hence we can set this flag only for the acpi idle
      driver, remove the former flag from all the drivers and invert the logic with
      this flag in the different governor.
      
      Signed-off-by: default avatarDaniel Lezcano <daniel.lezcano@linaro.org>
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      b82b6cca
  2. Oct 02, 2014
  3. Sep 08, 2014
  4. Jul 18, 2014
  5. Jun 17, 2014
    • Arnd Bergmann's avatar
      ARM: samsung: make SAMSUNG_DMADEV optional · 27873b05
      Arnd Bergmann authored
      
      
      The only remaining driver using the samsung dmadev code is the broken
      samsung-ac97 sound driver. However, as found by Russell's autobuilder,
      the elaborate dependency chains around it cause problems with
      circular dependencies.
      
      This is an attempt to simplify those dependencies by making the
      SAMSUNG_DMADEV option user-selectable. I also try to keep the
      default settings for all related options unchanged, so we don't
      introduce any regressions against earlier testing on linux-next.
      
      In particular, all s3c64xx and s5p* platforms keep selecting the
      pl330 and pl08x drivers they require, but the select statement
      is now moved towards the main platform option, and it remains
      optional by unselecting CONFIG_DMADEVICES.
      
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Cc: Kukjin Kim <kgene.kim@samsung.com>
      27873b05
  6. Mar 21, 2014
  7. Mar 20, 2014
  8. Mar 11, 2014
  9. Feb 15, 2014
    • Paul Gortmaker's avatar
      ARM: S3C64XX: mach-crag6410-module.c is not modular · baf64abc
      Paul Gortmaker authored
      
      
      Despite the name mach-crag6410-module.c, the code is built for
      MACH_WLF_CRAGG_6410 -- which is bool, and hence this code is
      either present or absent.  It will never be modular, so using
      module_init as an alias for __initcall can be somewhat
      misleading.
      
      Fix this up now, so that we can relocate module_init from
      init.h into module.h in the future.  If we don't do this, we'd
      have to add module.h to obviously non-modular code, and that
      would be a worse thing.
      
      Note that direct use of __initcall is discouraged, vs. one
      of the priority categorized subgroups.  As __initcall gets
      mapped onto device_initcall, our use of device_initcall
      directly in this change means that the runtime impact is
      zero -- it will remain at level 6 in initcall ordering.
      
      Cc: Ben Dooks <ben-linux@fluff.org>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: patches@opensource.wolfsonmicro.com
      Signed-off-by: default avatarPaul Gortmaker <paul.gortmaker@windriver.com>
      Signed-off-by: default avatarKukjin Kim <kgene.kim@samsung.com>
      baf64abc
  10. Feb 14, 2014
  11. Feb 13, 2014
  12. Jan 14, 2014
  13. Dec 20, 2013
    • Linus Walleij's avatar
      ARM: s3c64xx: get rid of custom <mach/gpio.h> · 41c3548e
      Linus Walleij authored
      
      
      This isolates the custom S3C64xx GPIO definition table to
      <linux/platform_data/gpio-samsung-s3x64xx.h> as this is
      used in a few different places in the kernel, removing the
      need to depend on the implicit inclusion of <mach/gpio.h>
      from <linux/gpio.h> and thus getting rid of a few nasty
      cross-dependencies.
      
      Also delete the CONFIG_SAMSUNG_GPIO_EXTRA stuff. Instead
      roof the number of GPIOs for this platform:
      First sum up all the GPIO banks from A to Q: 187 GPIOs.
      Add the 16 "board GPIOs" and the roof for SAMSUNG_GPIO_EXTRA,
      128, so in total maximum 187+16+128 = 331 GPIOs, so let's
      take the same roof as for S3C24XX: 512. This way we can do
      away with the GPIO calculation macros for GPIO_BOARD_START,
      BOARD_NR_GPIOS and the definition of ARCH_NR_GPIOS.
      
      Cc: Mark Brown <broonie@kernel.org>
      [on Mini6410 board]
      Tested-by: default avatarTomasz Figa <t.figa@samsung.com>
      [for changes in mach-s3c64xx]
      Acked-by: default avatarTomasz Figa <t.figa@samsung.com>
      Tested-by: default avatarMark Brown <broonie@linaro.org>
      Acked-by: default avatarKukjin Kim <kgene.kim@samsung.com>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      41c3548e
    • Uwe Kleine-König's avatar
      ARM: drop <mach/timex.h> for !ARCH_MULTIPLATFORM, too · 79f08d9e
      Uwe Kleine-König authored
      
      
      While <mach/timex.h> isn't used for multi-platform builds since long it
      still is for "normal" builds. As the previous patches fix all sites to
      not make use of this per-platform file, it can go now for good also for
      platforms that are not (yet) converted to multi-platform.
      
      While at it there are no users of CLOCK_TICK_RATE any more, so also drop
      the dummy #define.
      
      Signed-off-by: default avatarUwe Kleine-König <u.kleine-koenig@pengutronix.de>
      79f08d9e
  14. Dec 18, 2013
  15. Dec 14, 2013
    • Tomasz Figa's avatar
      ARM: s3c64xx: dt: Fix boot failure due to double clock initialization · cb120572
      Tomasz Figa authored
      
      
      Commit
      
      4178bac4 ARM: call of_clk_init from default time_init handler
      
      added implicit call to of_clk_init() from default time_init callback,
      but it did not change platforms calling it from other callbacks, despite
      of not having custom time_init callbacks. This caused double clock
      initialization on such platforms, leading to boot failures. An example
      of such platform is mach-s3c64xx.
      
      This patch fixes boot failure on s3c64xx by dropping custom init_irq
      callback, which had a call to of_clk_init() and moving system reset
      initialization to init_machine callback. This allows us to have
      clocks initialized properly without a need to have custom init_time or
      init_irq callbacks.
      
      Signed-off-by: default avatarTomasz Figa <tomasz.figa@gmail.com>
      Signed-off-by: default avatarOlof Johansson <olof@lixom.net>
      cb120572
  16. Dec 11, 2013
  17. Nov 24, 2013
  18. Oct 23, 2013
  19. Oct 16, 2013
  20. Oct 06, 2013
  21. Sep 16, 2013
  22. Aug 29, 2013
  23. Aug 12, 2013
  24. Aug 05, 2013
  25. Jul 09, 2013
  26. Jun 18, 2013
Loading