1. 16 11月, 2011 12 次提交
  2. 11 11月, 2011 13 次提交
  3. 10 11月, 2011 3 次提交
    • Y
      arm/tegra: enable headphone detection gpio on seaboard · 686448d7
      Yufeng Shen 提交于
      Enable the headphone detection gpio on tegra platform.
      Signed-off-by: NYufeng Shen <miletus@chromium.org>
      Acked-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      686448d7
    • S
      arm/dt: Fix ventana SDHCI power-gpios · c406eeb3
      Stephen Warren 提交于
      Ventana uses the same SDHCI GPIOs as Seaboard; PI6 (70) is the power GPIO
      for the SD port, and there is no power GPIO for the MMC chip.
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      c406eeb3
    • S
      arm/tegra: Don't create duplicate gpio and pinmux devices · 4b91b6fb
      Stephen Warren 提交于
      *_pinmux_init() register the GPIO and pinmux devices so that they're ready
      before any other device needs them.
      
      *_pinmux_init() are also called by board-dt.c in order to set up the GPIO
      and pinmux configurations. In this case, if we register the devices, they
      end up being probed once due to this registration, and a second time due
      to a device-tree node (or vice-versa). The second probe fails since the
      memory regions are already requested. Besides, we don't actually want the
      duplicated devices.
      
      To avoid this duplicate registration, modify *_pinmux_init() to check
      whether it's running on a DT machine. If not, register the pinmux devices.
      If so, don't register them.
      
      Finally, modify board-dt.c to call the *_pinmux_init() after all devices have
      been instantiated from device-tree. This allows the GPIO and pinmux devices
      to be instantiated and initialized before calling functions to configure the
      hardware.
      
      This has one disadvantage: The pinmux and GPIO initialization now happens
      after /all/ devices are instantiated, rather than after just gpio and
      pinmux but before anything else. So the correct HW configuration is not
      in place when e.g. the SD/MMC device is probed. Long-term, this should be
      solved by doing both:
      
      a) Initializing the HW state from DT nodes during GPIO and pinmux device
         probe.
      b) Using the deferred driver probe mechanism, so that drivers can defer
         their probe until after the gpio and pinmux drivers have probed.
      
      v2: s/int is_dt/bool is_dt/
      v3: Use of_machine_is_compatible inside *_pinmux_init() rather than passing
      an explicit parameter into the function from outside.
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      4b91b6fb
  4. 09 11月, 2011 6 次提交
  5. 08 11月, 2011 4 次提交
    • S
      arm/mxs: fix mmc device adding for mach-mx28evk · e94e05ea
      Shawn Guo 提交于
      The merge commit "526b2641 Merge branch 'imx/cleanup' into imx/devel"
      left a duplicated mx28_add_mxs_mmc() call, which causes the problem
      below during boot.
      
        kobject_add_internal failed for mxs-mmc.1 with -EEXIST, don't try
        to register things with the same name in the same directory.
      
      The patch removes this leftover and also change mmc0 adding to align
      with mmc1.
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      e94e05ea
    • T
      ARM: OMAP: Fix export.h or module.h includes · a1bcc1dc
      Tony Lindgren 提交于
      Commit 32aaeffb (Merge branch
      'modsplit-Oct31_2011'...) caused some build errors. Fix these
      and make sure we always have export.h or module.h included
      for MODULE_ and EXPORT_SYMBOL users:
      
      $ grep -rl ^MODULE_ arch/arm/*omap*/*.c | xargs \
        grep -L linux/module.h
        arch/arm/mach-omap2/dsp.c
        arch/arm/mach-omap2/mailbox.c
        arch/arm/mach-omap2/omap-iommu.c
        arch/arm/mach-omap2/smartreflex.c
      
      Also check we either have export.h or module.h included
      for the files exporting symbols:
      
      $ grep -rl EXPORT_SYMBOL arch/arm/*omap*/*.c | xargs \
        grep -L linux/export.h | xargs grep -L linux/module.h
      
      Cc: Russell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      a1bcc1dc
    • A
      ARM: OMAP: omap_device: Include linux/export.h · 55581415
      Axel Lin 提交于
      Include linux/export.h to fix below build warning:
      
        CC      arch/arm/plat-omap/omap_device.o
      arch/arm/plat-omap/omap_device.c:1055: warning: data definition has no type or storage class
      arch/arm/plat-omap/omap_device.c:1055: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL'
      arch/arm/plat-omap/omap_device.c:1055: warning: parameter names (without types) in function declaration
      Signed-off-by: NAxel Lin <axel.lin@gmail.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      55581415
    • P
      arm: Add export.h to recently added files for EXPORT_SYMBOL · 0c073e35
      Paul Gortmaker 提交于
      These files didn't exist at the time of the module.h split, and
      so were not fixed by the commits on that baseline.  Since they use
      the EXPORT_SYMBOL and/or THIS_MODULE macros, they will need the
      new export.h file included that provides them.
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      0c073e35
  6. 07 11月, 2011 2 次提交