1. 10 12月, 2013 1 次提交
    • R
      gpio: twl4030: Fix regression for twl gpio LED output · f5837ec1
      Roger Quadros 提交于
      Commit 0b2aa8be introduced a regression that causes failure
      in setting LED GPO direction to OUT.
      
      This causes USB host probe failures for Beagleboard C4.
      
      platform usb_phy_gen_xceiv.2: Driver usb_phy_gen_xceiv requests probe deferral
      hsusb2_vcc: Failed to request enable GPIO510: -22
      reg-fixed-voltage reg-fixed-voltage.0.auto: Failed to register regulator: -22
      reg-fixed-voltage: probe of reg-fixed-voltage.0.auto failed with error -22
      
      direction_out/direction_in must return 0 if the operation succeeded.
      
      Also, don't update direction flag and output data if twl4030_set_gpio_direction()
      failed inside twl_direction_out();
      
      Cc: stable@vger.kernel.org
      Signed-off-by: NRoger Quadros <rogerq@ti.com>
      Acked-by: NTony Lindgren <tony@atomide.com>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      f5837ec1
  2. 19 11月, 2013 2 次提交
    • T
      gpio: twl4030: Fix passing of pdata in the device tree case · fd3a5d5b
      Tony Lindgren 提交于
      We still have some legacy code needing the callback functions
      that won't work properly without platform data. To use platform
      data for twl4030-gpio, we need to not trash the possible data.
      
      Cc: linux-gpio@vger.kernel.org
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NFengguang Wu <fengguang.wu@intel.com>
      [tony@atomide.com: folded in fix from Fengguang to use struct assignment]
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      fd3a5d5b
    • T
      gpio: twl4030: Fix regression for twl gpio output · 0b2aa8be
      Tony Lindgren 提交于
      Commit c111feab (gpio: twl4030: Cache the direction and output
      states in private data) improved things in general, but caused a
      regression for setting the GPIO output direction.
      
      The change reorganized twl_direction_out() and twl_set() and swapped
      the function names around in the process. While doing that, a bug got
      introduced that's not obvious while reading the patch as it appears
      as no change to the code.
      
      The bug is we now call function twl4030_set_gpio_dataout() twice in
      both twl_direction_out() and twl_set(). Instead, we should first
      call twl_direction_out() in twl_direction_out() followed by
      twl4030_set_gpio_dataout() in twl_set().
      
      This regression probably has gone unnoticed for a long time as the
      bootloader may have set the GPIO direction properly in many cases.
      This fixes at least the LCD panel not turning on omap3 LDP for
      example.
      
      Cc: linux-gpio@vger.kernel.org
      Cc: stable@vger.kernel.org #v3.9+
      Reviewed-by: NPeter Ujfalusi <peter.ujfalusi@ti.com>
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      0b2aa8be
  3. 02 10月, 2013 1 次提交
  4. 16 8月, 2013 1 次提交
  5. 17 1月, 2013 2 次提交
  6. 29 11月, 2012 2 次提交
  7. 21 11月, 2012 1 次提交
  8. 18 11月, 2012 1 次提交
  9. 13 9月, 2012 1 次提交
  10. 08 9月, 2012 1 次提交
  11. 22 3月, 2012 3 次提交
  12. 07 6月, 2011 1 次提交
  13. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  14. 14 12月, 2009 2 次提交
  15. 29 10月, 2009 1 次提交
    • M
      twl4030-gpio: remove __devexit markings from remove func · 46c529cf
      Mike Frysinger 提交于
      The gpio_twl4030_probe() function calls gpio_twl4030_remove(), and the
      former has __devinit, so the latter cannot use __devexit.  Otherwise we
      hit the section mismatch warning:
      
      WARNING: drivers/gpio/built-in.o(.devinit.text+0x71a): Section mismatch
      	in reference from the function _gpio_twl4030_probe() to the function
      	.devexit.text:_gpio_twl4030_remove()
      The function __devinit _gpio_twl4030_probe() references a function
      	__devexit _gpio_twl4030_remove().
      This is often seen when error handling in the init function uses
      	functionality in the exit path.
      The fix is often to remove the __devexit annotation of
      	_gpio_twl4030_remove() so it may be used outside an exit section.
      Signed-off-by: NMike Frysinger <vapier@gentoo.org>
      Cc: David Brownell <david-b@pacbell.net>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      46c529cf
  16. 07 1月, 2009 1 次提交
  17. 22 10月, 2008 1 次提交