1. 30 4月, 2013 6 次提交
  2. 28 4月, 2013 1 次提交
  3. 24 4月, 2013 3 次提交
  4. 17 4月, 2013 1 次提交
  5. 16 4月, 2013 3 次提交
  6. 13 4月, 2013 3 次提交
  7. 12 4月, 2013 3 次提交
  8. 10 4月, 2013 1 次提交
  9. 09 4月, 2013 4 次提交
    • T
      pinctrl: Add pinctrl-s3c64xx driver · 61dd7261
      Tomasz Figa 提交于
      This patch adds pinctrl-s3c64xx driver which implements pin control
      interface for Samsung S3C64xx SoCs.
      Signed-off-by: NTomasz Figa <tomasz.figa@gmail.com>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      61dd7261
    • M
      ARM: sunxi: Rework the restart code · bc34b5f2
      Maxime Ripard 提交于
      The Allwinner sun6i (A31) has a slightly different watchdog, that
      doesn't allow to use the already existing restart code.
      
      Rework a bit the restart code to allow to plug in more easily different
      restart handlers depending on the device tree.
      
      In the past, we were also meaning sunxi as a generic name covering all
      Allwinner SoCs. This won't be true anymore with the A31 (sun6i) that
      differs pretty much from sun4i and sun5i, and we will end up having
      sunxi, for sun4i and sun5i, and sun6i, which is neither consistent nor
      convenient. So, while we're at it, also change sunxi to sun4i.
      Signed-off-by: NMaxime Ripard <maxime.ripard@free-electrons.com>
      bc34b5f2
    • M
      irqchip: sunxi: Rename sunxi to sun4i · d7fbc6ca
      Maxime Ripard 提交于
      During the introduction of the Allwinner SoC platforms, sunxi was
      initially meant as a generic name for all the variants of the Allwinner
      SoC.
      
      It was ok at the time of the support of only the A10 and A13 that
      looks pretty much the same, but it's beginning to be troublesome with
      the future addition of the Allwinner A31 (sun6i) that is quite
      different, and would introduce some weird logic, where sunxi would
      actually mean in some case sun4i and sun5i but without sun6i...
      
      Moreover, it makes the compatible strings naming scheme not consistent
      with other architectures, where usually for this kind of compability, we
      just use the oldest SoC name that has this IP, so let's do just this.
      Signed-off-by: NMaxime Ripard <maxime.ripard@free-electrons.com>
      d7fbc6ca
    • M
      clocksource: sunxi: Rename sunxi to sun4i · 119fd635
      Maxime Ripard 提交于
      During the introduction of the Allwinner SoC platforms, sunxi was
      initially meant as a generic name for all the variants of the Allwinner
      SoC.
      
      It was ok at the time of the support of only the A10 and A13 that
      looks pretty much the same, but it's beginning to be troublesome with
      the future addition of the Allwinner A31 (sun6i) that is quite
      different, and would introduce some weird logic, where sunxi would
      actually mean in some case sun4i and sun5i but without sun6i...
      
      Moreover, it makes the compatible strings naming scheme not consistent
      with other architectures, where usually for this kind of compability, we
      just use the oldest SoC name that has this IP, so let's do just this.
      Signed-off-by: NMaxime Ripard <maxime.ripard@free-electrons.com>
      119fd635
  10. 08 4月, 2013 1 次提交
  11. 07 4月, 2013 3 次提交
  12. 05 4月, 2013 4 次提交
  13. 04 4月, 2013 1 次提交
    • T
      video: fb: vt8500: Convert framebuffer drivers to standardized binding · 7ab0a484
      Tony Prisk 提交于
      Now that a display timing binding is available, convert our almost identical
      binding to use the standard binding.
      
      This patch converts the vt8500 and wm8505 framebuffer drivers and
      associated dts/dtsi files to use the standard binding as defined in
      bindings/video/display-timing.txt.
      
      There are two side-effects of making this conversion:
      
      1) The fb node should now be in the board file, rather than the soc file as
      the display-timing node is a child of the fb node.
      
      2) We still require a bits per pixel property to initialize the framebuffer
      for the different lcd panels. Rather than including this as part of the
      display timing, it is moved into the framebuffer node.
      
      I have also taken the opportunity to alphabetise the includes of each
      driver to avoid double-ups.
      Signed-off-by: NTony Prisk <linux@prisktech.co.nz>
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      7ab0a484
  14. 03 4月, 2013 3 次提交
  15. 02 4月, 2013 2 次提交
  16. 01 4月, 2013 1 次提交