1. 23 7月, 2014 1 次提交
    • A
      video: fix up versatile CLCD helper move · ec4c4d87
      Arnd Bergmann 提交于
      commit 11c32d7b ("video: move Versatile CLCD helpers")
      moved files out of the plat-versatile directory but in the process
      got a few of the dependencies wrong:
      
      - If CONFIG_FB is not set, the file no longer gets built, resulting
        in a link error
      - If CONFIG_FB or CONFIG_FB_ARMCLCD are disabled, we also get a
        Kconfig warning for incorrect dependencies due to the symbol
        being 'select'ed from the platform Kconfig.
      - When the file is not built, we also get a link error for missing
        symbols.
      
      This patch should fix all three, by removing the 'select' statements,
      changing the Kconfig description of the symbol to be enabled in
      exactly the right configurations, and adding inline stub functions
      for the case when the framebuffer driver is disabled.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Reviewed-by: NLinus Walleij <linus.walleij@linaro.org>
      ec4c4d87
  2. 13 7月, 2014 2 次提交
  3. 27 6月, 2014 1 次提交
    • L
      video: move Versatile CLCD helpers · 11c32d7b
      Linus Walleij 提交于
      This moves the Versatile-specific helper code and panel database
      down into the drivers/video folder next to the CLCD driver
      itself, preserving the config symbol but also moving the header
      to platform data.
      
      This is necessary to rid the Integrator of this final <plat/*>
      inclusion dependency and get us one less user of the
      plat-versatile folder.
      
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
      Cc: linux-fbdev@vger.kernel.org
      Cc: Russell King <linux@arm.linux.org.uk>
      Acked-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      11c32d7b
  4. 16 5月, 2014 1 次提交
  5. 09 5月, 2014 4 次提交
  6. 07 5月, 2014 1 次提交
    • A
      video: sh_mobile_lcdcfb depends on meram · 423431a3
      Arnd Bergmann 提交于
      The sh_mobile_lcdcfb driver calls interfaces provided
      by the corresponding "meram" helper. This fails if meram
      is a module but lcdcfb is built-in.
      
      To work around it, this uses special Kconfig magic to
      only allow lcdcfb to be built if
      a) both are modules,
      b) meram is built-in, or
      c) meram is disabled and the helpers stubbed out
      
      Changing meram from 'y' to 'm' now forces clcd to
      be a module as well, which seems to be the desired
      behavior.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NPeter Griffin <peter.griffin@linaro.org>
      Cc: Simon Horman <horms+renesas@verge.net.au>
      Cc: Magnus Damm <magnus.damm@gmail.com>
      Cc: linux-sh@vger.kernel.org
      Cc: Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
      Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
      Cc: linux-fbdev@vger.kernel.org
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      423431a3
  7. 30 4月, 2014 1 次提交
  8. 17 4月, 2014 1 次提交
  9. 14 4月, 2014 1 次提交
  10. 20 3月, 2014 1 次提交
  11. 05 3月, 2014 1 次提交
  12. 28 2月, 2014 1 次提交
  13. 14 2月, 2014 1 次提交
  14. 17 1月, 2014 2 次提交
  15. 31 10月, 2013 1 次提交
  16. 27 9月, 2013 1 次提交
  17. 09 8月, 2013 1 次提交
  18. 03 8月, 2013 1 次提交
  19. 26 7月, 2013 1 次提交
  20. 08 7月, 2013 1 次提交
  21. 26 6月, 2013 1 次提交
  22. 25 5月, 2013 2 次提交
    • G
      fbdev: FB_GOLDFISH should depend on HAS_DMA · e5ee7305
      Geert Uytterhoeven 提交于
      If NO_DMA=y:
      
        drivers/built-in.o: In function `goldfish_fb_remove':
        drivers/video/goldfishfb.c:301: undefined reference to `dma_free_coherent'
        drivers/built-in.o: In function `goldfish_fb_probe':
        drivers/video/goldfishfb.c:247: undefined reference to `dma_alloc_coherent'
        drivers/video/goldfishfb.c:280: undefined reference to `dma_free_coherent'
      Signed-off-by: NGeert Uytterhoeven <geert@linux-m68k.org>
      Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      e5ee7305
    • S
      drivers/video: implement a simple framebuffer driver · 26549c8d
      Stephen Warren 提交于
      A simple frame-buffer describes a raw memory region that may be rendered
      to, with the assumption that the display hardware has already been set
      up to scan out from that buffer.
      
      This is useful in cases where a bootloader exists and has set up the
      display hardware, but a Linux driver doesn't yet exist for the display
      hardware.
      
      Examples use-cases include:
      
      * The built-in LCD panels on the Samsung ARM chromebook, and Tegra
        devices, and likely many other ARM or embedded systems.  These cannot
        yet be supported using a full graphics driver, since the panel control
        should be provided by the CDF (Common Display Framework), which has been
        stuck in design/review for quite some time.  One could support these
        panels using custom SoC-specific code, but there is a desire to use
        common infra-structure rather than having each SoC vendor invent their
        own code, hence the desire to wait for CDF.
      
      * Hardware for which a full graphics driver is not yet available, and
        the path to obtain one upstream isn't yet clear.  For example, the
        Raspberry Pi.
      
      * Any hardware in early stages of upstreaming, before a full graphics
        driver has been tackled.  This driver can provide a graphical boot
        console (even full X support) much earlier in the upstreaming process,
        thus making new SoC or board support more generally useful earlier.
      
      [akpm@linux-foundation.org: make simplefb_formats[] static]
      Signed-off-by: NStephen Warren <swarren@wwwdotorg.org>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Acked-by: NOlof Johansson <olof@lixom.net>
      Cc: Rob Clark <robclark@gmail.com>
      Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
      Cc: Tomasz Figa <tomasz.figa@gmail.com>
      Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      26549c8d
  23. 10 5月, 2013 1 次提交
    • F
      video: mxsfb: Adapt to new videomode API · d7321df3
      Fabio Estevam 提交于
      commit 6cd2c7db (videomode: videomode_from_timing work) changed the name of
      the function from videomode_from_timing() to videomode_from_timings().
      
      commit 32ed6ef1 (videomode: create enum for videomode's display flags) changed
      the 'data_flags' field in videomode structure to 'flags'
      
      Adapt to these changes in order to fix the following errors:
      
      drivers/video/mxsfb.c:761:3: error: too many arguments to function 'videomode_from_timing'
      drivers/video/mxsfb.c:761:7: error: void value not ignored as it ought to be
      drivers/video/mxsfb.c:768:9: error: 'struct videomode' has no member named 'data_flags'
      drivers/video/mxsfb.c:770:9: error: 'struct videomode' has no member named 'data_flags'
      
      Also, select VIDEOMODE_HELPER instead of OF_VIDEOMODE, as this one is
      deprecated.
      Signed-off-by: NFabio Estevam <fabio.estevam@freescale.com>
      Acked-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      d7321df3
  24. 30 4月, 2013 1 次提交
  25. 22 4月, 2013 1 次提交
  26. 17 4月, 2013 1 次提交
  27. 16 4月, 2013 1 次提交
  28. 15 4月, 2013 1 次提交
  29. 04 4月, 2013 4 次提交
  30. 12 3月, 2013 1 次提交
    • T
      videomode: simplify videomode Kconfig and Makefile · a38884f6
      Tomi Valkeinen 提交于
      This patch simplifies videomode related Kconfig and Makefile. After this
      patch, there's only one non-user selectable Kconfig option left,
      VIDEOMODE_HELPERS. The reasons for the change:
      
      * Videomode helper functions are not something that should be shown in
        the kernel configuration options. The related code should just be
        included if it's needed, i.e. selected by drivers using videomode.
      
      * There's no need to have separate Kconfig options for videomode and
        display_timing. First of all, the amount of code for both is quite
        small. Second, videomode depends on display_timing, and display_timing
        in itself is not really useful, so both would be included in any case.
      
      * CONFIG_VIDEOMODE is a bit vague name, and CONFIG_VIDEOMODE_HELPERS
        describes better what's included.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      Cc: Steffen Trumtrar <s.trumtrar@pengutronix.de>
      Acked-by: NLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      a38884f6
  31. 22 2月, 2013 1 次提交