25 Nov, 2019

1 commit


21 May, 2019

1 commit


27 Jan, 2015

1 commit

  • Previously the struct bus_type exported by the host1x infrastructure was
    only a very basic skeleton. Turn that implementation into a more full-
    fledged bus to support proper probe ordering and power management.

    Note that the bus infrastructure needs to be available before any of the
    drivers can be registered. This is automatically ensured if all drivers
    are built as loadable modules (via symbol dependencies). If all drivers
    are built-in there are no such guarantees and the link order determines
    the initcall ordering. Adjust drivers/gpu/Makefile to make sure that the
    host1x bus infrastructure is initialized prior to any of its users (only
    drm/tegra currently).

    v2: Fix building host1x and tegra-drm as modules
    Reported-by: Dave Airlie

    Reviewed-by: Sean Paul
    Reviewed-by: Mark Zhang
    Signed-off-by: Thierry Reding

    Thierry Reding
     

04 Jun, 2014

1 commit

  • The i.MX Image Processing Unit (IPU) contains a number of image processing
    blocks that sit right in the middle between DRM and V4L2. Some of the modules,
    such as Display Controller, Processor, and Interface (DC, DP, DI) or CMOS
    Sensor Interface (CSI) and their FIFOs could be assigned to either framework,
    but others, such as the dma controller (IDMAC) and image converter (IC) can
    be used by both.
    The IPUv3 core driver provides an internal API to access the modules, to be
    used by both DRM and V4L2 IPUv3 drivers.

    Signed-off-by: Lucas Stach
    Signed-off-by: Philipp Zabel
    Acked-by: Greg Kroah-Hartman

    Philipp Zabel
     

22 Apr, 2013

1 commit

  • Add host1x, the driver for host1x and its client unit 2D. The Tegra
    host1x module is the DMA engine for register access to Tegra's
    graphics- and multimedia-related modules. The modules served by
    host1x are referred to as clients. host1x includes some other
    functionality, such as synchronization.

    Signed-off-by: Arto Merilainen
    Signed-off-by: Terje Bergstrom
    Reviewed-by: Thierry Reding
    Tested-by: Thierry Reding
    Tested-by: Erik Faye-Lund
    Signed-off-by: Thierry Reding

    Terje Bergstrom
     

20 Feb, 2013

1 commit

  • In v3.3, the gma500 drm driver moved from staging to drm group by
    Alan Cox's 3abcf41fb patch. the gma500 drm driver should control
    brightness well and don't need gma500 stub driver anymore.

    Reference:
    http://lists.freedesktop.org/archives/dri-devel/2012-May/023426.html
    http://lists.freedesktop.org/archives/dri-devel/2012-May/023467.html

    Acked-by: Matthew Garrett
    Acked-by: Greg Kroah-Hartman
    Signed-off-by: Lee, Chun-Yi
    Signed-off-by: Dave Airlie

    Lee, Chun-Yi
     

26 Oct, 2010

1 commit

  • Currently, there have no GMA500(Poulsbo) native video driver to support
    intel opregion. So, use this stub driver to enable the acpi backlight
    control sysfs entry files by requrest acpi_video_register.

    [airlied: fix warnings]

    Signed-off-by: Lee, Chun-Yi
    Signed-off-by: Dave Airlie

    Lee, Chun-Yi
     

10 Sep, 2009

1 commit

  • Background:
    Graphic devices are accessed through ranges in I/O or memory space. While most
    modern devices allow relocation of such ranges, some "Legacy" VGA devices
    implemented on PCI will typically have the same "hard-decoded" addresses as
    they did on ISA. For more details see "PCI Bus Binding to IEEE Std 1275-1994
    Standard for Boot (Initialization Configuration) Firmware Revision 2.1"
    Section 7, Legacy Devices.

    The Resource Access Control (RAC) module inside the X server currently does
    the task of arbitration when more than one legacy device co-exists on the same
    machine. But the problem happens when these devices are trying to be accessed
    by different userspace clients (e.g. two server in parallel). Their address
    assignments conflict. Therefore an arbitration scheme _outside_ of the X
    server is needed to control the sharing of these resources. This document
    introduces the operation of the VGA arbiter implemented for Linux kernel.

    Signed-off-by: Benjamin Herrenschmidt
    Signed-off-by: Tiago Vignatti
    Signed-off-by: Dave Airlie
    Signed-off-by: Jesse Barnes

    Benjamin Herrenschmidt
     

14 Jul, 2008

1 commit

  • With the coming of kernel based modesetting and the memory manager stuff,
    the everything in one directory approach was getting very ugly and
    starting to be unmanageable.

    This restructures the drm along the lines of other kernel components.

    It creates a drivers/gpu/drm directory and moves the hw drivers into
    subdirectores. It moves the includes into an include/drm, and
    sets up the unifdef for the userspace headers we should be exporting.

    Signed-off-by: Dave Airlie

    Dave Airlie