1. 11 4月, 2013 4 次提交
  2. 08 4月, 2013 2 次提交
  3. 02 4月, 2013 1 次提交
  4. 13 3月, 2013 1 次提交
  5. 05 2月, 2013 1 次提交
  6. 23 1月, 2013 7 次提交
  7. 15 1月, 2013 1 次提交
  8. 11 1月, 2013 1 次提交
  9. 08 1月, 2013 2 次提交
    • M
      ALSA: pxa27x: rename pxa27x_assert_ac97reset() · 053fe0f1
      Mike Dunn 提交于
      This patch does nothing functionally, it just gives the function a new name and
      modifies the prototype slightly in order to clarify what the function is doing
      (which is not necessarily asserting the reset).
      Some commentary also added.
      
      Tested on a palm treo 680 machine.
      Signed-off-by: NMike Dunn <mikedunn@newsguy.com>
      Acked-by: NIgor Grinberg <grinberg@compulab.co.il>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      053fe0f1
    • M
      ALSA: pxa27x: fix ac97 warm reset · 3b4bc7bc
      Mike Dunn 提交于
      This patch fixes some code that implements a work-around to a hardware bug in
      the ac97 controller on the pxa27x.  A bug in the controller's warm reset
      functionality requires that the mfp used by the controller as the AC97_nRESET
      line be temporarily reconfigured as a generic output gpio (AF0) and manually
      held high for the duration of the warm reset cycle.  This is what was done in
      the original code, but it was broken long ago by commit fb1bf8cd
          ([ARM] pxa: introduce processor specific pxa27x_assert_ac97reset())
      which changed the mfp to a GPIO input instead of a high output.
      
      The fix requires the ac97 controller to obtain the gpio via gpio_request_one(),
      with arguments that configure the gpio as an output initially driven high.
      
      Tested on a palm treo 680 machine.  Reportedly, this broken code only prevents a
      warm reset on hardware that lacks a pull-up on the line, which appears to be the
      case for me.
      Signed-off-by: NMike Dunn <mikedunn@newsguy.com>
      Signed-off-by: NIgor Grinberg <grinberg@compulab.co.il>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Cc: stable@vger.kernel.org
      3b4bc7bc
  10. 04 1月, 2013 1 次提交
    • G
      ARM: drivers: remove __dev* attributes. · 351a102d
      Greg Kroah-Hartman 提交于
      CONFIG_HOTPLUG is going away as an option.  As a result, the __dev*
      markings need to be removed.
      
      This change removes the use of __devinit, __devexit_p, __devinitdata,
      and __devexit from these drivers.
      
      Based on patches originally written by Bill Pemberton, but redone by me
      in order to handle some of the coding style issues better, by hand.
      
      Cc: Bill Pemberton <wfp5p@virginia.edu>
      Cc: Russell King <linux@arm.linux.org.uk>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      351a102d
  11. 25 12月, 2012 2 次提交
  12. 23 11月, 2012 1 次提交
  13. 22 11月, 2012 1 次提交
  14. 21 11月, 2012 1 次提交
  15. 16 11月, 2012 1 次提交
  16. 15 11月, 2012 1 次提交
  17. 06 11月, 2012 1 次提交
  18. 28 10月, 2012 2 次提交
    • M
      ARM: pxa/spitz_pm: Fix hang when resuming from STR · 510fcb0d
      Marko Katic 提交于
      Devices that use spitz_pm.c will fail to resume
      from STR (Suspend To Ram) when the charger plug is inserted
      or removed when a device is in STR mode. The culprit is
      a misconfigured gpio line - GPIO18. GPIO18 should be configured as a
      regular GPIO input but it gets configured as an alternate function
      GPIO18_RDY. And then later in postsuspend() it gets configured as
      a regular GPIO18 input line.
      
      Fix this by removing the GPIO18_RDY configuration so that GPIO18
      only gets configured as a regular gpio input.
      Signed-off-by: NMarko Katic <dromede@gmail.com>
      Signed-off-by: NHaojian Zhuang <haojian.zhuang@gmail.com>
      510fcb0d
    • P
      ARM: pxa: hx4700: Fix backlight PWM device number · 8d6b00f5
      Paul Parsons 提交于
      Recent changes to PXA PWM support changed the PXA27X PWM device
      numbering scheme.
      
      The linux-3.5 PXA PWM driver followed the hardware numbering scheme for
      the 4 PWMs, while the linux-3.6-rc1 PXA PWM driver has adopted a linear
      numbering scheme:
      
      Address		Hardware	3.5 pwm_id	3.6-rc1 pwm_id
      0x40b00000	PWM0		0		0
      0x40b00010	PWM2		2		1
      0x40c00000	PWM1		1		2
      0x40c00010	PWM3		3		3
      
      The hx4700 backlight uses PWM1 at 0x40c00000. Consequently the pwm_id
      must be changed from 1 to 2.
      
      This patch fixes the backlight PWM device number and at the same time
      moves from the legacy PWM API (pwm_id) to the new PWM API (pwm_lookup).
      Signed-off-by: NPaul Parsons <lost.distance@yahoo.com>
      Cc: Thierry Reding <thierry.reding@avionic-design.de>
      Signed-off-by: NHaojian Zhuang <haojian.zhuang@gmail.com>
      8d6b00f5
  19. 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
  20. 04 10月, 2012 4 次提交
    • A
      ARM: pxa: work around duplicate definition of GPIO24_SSP1_SFRM · e0347c52
      Arnd Bergmann 提交于
      The symbol "GPIO24_SSP1_SFRM" is defined in both mfp-pxa27x.h and
      mfp-pxa25x.h. Since the macro is not actually used in the cm-x2xx.c
      file, but it includes both headers, a safe workaround should be
      to just undefine it from the .c file. This is a bit hacky and
      the headers should be fixed to not both define it, but for now
      it gets us around an annoying warning.
      
      Without this patch, building cm_x2xx_defconfig results in:
      
      In file included from arch/arm/mach-pxa/include/mach-pxa/pxa27x.h:7:0,
                       from arch/arm/mach-pxa/cm-x2xx.c:25:
      arch/arm/mach-pxa/include/mach-pxa/mfp-pxa27x.h:215:0: warning: "GPIO24_SSP1_SFRM" redefined [enabled by default]
      arch/arm/mach-pxa/include/mach-pxa/mfp-pxa25x.h:111:0: note: this is the location of the previous definition
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NIgor Grinberg <grinberg@compulab.co.il>
      Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
      Cc: Mike Rapoport <mike@compulab.co.il>
      e0347c52
    • A
      ARM: pxa: remove sharpsl_fatal_check function · 066258f4
      Arnd Bergmann 提交于
      The sharpsl_fatal_check has not been used since Pavel Machek removed
      the caller in 99f329a2 "pxa/sharpsl_pm: zaurus c3000 aka spitz: fix
      resume". Nobody has complained since 2009, so it's safe to assume we
      can just remove the function.
      
      Without this patch, building corgi_defconfig results in:
      
      /home/arnd/linux-arm/arch/arm/mach-pxa/sharpsl_pm.c:693:12: warning: 'sharpsl_fatal_check' defined but not used [-Wunused-function]
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Cc: Pavel Machek <pavel@ucw.cz>
      Cc: Stanislav Brabec <utx@penguin.cz>
      Cc: Eric Miao <eric.y.miao@gmail.com>
      Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
      066258f4
    • A
      ARM: pxa: define palmte2_pxa_keys conditionally · 30bda0eb
      Arnd Bergmann 提交于
      Gcc prints a harmless warning about palmte2_pxa_keys not being used
      when the gpio keyboard driver is disabled. The solution is to use
      the same #ifdef that is already present in the place where the
      symbol is used.
      
      Without this patch, building palmz72_defconfig results in:
      
      /home/arnd/linux-arm/arch/arm/mach-pxa/palmte2.c:128:31: warning: 'palmte2_pxa_keys' defined but not used [-Wunused-variable]
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NMarek Vasut <marek.vasut@gmail.com>
      Cc: Carlos Eduardo Medaglia Dyonisio <cadu@nerdfeliz.com>
      Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
      Cc: Eric Miao <eric.y.miao@gmail.com>
      30bda0eb
    • A
      ARM: pxa: Wunused-result warning in viper board file · 5f0cc6d1
      Arnd Bergmann 提交于
      Calling kstrtoul requires checking the result. In case of
      the viper_tpm_setup function, let's fail the __setup function
      if the number was invalid.
      
      Without this patch, building viper_defconfig results in:
      
      arch/arm/mach-pxa/viper.c: In function 'viper_tpm_setup':
      arch/arm/mach-pxa/viper.c:771:10: warning: ignoring return value of 'kstrtoul', declared with attribute warn_unused_result [-Wunused-result]
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NMarc Zyngier <maz@misterjones.org>
      Cc: Haojian Zhuang <haojian.zhuang@marvell.com>
      Cc: Eric Miao <eric.y.miao@gmail.com>
      5f0cc6d1
  21. 24 9月, 2012 1 次提交
  22. 14 9月, 2012 3 次提交