1. 28 7月, 2017 1 次提交
    • A
      ARM: pxa: select both FB and FB_W100 for eseries · 1d20d8a9
      Arnd Bergmann 提交于
      We get a link error trying to access the w100fb_gpio_read/write
      functions from the platform when the driver is a loadable module
      or not built-in, so the platform already uses 'select' to hard-enable
      the driver.
      
      However, that fails if the framebuffer subsystem is disabled
      altogether.
      
      I've considered various ways to fix this properly, but they
      all seem like too much work or too risky, so this simply
      adds another 'select' to force the subsystem on as well.
      
      Fixes: 82427de2 ("ARM: pxa: PXA_ESERIES depends on FB_W100.")
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      1d20d8a9
  2. 09 8月, 2016 1 次提交
  3. 30 4月, 2016 1 次提交
    • R
      ARM: pxa: activate pinctrl for device-tree machines · f806dac5
      Robert Jarzmik 提交于
      Pincontrol is not yet ready for all PXA platforms.
      For example, a legacy platform, if PINCTRL was activated, will fail its
      calls to gpio_request() or gpio_direction_output(), as the pinctrl
      driver might not be available, such as for pxa25x and pxa3xx.
      
      As a step forward, activate pincontrol for all device-tree available
      machines, ie. pxa27x device-tree based and pxa3xx device-tree based.
      
      If it appears later that pincontrol is also required for legacy
      platforms and if the mfp->pinctrl conversion can be achieved, then
      PINCTRL will be activated for the whole PXA architecture.
      
      Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
      Signed-off-by: NRobert Jarzmik <robert.jarzmik@free.fr>
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      f806dac5
  4. 02 2月, 2016 2 次提交
  5. 01 5月, 2015 1 次提交
    • 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
  6. 27 12月, 2014 2 次提交
  7. 20 11月, 2014 1 次提交
  8. 22 3月, 2014 4 次提交
    • A
      ARM: pxa: trizeps4 and trizeps4wl use the same file · edd4c720
      Arnd Bergmann 提交于
      The trizeps4 and trizeps4wl platforms are both implemented
      using the same board file. Since the trizeps4wl code is a
      superset of trizeps4, it makes no sense to enable just the
      latter, but with the current Kconfig logic, it causes the
      board file not to be built at all.
      
      Selecting MACH_TRIZEPS4 from MACH_TRIZEPS4WL ensures that
      we are actually building the board file.
      
      Found during randconfig testing.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Cc: Eric Miao <eric.y.miao@gmail.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
      Cc: Daniel Mack <zonque@gmail.com>
      edd4c720
    • A
      ARM: pxa: select I2C_GPIO only if I2C is on · c7dc7d49
      Arnd Bergmann 提交于
      The Arcom/Eurotech VIPER SBC enables the I2C_GPIO driver, but
      that has a dependency on I2C, and causes build failures if I2C
      is disabled. To keep existing configurations running while fixing
      the randconfig problems, this changes the logic to only enable
      I2C_GPIO if I2C is already enabled.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NHaojian Zhuang <haojian.zhuang@gmail.com>
      Cc: Eric Miao <eric.y.miao@gmail.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Daniel Mack <zonque@gmail.com>
      c7dc7d49
    • A
      ARM: pxa: enable pxafb unconditionally for some boards · e914f19f
      Arnd Bergmann 提交于
      The SAAR and TAVOREVB machines try to call functions from
      the PXAFB frame buffer driver from their platform code,
      which only works if that driver is built-in.
      
      This patch ensures that both the generic frame buffer
      code and the specific pxafb driver are always enabled
      when we build a kernel for one of the two boards.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Cc: Eric Miao <eric.y.miao@gmail.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
      Cc: Daniel Mack <zonque@gmail.com>
      e914f19f
    • A
      ARM: pxa: don't "select" SMC91X on MACH_XCEP · a0ad0fdb
      Arnd Bergmann 提交于
      We normally don't hard-enable Kconfig options just because
      a board contains a specific piece of hardware. In this case,
      selecting SMC91X causes a build error, if we don't also enable
      basic network device driver support.
      
      Since the platform has no direct dependency on this driver
      at link time, we can just remove the 'select' statement.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Cc: Eric Miao <eric.y.miao@gmail.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
      Cc: Daniel Mack <zonque@gmail.com>
      a0ad0fdb
  9. 10 2月, 2014 1 次提交
    • S
      pwm: Remove obsolete HAVE_PWM Kconfig symbol · 557fe99d
      Sascha Hauer 提交于
      Before we had the PWM framework we used to have a barebone PWM api. The
      HAVE_PWM Kconfig symbol used to be selected by the PWM drivers to specify
      the PWM API is present in the kernel. Since the last legacy driver is gone
      the HAVE_PWM symbol can go aswell.
      Signed-off-by: NSascha Hauer <s.hauer@pengutronix.de>
      Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
      Cc: Eric Miao <eric.y.miao@gmail.com>
      Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: linux-kernel@vger.kernel.org
      Cc: Thierry Reding <thierry.reding@gmail.com>
      Cc: linux-pwm@vger.kernel.orig
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Signed-off-by: NThierry Reding <thierry.reding@gmail.com>
      557fe99d
  10. 16 10月, 2013 1 次提交
  11. 18 6月, 2013 1 次提交
  12. 11 4月, 2013 1 次提交
  13. 05 4月, 2013 1 次提交
  14. 15 11月, 2012 1 次提交
  15. 14 10月, 2012 1 次提交
    • R
      ARM: config: sort select statements alphanumerically · b1b3f49c
      Russell King 提交于
      As suggested by Andrew Morton:
      
        This is a pet peeve of mine.  Any time there's a long list of items
        (header file inclusions, kconfig entries, array initalisers, etc) and
        someone wants to add a new item, they *always* go and stick it at the
        end of the list.
      
        Guys, don't do this.  Either put the new item into a randomly-chosen
        position or, probably better, alphanumerically sort the list.
      
      lets sort all our select statements alphanumerically.  This commit was
      created by the following perl:
      
      while (<>) {
      	while (/\\\s*$/) {
      		$_ .= <>;
      	}
      	undef %selects if /^\s*config\s+/;
      	if (/^\s+select\s+(\w+).*/) {
      		if (defined($selects{$1})) {
      			if ($selects{$1} eq $_) {
      				print STDERR "Warning: removing duplicated $1 entry\n";
      			} else {
      				print STDERR "Error: $1 differently selected\n".
      					"\tOld: $selects{$1}\n".
      					"\tNew: $_\n";
      				exit 1;
      			}
      		}
      		$selects{$1} = $_;
      		next;
      	}
      	if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
      			  /^endif/ or /^endchoice/)) {
      		foreach $k (sort (keys %selects)) {
      			print "$selects{$k}";
      		}
      		undef %selects;
      	}
      	print;
      }
      if (%selects) {
      	foreach $k (sort (keys %selects)) {
      		print "$selects{$k}";
      	}
      }
      
      It found two duplicates:
      
      Warning: removing duplicated S5P_SETUP_MIPIPHY entry
      Warning: removing duplicated HARDIRQS_SW_RESEND entry
      
      and they are identical duplicates, hence the shrinkage in the diffstat
      of two lines.
      
      We have four testers reporting success of this change (Tony, Stephen,
      Linus and Sekhar.)
      Acked-by: NJason Cooper <jason@lakedaemon.net>
      Acked-by: NTony Lindgren <tony@atomide.com>
      Acked-by: NStephen Warren <swarren@nvidia.com>
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      Acked-by: NSekhar Nori <nsekhar@ti.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      b1b3f49c
  16. 16 8月, 2012 1 次提交
  17. 06 4月, 2012 1 次提交
    • R
      ARM: fix __io macro for PCMCIA · 1ac02d79
      Rob Herring 提交于
      With commit c334bc15 (ARM: make mach/io.h include optional), PCMCIA was
      broken. PCMCIA depends on __io() returning a valid i/o address, and most
      ARM platforms require IO_SPACE_LIMIT be set to 0xffffffff for PCMCIA. This
      needs a better fix with a fixed i/o address mapping, but for now we just
      restore things to the previous behavior.
      
      This fixes at91, omap1, pxa and sa11xx. pxa needs io.h if PCI is enabled,
      but PCMCIA is not. sa11xx already has IO_SPACE_LIMIT set to 0xffffffff,
      so it doesn't need an io.h.
      Signed-off-by: NRob Herring <rob.herring@calxeda.com>
      Cc: Joachim Eastwood <joachim.eastwood@jotron.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Andrew Victor <linux@maxim.org.za>
      Cc: Nicolas Ferre <nicolas.ferre@atmel.com>
      Cc: Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
      Tested-by: Paul Parsons <lost.distance@yahoo.com> (pxa270)
      Acked-by: NTony Lindgren <tony@atomide.com>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      1ac02d79
  18. 26 3月, 2012 1 次提交
  19. 08 10月, 2011 4 次提交
  20. 25 5月, 2011 1 次提交
  21. 03 1月, 2011 1 次提交
  22. 20 12月, 2010 2 次提交
  23. 18 12月, 2010 2 次提交
  24. 16 12月, 2010 1 次提交
  25. 05 12月, 2010 1 次提交
  26. 09 10月, 2010 1 次提交
  27. 08 10月, 2010 2 次提交
  28. 05 8月, 2010 2 次提交