1ARMADA(4) Kernel Interfaces Manual ARMADA(4)
2
6 armada - Marvell Armada 510 and Freescale iMX6 Xorg driver
7
9 Section "Device"
10 Identifier "devname"
11 Driver "armada"
12 ...
13 EndSection
14
17 armada is an Xorg driver for Marvell Armada and Freescale iMX6 SoCs.
18 This is kernel mode setting front end driver, with modular acceleration
19 backends. The following framebuffer depths are supported: 8, 15, 16,
20 24. All visual types are supported for depth 8, and TrueColor visual
21 is supported for the other depths. The driver has preliminary support
22 for the Direct Rendering Infrastructure (DRI) version 2 and version 3.
23 Multi-head configurations are supported.
24 Acceleration support is dependent on a separate acceleration module.
26 See the "GPU ACCELERATION MODULES" section below for additional infor‐
27 mation.
28 Support for video overlay is provided, supporting I420, YV12, I422,
30 YUY2, UYVY, VYUY and YV16 formats, dependent on support from the kernel
31 DRM driver. The common I420 and YV12 formats are converted on the fly
32 by this driver to I422 and YV16 for the hardware. Support is also pro‐
33 vided for video overlay using an XVBO format, which can be used to pass
34 a DRM buffer handle to the video overlay backend.
35
37 The armada driver currently supports the Marvell Armada 510 LCD con‐
38 troller(s) and the Freescale iMX6 IPU.
39 armada communicates with the Linux Kernel Direct Rendering Manager
41 (drm) layer to control and arbitrate access to the hardware. Kernel
42 drm support is required.
43 Other hardware which provides a Linux Kernel drm driver should also
45 work with this driver.
46
49 Several GPU acceleration methods are supported by the DDX driver. Each
50 method is contained within its own module. Details are listed below.
51
53 Two GPU acceleration modules are currently supported.
54 etnaviv_gpu
56 The etnaviv_gpu module provides 2D acceleration with the Vivante 2D
57 PE1.0 and PE2.0 hardware (eg, GC600, GC320), supporting framebuffers
58 with depths of 15, 16, 24.
59 Xrender acceleration is provided for most formats with a depth of 15,
61 16, 24, 32, and on PE2.0 hardware, A8 alpha-only format. Full glyph
62 compositing is also supported with PE2.0 hardware, however glyph
63 caching and accelerated assembling of glyphs for final blend is sup‐
64 ported with all hardware.
65 XV textured overlay is also provided, with support for I420, YV12, UYVY
67 and YUY2 formatted images.
68 vivante_gpu
70 The vivante_gpu module provides 2D acceleration with the Vivante 2D
71 PE1.0 and PE2.0 hardware, supporting framebuffers with depths of 15,
72 16, 24 but is only usable with the armada kernel DRM driver.
73
75 Please refer to xorg.conf(5) for general configuration details. This
76 section only covers configuration details specific to this driver.
77 For this driver it is not required to specify modes in the screen sec‐
79 tion of the config file. The armada driver will request video mode
80 information from the Linux Kernel drm layer.
81 The VideoRAM option is ignored by this driver; video memory is managed
83 by the Linux Kernel drm layer using system memory.
84 The following driver Options are supported:
86 Option "AccelModule" "filename"
88 Force the usage of an acceleration module.
89 Default: try the etnadrm_gpu drivers in turn, selecting the
91 first which initialises.
92 Option "Hotplug" "boolean"
94 This option controls whether the driver automatically notifies
95 when monitors are connected or disconnected.
96 Default: enabled.
98 Option "HWcursor" "boolean"
100 Enable or disable use of the hardware cursor.
101 Default: disabled.
103 Option "UseGPU" "boolean"
105 Enable or disable use of a GPU module for acceleration and tex‐
106 tured XV support.
107 Default: enabled.
109 Option "XvAccel" "boolean"
111 Enable or disable the X Video backend.
112 Default: enabled.
114 Option "XvDisablePrimary" "boolean"
116 Allow the X Video backend to disable the primary plane when X
117 Video image is displayed at full screen.
118 Note: Some kernel drivers may not fully support this (eg, the
120 kernel driver does a full modeset when restoring the primary
121 plane, causing the screen to momentarily blank.) This option
122 should be disabled for such kernel drivers, or the kernel driver
123 updated to avoid such behaviour.
124 Default: enabled.
126 Option "XvPreferOverlay" "boolean"
128 Make the hardware overlay the first XV adapter. Disabling this
129 option makes any GPU provided textured overlay the first XV
130 adapter.
131 Note: iMX hardware does not provide scaling for XV overlay, and
133 this option should be disabled on such systems to prefer tex‐
134 tured overlay instead.
135 Default: Overlay is preferred.
137
140 The following XV attributes are supported by the XV overlay video
141 driver.
142 XV_AUTOPAINT_COLORKEY
144 XV_AUTOPAINT_COLORKEY is used to control whether driver automatically
145 fills the overlay window with the overlay color key. It is a Boolean
146 attribute, with values 0 (never paint color key) and 1 (always paint
147 color key). Default: 1.
148 XV_COLORKEY
150 XV_COLORKEY sets the color used for the overlay color key, in R8G8B8
151 format. Default: 0x0101fe.
152 XV_PIPE
154 XV_PIPE is used to control the CRTC to be used for overlay. A value of
155 -1 allows the driver to select the appropriate CRTC based upon the
156 position of the overlay window. Other values select an explicit CRTC.
157 Default: -1.
158 XV_BRIGHTNESS
160 XV_CONTRAST
161 XV_SATURATION
162 These options can be used to adjust the overlaid picture brightness,
163 contrast and saturation levels. These options are dependent on their
164 presence in the Linux kernel drm driver.
165 XV_ITURBT_709
167 XV_ITURBT_709 sets the colorimetry for YUV format video. A value of 0
168 selects ITU-R BT.601 colorspace. A value of 1 selects ITU-R BT.709
169 colorspace. This option is dependent on the Linux kernel drm driver.
170
174 Textured overlay attributes are dependent on the GPU acceleration mod‐
175 ule.
176 XV_PIPE
178 XV_PIPE is used to select which CRTC is used to synchronize the screen
179 update with the screen scanout to minimise tearing. A value of -1
180 allows the driver to select the appropriate CRTC based upon the posi‐
181 tion of the overlay window. Other vlaues select an explicit CRTC.
182 Default: -1.
183 XV_SYNC_TO_VBLANK
185 XV_SYNC_TO_VBLANK is used to control whether the textured adapter syn‐
186 chronises with the screen scanout to minimise tearing. It is a Boolean
187 attribute with values 0 (never sync) and 1 (always sync.) Default: 1.
188
191 The xf86-video-armada driver is a separately maintained driver, and
192 bugs should be reported to the author.
193
196 Xorg(1), xorg.conf(5), xorgconfig(1), Xserver(1), X(7)
197
199 Authors include: Gerd Knorr, Michel Dänzer, Geert Uytterhoeven, Russell
200 King.
201X Version 11 xf86-video-armada 0.0.0 ARMADA(4)