1. 15 10月, 2015 7 次提交
  2. 07 10月, 2015 3 次提交
  3. 06 10月, 2015 2 次提交
  4. 27 9月, 2015 2 次提交
  5. 21 9月, 2015 1 次提交
  6. 06 9月, 2015 2 次提交
    • R
      ARM: pxa: add memory resource to SA1100 RTC device · 2c4fabec
      Rob Herring 提交于
      The drivers for the SA1100 and PXA RTCs are now mutually exclusive, so
      add the memory resource for the sa1100-rtc device. Since the memory
      resource is already present in the pxa_rtc_resources, that makes
      sa1100_rtc_resources and pxa_rtc_resources equivalent, so use
      pxa_rtc_resources for both devices and remove the duplicate
      sa1100_rtc_resources.
      Signed-off-by: NRob Herring <robh@kernel.org>
      Cc: Daniel Mack <daniel@zonque.org>
      Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
      Acked-by: NRobert Jarzmik <robert.jarzmik@free.fr>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: linux-arm-kernel@lists.infradead.org
      Signed-off-by: NAlexandre Belloni <alexandre.belloni@free-electrons.com>
      2c4fabec
    • R
      rtc: pxa: convert to use shared sa1100 functions · 3cdf4ad9
      Rob Herring 提交于
      Currently, the rtc-sa1100 and rtc-pxa drivers co-exist as rtc-pxa has a
      superset of functionality. Having 2 drivers sharing the same memory
      resource is not allowed by the driver model if resources are properly
      declared. This problem was avoided by not adding memory resources to the
      SA1100 RTC driver, but that prevents clean-up of the SA1100 driver.
      
      This commit converts the PXA RTC to use the exported SA1100 RTC
      functions. Now the sa1100-rtc and pxa-rtc devices are mutually
      exclusive, so we must remove the sa1100-rtc from pxa27x and pxa3xx.
      Signed-off-by: NRob Herring <robh@kernel.org>
      Cc: Daniel Mack <daniel@zonque.org>
      Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
      Cc: Robert Jarzmik <robert.jarzmik@free.fr>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Alessandro Zummo <a.zummo@towertech.it>
      Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com>
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: rtc-linux@googlegroups.com
      Signed-off-by: NAlexandre Belloni <alexandre.belloni@free-electrons.com>
      3cdf4ad9
  7. 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
  8. 18 7月, 2015 3 次提交
    • V
      ARM: pxa: Use setup_timer · 6d6db340
      Vaishali Thakkar 提交于
      Use the timer API function setup_timer instead of structure field
      assignments to initialize a timer.
      
      A simplified version of the Coccinelle semantic patch that performs
      this transformation is as follows:
      
      @change@
      expression e1, e2, a;
      @@
      
      -init_timer(&e1);
      +setup_timer(&e1, a, 0UL);
      ... when != a = e2
      -e1.function = a;
      Signed-off-by: NVaishali Thakkar <vthakkar1994@gmail.com>
      Signed-off-by: NRobert Jarzmik <robert.jarzmik@free.fr>
      6d6db340
    • V
      ARM: pxa: Use module_platform_driver · 9754c8ef
      Vaishali Thakkar 提交于
      Use module_platform_driver for drivers whose init and exit functions
      only register and unregister, respectively.
      
      A simplified version of the Coccinelle semantic patch that performs
      this transformation is as follows:
      
      @a@
      identifier f, x;
      @@
      -static f(...) { return platform_driver_register(&x); }
      
      @b depends on a@
      identifier e, a.x;
      @@
      -static e(...) { platform_driver_unregister(&x); }
      
      @c depends on a && b@
      identifier a.f;
      declarer name module_init;
      @@
      -module_init(f);
      
      @d depends on a && b && c@
      identifier b.e, a.x;
      declarer name module_exit;
      declarer name module_platform_driver;
      @@
      -module_exit(e);
      +module_platform_driver(x);
      Signed-off-by: NVaishali Thakkar <vthakkar1994@gmail.com>
      Signed-off-by: NRobert Jarzmik <robert.jarzmik@free.fr>
      9754c8ef
    • R
      ARM: pxa: transition to dmaengine phase 1 · 4be0856f
      Robert Jarzmik 提交于
      In order to slowly transition pxa to dmaengine, the legacy code will now
      rely on dmaengine to request a channel.
      
      This implies that PXA architecture selects DMADEVICES and PXA_DMA,
      which is not pretty. Yet it enables PXA drivers to be ported one by one,
      with part of them using dmaengine, and the other part using the legacy
      code.
      Signed-off-by: NRobert Jarzmik <robert.jarzmik@free.fr>
      4be0856f
  9. 17 7月, 2015 1 次提交
  10. 13 7月, 2015 2 次提交
    • T
      ARM/pxa: Prepare balloon3_irq_handler for irq argument removal · 9ec97561
      Thomas Gleixner 提交于
      The irq argument of most interrupt flow handlers is unused or merily
      used instead of a local variable. The handlers which need the irq
      argument can retrieve the irq number from the irq descriptor.
      
      While at it fix the pointless lookup of irq_data with the proper
      methods to retrieve the same information from the irq descriptor.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Cc: Jiang Liu <jiang.liu@linux.intel.com>
      Cc: Russell King <linux+kernel@arm.linux.org.uk>
      Cc: linux-arm-kernel@lists.infradead.org
      9ec97561
    • T
      ARM/pxa: Prepare *_irq_handler for irq argument removal · 6947d04a
      Thomas Gleixner 提交于
      The irq argument of most interrupt flow handlers is unused or merily
      used instead of a local variable. The handlers which need the irq
      argument can retrieve the irq number from the irq descriptor.
      
      Search and update was done with coccinelle and the invaluable help of
      Julia Lawall.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Cc: Julia Lawall <Julia.Lawall@lip6.fr>
      Cc: Jiang Liu <jiang.liu@linux.intel.com>
      Cc: Russell King <linux+kernel@arm.linux.org.uk>
      Cc: linux-arm-kernel@lists.infradead.org
      6947d04a
  11. 22 5月, 2015 1 次提交
  12. 14 5月, 2015 1 次提交
  13. 13 5月, 2015 7 次提交
  14. 06 5月, 2015 1 次提交
  15. 01 5月, 2015 3 次提交
    • R
      ARM: pxa: lubbock: use new pxa_cplds driver · fc9e38c0
      Robert Jarzmik 提交于
      As the interrupt handling was transferred to the pxa_cplds driver,
      make the switch in lubbock platform code.
      
      Fixes: 157d2644 ("ARM: pxa: change gpio to platform device")
      Signed-off-by: NRobert Jarzmik <robert.jarzmik@free.fr>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      fc9e38c0
    • R
      ARM: pxa: mainstone: use new pxa_cplds driver · 27768863
      Robert Jarzmik 提交于
      As the interrupt handling was transferred to the pxa_cplds driver,
      make the switch in mainstone platform code.
      
      Fixes: 157d2644 ("ARM: pxa: change gpio to platform device")
      Signed-off-by: NRobert Jarzmik <robert.jarzmik@free.fr>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      27768863
    • R
      ARM: pxa: pxa_cplds: add lubbock and mainstone IO · aa8d6b73
      Robert Jarzmik 提交于
      Historically, this support was in arch/arm/mach-pxa/lubbock.c and
      arch/arm/mach-pxa/mainstone.c. When gpio-pxa was moved to drivers/pxa,
      it became a driver, and its initialization and probing happened at
      postcore initcall. The lubbock code used to install the chained lubbock
      interrupt handler at init_irq() time.
      
      The consequence of the gpio-pxa change is that the installed chained irq
      handler lubbock_irq_handler() was overwritten in pxa_gpio_probe(_dt)(),
      removing :
       - the handler
       - the falling edge detection setting of GPIO0, which revealed the
         interrupt request from the lubbock IO board.
      
      As a fix, move the gpio0 chained handler setup to a place where we have
      the guarantee that pxa_gpio_probe() was called before, so that lubbock
      handler becomes the true IRQ chained handler of GPIO0, demuxing the
      lubbock IO board interrupts.
      
      This patch moves all that handling to a mfd driver. It's only purpose
      for the time being is the interrupt handling, but in the future it
      should encompass all the motherboard CPLDs handling :
       - leds
       - switches
       - hexleds
      
      The same logic applies to mainstone board.
      
      Fixes: 157d2644 ("ARM: pxa: change gpio to platform device")
      Signed-off-by: NRobert Jarzmik <robert.jarzmik@free.fr>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      aa8d6b73
  16. 14 3月, 2015 1 次提交
  17. 05 3月, 2015 1 次提交
    • A
      ARM: fix typos in smc91x platform data · 04b91701
      Arnd Bergmann 提交于
      I recently did a rework of the smc91x driver and did some build-testing
      by compiling hundreds of randconfig kernels. Unfortunately, my script
      was wrong and did not actually test the configurations that mattered,
      so I introduced stupid typos in almost every file I touched.
      
      I fixed my script now, built all configurations that actually matter
      and fixed all the typos, this is the result.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Fixes: b70661c7 ("net: smc91x: use run-time configuration on all ARM machines")
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      04b91701