没有合适的资源?快使用搜索试试~ 我知道了~
DRM详解,针对intel平台linux内核中的DRM的详解
4星 · 超过85%的资源 需积分: 47 179 下载量 126 浏览量
2014-08-14
11:49:58
上传
评论 9
收藏 128KB PDF 举报
温馨提示
试读
54页
这个文档是准对INTEL平台的linux内核中有关Display相关的文档。INTEL使用DRM的显卡驱动框架来管理视频输出。文档对DRM代码框架作出了详细解释。
资源推荐
资源详情
资源评论
Linux DRM Developer's Guide
Jesse Barnes
Initial version
Intel Corporation
<jesse.barnes@intel.com>
Laurent Pinchart
Driver internals
Ideas on board SPRL
<laurent.pinchart@ideasonboard.com>
Copyright © 2008-2009, 2012 Intel Corporation, Laurent Pinchart
The contents of this file may be used under the terms of the GNU General Public License version 2 (the "GPL") as distributed in the kernel source
COPYING file.
Revision History
Revision 1.0 2012-07-13 LP
Added extensive documentation about driver internals.
Table of Contents
1. Introduction
Page
1
of
54
Linux DRM Developer's Guide
2013
-
4
-
27
http://landley.net/kdocs/htmldocs/drm.html
2. DRM Internals
Driver Initialization
Driver Information
Driver Load
Memory management
The Translation Table Manager (TTM)
The Graphics Execution Manager (GEM)
Mode Setting
Frame Buffer Creation
Output Polling
KMS Initialization and Cleanup
CRTCs (struct drm_crtc)
Planes (struct drm_plane)
Encoders (struct drm_encoder)
Connectors (struct drm_connector)
Cleanup
Output discovery and initialization example
Mode Setting Helper Functions
Helper Functions
CRTC Helper Operations
Encoder Helper Operations
Connector Helper Operations
Modeset Helper Functions Reference
fbdev Helper Functions Reference
Display Port Helper Functions Reference
Vertical Blanking
Page
2
of
54
Linux DRM Developer's Guide
2013
-
4
-
27
http://landley.net/kdocs/htmldocs/drm.html
Open/Close, File Operations and IOCTLs
Open and Close
File Operations
IOCTLs
Command submission & fencing
Suspend/Resume
DMA services
3. Userland interfaces
VBlank event handling
A. DRM Driver API
Chapter 1. Introduction
The Linux DRM layer contains code intended to support the needs of complex graphics devices, usually containing programmable pipelines well
suited to 3D graphics acceleration. Graphics drivers in the kernel may make use of DRM functions to make tasks like memory management, interrupt
handling and DMA easier, and provide a uniform interface to applications.
A note on versions: this guide covers features found in the DRM tree, including the TTM memory manager, output configuration and mode setting,
and the new vblank internals, in addition to all the regular features found in current kernels.
[Insert diagram of typical DRM stack here]
Chapter 2. DRM Internals
Table of Contents
Driver Initialization
Driver Information
Driver Load
Page
3
of
54
Linux DRM Developer's Guide
2013
-
4
-
27
http://landley.net/kdocs/htmldocs/drm.html
Memory management
The Translation Table Manager (TTM)
The Graphics Execution Manager (GEM)
Mode Setting
Frame Buffer Creation
Output Polling
KMS Initialization and Cleanup
CRTCs (struct drm_crtc)
Planes (struct drm_plane)
Encoders (struct drm_encoder)
Connectors (struct drm_connector)
Cleanup
Output discovery and initialization example
Mode Setting Helper Functions
Helper Functions
CRTC Helper Operations
Encoder Helper Operations
Connector Helper Operations
Modeset Helper Functions Reference
fbdev Helper Functions Reference
Display Port Helper Functions Reference
Vertical Blanking
Open/Close, File Operations and IOCTLs
Open and Close
File Operations
IOCTLs
Command submission & fencing
Page
4
of
54
Linux DRM Developer's Guide
2013
-
4
-
27
http://landley.net/kdocs/htmldocs/drm.html
Suspend/Resume
DMA services
This chapter documents DRM internals relevant to driver authors and developers working to add support for the latest features to existing drivers.
First, we go over some typical driver initialization requirements, like setting up command buffers, creating an initial output configuration, and
initializing core services. Subsequent sections cover core internals in more detail, providing implementation notes and examples.
The DRM layer provides several services to graphics drivers, many of them driven by the application interfaces it provides through libdrm, the library
that wraps most of the DRM ioctls. These include vblank event handling, memory management, output management, framebuffer management,
command submission & fencing, suspend/resume support, and DMA services.
Driver Initialization
At the core of every DRM driver is a drm_driver structure. Drivers typically statically initialize a drm_driver structure, and then pass it to one of the
drm_*_init()
functions to register it with the DRM subsystem.
The drm_driver structure contains static information that describes the driver and features it supports, and pointers to methods that the DRM core will
call to implement the DRM API. We will first go through the drm_driver static information fields, and will then describe individual operations in
details as they get used in later sections.
Driver Information
Driver Features
Drivers inform the DRM core about their requirements and supported features by setting appropriate flags in the
driver_features
field. Since those
flags influence the DRM core behaviour since registration time, most of them must be set to registering the drm_driver instance.
u32 driver_features;
Driver Feature Flags
DRIVER_USE_AGP
Driver uses AGP interface, the DRM core will manage AGP resources.
Page
5
of
54
Linux DRM Developer's Guide
2013
-
4
-
27
http://landley.net/kdocs/htmldocs/drm.html
剩余53页未读,继续阅读
小黑9009
- 粉丝: 10
- 资源: 3
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功
- 1
- 2
- 3
前往页