1. 26 8月, 2014 5 次提交
  2. 13 8月, 2014 1 次提交
  3. 08 8月, 2014 1 次提交
  4. 06 8月, 2014 1 次提交
  5. 04 8月, 2014 2 次提交
    • D
      video: hyperv: hyperv_fb: refresh the VM screen by force on VM panic · 3686fe96
      Dexuan Cui 提交于
      Currently the VSC has no chance to notify the VSP of the dirty rectangle on VM
      panic because the notification work is done in a workqueue, and in panic() the
      kernel typically ends up in an infinite loop, and a typical kernel config has
      CONFIG_PREEMPT_VOLUNTARY=y and CONFIG_PREEMPT is not set, so a context switch
      can't happen in panic() and the workqueue won't have a chance to run. As a
      result, the VM Connection window can't refresh until it's closed and we
      re-connect to the VM.
      
      We can register a handler on panic_notifier_list: the handler can notify
      the VSC and switch the framebuffer driver to a "synchronous mode", meaning
      the VSC flushes any future framebuffer change to the VSP immediately.
      
      v2: removed the MS-TFS line in the commit message
      v3: remove some 'unlikely' markings
      v4: avoid global variables as Tomi Valkeinen suggested
      
      Cc: Haiyang Zhang <haiyangz@microsoft.com>
      Signed-off-by: NDexuan Cui <decui@microsoft.com>
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      3686fe96
    • P
      video: ARM CLCD: Fix DT-related build problems · 1d5167b7
      Pawel Moll 提交于
      This patch fixes the following error when !CONFIG_OF:
      
      drivers/video/fbdev/amba-clcd.c:800:54: warning: ‘struct amba_dev’ declared inside parameter list [enabled by default]
       static struct clcd_board *clcdfb_of_get_board(struct amba_dev *dev)
                                                            ^
      and adds a missing Kconfig select causing this
      when CONFIG_OF && !CONFIG_FB_MODE_HELPERS:
      
      drivers/video/fbdev/amba-clcd.c:567: undefined reference to `fb_videomode_from_videomode'
      Reported-by: NFengguang Wu <fengguang.wu@intel.com>
      Signed-off-by: NPawel Moll <pawel.moll@arm.com>
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      1d5167b7
  6. 30 7月, 2014 5 次提交
  7. 29 7月, 2014 1 次提交
  8. 28 7月, 2014 1 次提交
    • M
      video: clcd-versatile: Depend on ARM · 94f30477
      Mark Brown 提交于
      The Versatile CLCD helpers call dma_alloc_writecombine() which is only
      available on ARM and AVR32, meaning they won't build on other platforms
      including arm64. Unfortunately the current Kconfig enables the symbol
      by default if ARCH_VEXPRESS is defined which means that it is enabled on
      arm64 when building for the ARM reference platforms and models for ARMv8
      since they have many hardware similarities with their pre-ARMv8 systems.
      
      Since all the systems that need the helpers are ARM systems fix this by
      adding a dependency on ARM.
      Signed-off-by: NMark Brown <broonie@linaro.org>
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      94f30477
  9. 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
  10. 13 7月, 2014 2 次提交
  11. 11 7月, 2014 1 次提交
    • B
      x86, ia64: Move EFI_FB vga_default_device() initialization to pci_vga_fixup() · 20cde694
      Bruno Prémont 提交于
      Commit b4aa0163 ("efifb: Implement vga_default_device() (v2)") added
      efifb vga_default_device() so EFI systems that do not load shadow VBIOS or
      setup VGA get proper value for boot_vga PCI sysfs attribute on the
      corresponding PCI device.
      
      Xorg doesn't detect devices when boot_vga=0, e.g., on some EFI systems such
      as MacBookAir2,1.  Xorg detects the GPU and finds the DRI device but then
      bails out with "no devices detected".
      
      Note: When vga_default_device() is set boot_vga PCI sysfs attribute
      reflects its state.  When unset this attribute is 1 whenever
      IORESOURCE_ROM_SHADOW flag is set.
      
      With introduction of sysfb/simplefb/simpledrm efifb is getting obsolete
      while having native drivers for the GPU also makes selecting sysfb/efifb
      optional.
      
      Remove the efifb implementation of vga_default_device() and initialize
      vgaarb's vga_default_device() with the PCI GPU that matches boot
      screen_info in pci_fixup_video().
      
      [bhelgaas: remove unused "dev" in efifb_setup()]
      Fixes: b4aa0163 ("efifb: Implement vga_default_device() (v2)")
      Tested-by: NAnibal Francisco Martinez Cortina <linuxkid.zeuz@gmail.com>
      Signed-off-by: NBruno Prémont <bonbons@linux-vserver.org>
      Signed-off-by: NBjorn Helgaas <bhelgaas@google.com>
      Acked-by: NMatthew Garrett <matthew.garrett@nebula.com>
      CC: stable@vger.kernel.org	# v3.5+
      20cde694
  12. 04 7月, 2014 15 次提交
  13. 01 7月, 2014 4 次提交