1. 02 12月, 2015 5 次提交
  2. 13 10月, 2015 4 次提交
  3. 27 9月, 2015 1 次提交
  4. 16 9月, 2015 1 次提交
    • T
      genirq: Remove irq argument from irq flow handlers · bd0b9ac4
      Thomas Gleixner 提交于
      Most interrupt flow handlers do not use the irq argument. Those few
      which use it can retrieve the irq number from the irq descriptor.
      
      Remove the argument.
      
      Search and replace was done with coccinelle and some extra helper
      scripts around it. Thanks to Julia for her help!
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Cc: Julia Lawall <Julia.Lawall@lip6.fr>
      Cc: Jiang Liu <jiang.liu@linux.intel.com>
      bd0b9ac4
  5. 30 7月, 2015 7 次提交
  6. 28 7月, 2015 2 次提交
    • R
      ARM: kill off set_irq_flags usage · e8d36d5d
      Rob Herring 提交于
      set_irq_flags is ARM specific with custom flags which have genirq
      equivalents. Convert drivers to use the genirq interfaces directly, so we
      can kill off set_irq_flags. The translation of flags is as follows:
      
      IRQF_VALID -> !IRQ_NOREQUEST
      IRQF_PROBE -> !IRQ_NOPROBE
      IRQF_NOAUTOEN -> IRQ_NOAUTOEN
      
      For IRQs managed by an irqdomain, the irqdomain core code handles clearing
      and setting IRQ_NOREQUEST already, so there is no need to do this in
      .map() functions and we can simply remove the set_irq_flags calls. Some
      users also modify IRQ_NOPROBE and this has been maintained although it
      is not clear that is really needed. There appears to be a great deal of
      blind copy and paste of this code.
      Signed-off-by: NRob Herring <robh@kernel.org>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Sekhar Nori <nsekhar@ti.com>
      Cc: Kevin Hilman <khilman@deeprootsystems.com>
      Cc: Jason Cooper <jason@lakedaemon.net>
      Cc: Andrew Lunn <andrew@lunn.ch>
      Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
      Cc: Gregory Clement <gregory.clement@free-electrons.com>
      Acked-by: NHans Ulli Kroll <ulli.kroll@googlemail.com>
      Acked-by: NShawn Guo <shawnguo@kernel.org>
      Cc: Sascha Hauer <kernel@pengutronix.de>
      Cc: Imre Kaloz <kaloz@openwrt.org>
      Acked-by: NKrzysztof Halasa <khalasa@piap.pl>
      Cc: Greg Ungerer <gerg@uclinux.org>
      Cc: Roland Stigge <stigge@antcom.de>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Daniel Mack <daniel@zonque.org>
      Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
      Cc: Robert Jarzmik <robert.jarzmik@free.fr>
      Cc: Simtec Linux Team <linux@simtec.co.uk>
      Cc: Kukjin Kim <kgene@kernel.org>
      Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>
      Acked-by: NWan ZongShun <mcuos.com@gmail.com>
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: linux-omap@vger.kernel.org
      Cc: linux-samsung-soc@vger.kernel.org
      Tested-by: NKevin Hilman <khilman@linaro.org>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      e8d36d5d
    • N
      ARM: appropriate __init annotation for const data · 19c233b7
      Nicolas Pitre 提交于
      Init data marked const should be annotated with __initconst for
      correctness and not __initdata.  In some cases the array gathering
      references to that data has to be marked const as well. This fixes
      LTO builds that otherwise fail with section mismatch errors.
      Signed-off-by: NNicolas Pitre <nico@linaro.org>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      19c233b7
  7. 21 7月, 2015 1 次提交
  8. 27 3月, 2015 1 次提交
  9. 24 3月, 2015 1 次提交
  10. 27 2月, 2015 3 次提交
    • A
      ARM: S3C64XX: fix __initdata section mismatch · 19c69daf
      Arnd Bergmann 提交于
      smdk6410_b_pwr_5v_data is marked as __initdata, but referenced
      from a structure that is not:
      
      WARNING: arch/arm/mach-s3c64xx/built-in.o(.data+0x4c5c): Section mismatch in reference from the variable smdk6410_b_pwr_5v_data to the (unknown reference) .init.data:(unknown)
      
      This removes the annotation to avoid an invalid pointer access
      when the regulator driver accesses this variable.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NKukjin Kim <kgene@kernel.org>
      19c69daf
    • A
      ARM: S3C64XX: fix building without CONFIG_PM_SLEEP · 484c213b
      Arnd Bergmann 提交于
      arch/arm/mach-s3c64xx/built-in.o: In function `s3c_pm_restore_core':
      :(.text+0x5d0): undefined reference to `s3c_pm_do_restore_core'
      :(.text+0x5d4): undefined reference to `s3c_pm_do_restore'
      arch/arm/mach-s3c64xx/built-in.o: In function `s3c_pm_save_core':
      :(.text+0x60c): undefined reference to `s3c_pm_do_save'
      arch/arm/mach-s3c64xx/built-in.o: In function `s3c64xx_irq_pm_resume':
      :(.text+0x670): undefined reference to `s3c_pm_do_restore'
      arch/arm/mach-s3c64xx/built-in.o: In function `s3c64xx_irq_pm_suspend':
      :(.text+0x6d8): undefined reference to `s3c_pm_do_save'
      arch/arm/mach-s3c64xx/built-in.o: In function `s3c_cpu_resume':
      :(.text+0x71c): undefined reference to `cpu_resume'
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NKukjin Kim <kgene@kernel.org>
      484c213b
    • A
      ARM: S3C64XX: add I2C dependencies where needed · 261592e6
      Arnd Bergmann 提交于
      The SMDK6410_WM1190_EV1 and SMDK6410_WM1192_EV1 add-on
      cards select MFD_WM*_I2C, but they ignore the fact that I2C
      may be compiled as a loadable module.
      
      This patch adds a dependency on I2C, which means we avoid
      the build errors, but can end up in a case where the options
      are hidden from the user when I2C is turned off.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Cc: Kukjin Kim <kgene.kim@samsung.com>
      Cc: Tomasz Figa <tomasz.figa@gmail.com>
      Cc: Ben Dooks <ben-linux@fluff.org>
      Signed-off-by: NKukjin Kim <kgene@kernel.org>
      261592e6
  11. 24 1月, 2015 1 次提交
  12. 13 11月, 2014 1 次提交
    • D
      cpuidle: Invert CPUIDLE_FLAG_TIME_VALID logic · b82b6cca
      Daniel Lezcano 提交于
      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: NDaniel Lezcano <daniel.lezcano@linaro.org>
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      b82b6cca
  13. 02 10月, 2014 1 次提交
  14. 09 9月, 2014 1 次提交
  15. 19 7月, 2014 1 次提交
  16. 17 6月, 2014 1 次提交
    • A
      ARM: samsung: make SAMSUNG_DMADEV optional · 27873b05
      Arnd Bergmann 提交于
      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: NArnd Bergmann <arnd@arndb.de>
      Cc: Kukjin Kim <kgene.kim@samsung.com>
      27873b05
  17. 22 3月, 2014 2 次提交
  18. 21 3月, 2014 2 次提交
  19. 11 3月, 2014 1 次提交
  20. 16 2月, 2014 1 次提交
    • P
      ARM: S3C64XX: mach-crag6410-module.c is not modular · baf64abc
      Paul Gortmaker 提交于
      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: NPaul Gortmaker <paul.gortmaker@windriver.com>
      Signed-off-by: NKukjin Kim <kgene.kim@samsung.com>
      baf64abc
  21. 14 2月, 2014 2 次提交