https://zhuanlan.zhihu.com/p/534267979
显示子系统是显示输出相关软件硬件的统称，它包括VOP 和 RGB 、BT1120、BT656、I8080、LVDS、MIPI DSI、EDP、DP、HDMI等显示信号输出以及与之对应的软件驱动。
上面的DSS框图，整个显示通路最后端，由RGA、GPU、VPU组成显示图形加速模块、他们是针对图形处理优化设计的硬件IP，能够高效的进行图形的生成和进一步处理（例如，GPU通过OpenGL功能提供图像渲染功能，RGA可以对图像数据进行缩放、旋转、合成等2D处理，VPU可以高效的进行视频解码），从而减轻CPU负担。
经过这些图像加速模块处理后的数据会放在DDR中，然后VOP读取，根据应用需求进行Alpha叠加，颜色空间转换、gamma矫正、HDR转换处理等，再发送到对应的显示接口模块（HDMI/DP/DSI/RGB/LVDS）,这些接口模块会把接受收到的数据转换成符合给自协议的数据流，发送到显示器或者屏幕，呈现在最终的用户眼前。
VOP1.0是多用户VOP方式来显示多屏幕显示，即正常情况下，一个VOP在同一时刻只能输出一路独立的显示时序，驱动一个屏幕显示独立的内容。如果需要实现双屏幕显示，则需要两个VOP来实现。
VOP2.0采用统一显示架构，即整个SOC上只存在一个VOP，但是在VOP的后端设计多路独立的Video Port（简称VP）输出接口，这些VP能够独立同时独立工作，并且输出相关独立的显示时许。
DRM全程是Direct Rendering Manger，进行显示输出管理、buffer分配、帧缓冲。对应的userspace库libdrm，libdrm库提供了一系列友好的控制封装，是用户可以进行显示的控制和buffer申请。DRM设备节点为"/dev/dri/cardX", X为0-15的数值，默认使用的是“/dev/dri/card0”。
| 基本概念 | 说明 |
|---|---|
| CRTC（Cathode Ray Tube Controller） | 阴极射线管控制器，显示控制器，内部VOP模块或者VOP2中Video Port的抽象 |
| Plane | 图层，SoC内部VOP模块win图层的抽象 |
| Encoder | 输出转换器（编码器），指的是RGB、LVDS、DSI、eDP、DP、HDMI、CVBS、VGA等显示接口 |
| Connector | 连接器，指的是encoder和panel之间交互的接口部分 |
| Bridge | 桥接设备，一般用于注册Encoder后面另外再转接芯片，如DSI2HDMI转换芯片 |
| Panel | 泛指屏幕，各种LCD显示设备的抽象 |
| GEM | DRM下buffer管理和分配，类似ION、DMA BUFFER |
CRTC常用行为：
ENCODER的常用行为如下：
Connector的常用行为如下：
显示驱动在 U-Boot 中主要提供开机 logo 显示和充电界面显示这两个功能。
驱动加载顺序
需要注意的是，DRM驱动时一系列相关模块的驱动的结合，他包含了backlight,panel,rgb,lvds,dsi,edp,hdmi,vop等等显示通路上的依赖模块。只有这些相互依赖的模块都加载完整，整个drm系统才算启动完成。
因为这些复杂的依赖关系，在 drm 系统初始化的过程中，可能会出现某个资源暂时未就绪，而导致某个模块暂时无法顺利加载的情况，为了解决这种问题，drm 驱动利用了 Linux 驱动 中的 deferred probe 机制，当发现某个依赖的资源未就绪的时候，驱动返回 -EPROBE_DEFER(-517) , 然后退出。Linux kernel 会在稍后再次尝试加载这个驱动，直到依赖的资源就绪，驱动顺利加载为止。
例子：
[1.747190] rockchip-drm display-subsystem: bound fdd90000.vop (ops vop2_component_ops)
[1.747877] dwhdmi-rockchip fde80000.hdmi: registered ddc I2C bus driver
[1.748022] rockchip-drm display-subsystem: bound fde80000.hdmi (ops
dw_hdmi_rockchip_ops)
[1.748676] dwhdmi-rockchip fdea0000.hdmi: registered ddc I2C bus driver
[1.748807] rockchip-drm display-subsystem: bound fdea0000.hdmi (ops
dw_hdmi_rockchip_ops)
[1.748840] dw-mipi-dsi2 fde20000.dsi: [drm:dw_mipi_dsi2_bind] *ERROR* Failed to find
panel or bridge: -517
[1.755174] panel-simple-dsi fde20000.dsi.0: failed to get power regulator: -517
[1.759296] brd: module loaded
[1.764374] loop: module loaded
[1.764528] zram: Added device: zram0
[1.764698] system_heap: orders[0] = 6
[2.248871] imx415 5-001a: supply dovdd not found, using dummy regulator
[2.416673] rockchip-drm display-subsystem: bound fdd90000.vop (ops vop2_component_ops)
[2.418711] dwhdmi-rockchip fde80000.hdmi: registered ddc I2C bus driver
[2.420336] rockchip-drm display-subsystem: bound fde80000.hdmi (ops
dw_hdmi_rockchip_ops)
[2.421725] dwhdmi-rockchip fdea0000.hdmi: registered ddc I2C bus driver
[2.422291] rockchip-drm display-subsystem: bound fdea0000.hdmi (ops
dw_hdmi_rockchip_ops)
[2.422318] dw-mipi-dsi2 fde20000.dsi: [drm:dw_mipi_dsi2_bind] *ERROR* Failed to find
panel or bridge: -517
[2.433888] input: adc-keys as /devices/platform/adc-keys/input/input3
[2.466237] rockchip-drm display-subsystem: bound fdd90000.vop (ops vop2_component_ops)
[2.468705] dwhdmi-rockchip fde80000.hdmi: registered ddc I2C bus driver
[2.469751] rockchip-drm display-subsystem: bound fde80000.hnd fde20000.dsi (ops
dw_mipi_dsi2_ops)
[2.472282] rockchip-drm display-subsystem: bound fde50000.dp (ops dw_dp_component_ops)
[2.472319] rockchip-drm display-subsystem: bound fde60000.dp (ops dw_dp_component_ops)
[2.531892] rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device
[2.532850] [drm] Initialized rockchip 3.0.0 20140818 for display-subsystem on minor 0从上面的 log 我们可以看到，在第 6 行和第 18 行，mipi dsi 驱动因为找不到 panel 或者 bridge 这个依赖资源，而返回-EPROBE_DEFER 退出，一直到第 23 行，dsi 驱动获取到依赖的资源 bind 成功，最终看到整个 drm 驱动完成加载的标准 log。
DTS配置：
在一颗SoC上，可能由多个VOP，HDMI，eDP，DP，MIPI，Panel模块，根据具体产品定义，一款产品可能只需要使用其中一部分模块组成显示通路。具体使用那些模块，以及这些模块之间如何衔接通过dts配置。
在每一个支持drm显示功能的SoC的核心dts里面，都会由如下display_subsystem节点：
display_subsystem: display-subsystem {
compatible = "rockchip,display-subsystem";
memory-region = <&drm_logo>, <&drm_cubic_lut>;
memory-region-names = "drm-logo", "drm-cubic-lut";
ports = <&vop_out>;
devfreq = <&dmc>;
route {
route_dsi0: route-dsi0 {
status = "disabled";
logo,uboot = "logo.bmp";
logo,kernel = "logo_kernel.bmp";
logo,mode = "center";
charge_logo,mode = "center";
connect = <&vp0_out_dsi0>;
};
route_dsi1: route-dsi1 {
status = "disabled";
logo,uboot = "logo.bmp";
logo,kernel = "logo_kernel.bmp";
logo,mode = "center";
charge_logo,mode = "center";
connect = <&vp0_out_dsi1>;
};
route_edp: route-edp {
status = "disabled";
logo,uboot = "logo.bmp";
logo,kernel = "logo_kernel.bmp";
logo,mode = "center";
charge_logo,mode = "center";
connect = <&vp0_out_edp>;
};
route_hdmi: route-hdmi {
status = "disabled";
logo,uboot = "logo.bmp";
logo,kernel = "logo_kernel.bmp";
logo,mode = "center";
charge_logo,mode = "center";
connect = <&vp1_out_hdmi>;
};
route_lvds: route-lvds {
status = "disabled";
logo,uboot = "logo.bmp";
logo,kernel = "logo_kernel.bmp";
logo,mode = "center";
charge_logo,mode = "center";
connect = <&vp1_out_lvds>;
};
route_rgb: route-rgb {
status = "disabled";
logo,uboot = "logo.bmp";
logo,kernel = "logo_kernel.bmp";
logo,mode = "center";
charge_logo,mode = "center";
connect = <&vp2_out_rgb>;
};
};
};该节点控制drm_drv.c驱动的加载。
vop节点
vop节点描述了VOP硬件资源，控制vop驱动的加载drm_vop.c drm_vop2.c,它描述了如下的显示通路连接关系：
vop_out: ports节点描述vop，vop0/1/2对应vop上video port 0/1/2三个独立的输出通路。
vp0/1/2：port下的endpoint描述的时VP和显示接口的连接关系，以上面的dts描述为例：vp0节点下有
vp0_out_dsi0，vp0_out_dsi1，vp0_out_edp，vp0_out_hdmi四个节点，说明vp0可以和dsi0、dsi1、
edp、hdmi、四个显示接口连接。
每个endpoint通过remote-endpoint属性和对应的显示接口组成一个连接通路，比如和hdmi显示接口的连接：
hdmi: hdmi@fe0a0000 {
compatible = "rockchip,rk3568-dw-hdmi";
...
status = "disabled";
ports{
....
port@0 {
reg = <0>;
....
hdmi_in_vp0: endpoint@0
{
reg = <0>;
remote-endpoint = <&vp0_out_hdmi>;
status = "disabled";
};
hdmi_in_vp1: endpoint@1 {
reg = <1>;
remote-endpoint = <&vp1_out_hdmi>;
status = "disabled";
}
}
};
};希望 HDMI 连接在 vp0 上，则 dts 中需要做如下设置：
&hdmi {
status = "okay";
};
&hdmi_in_vp0 {
status = "okay";
};
&hdmi_in_vp1 {
status = "disabled";
};
&route_hdmi {
status = "okay";
connect = <&vp0_out_hdmi>;
};单路DSI
双通道DSI
| 驱动 | 文件清单 |
|---|---|
| Core | drivers/gpu/drm/rockchip/rockchip_drm_drv.c |
| framebuffer | drivers/gpu/drm/rockchip/rockchip_drm_fb.c |
| gem | drivers/gpu/drm/rockchip/rockchip_drm_gem.c |
| vop | drivers/gpu/drm/rockchip/rockchip_drm_vop.c drivers/gpu/drm/rockchip/rockchip_vop_reg.c |
| lvds | drivers/gpu/drm/rockchip/rockchip_lvds.c |
| rga | drivers/gpu/drm/rockchip/rockchip_drm_rga.c |
| mipi | drivers/gpu/drm/rockchip/dw-mipi-dsi.c |
| hdmi | drivers/gpu/drm/rockchip/inno_hdmi.c |
| edp | drivers/gpu/drm/rockchip/analogix_dp-rockchip.c drivers/gpu/drm/bridge/analogix/analogix_dp_core.c drivers/gpu/drm/bridge/analogix/analogix_dp_reg.c |
| dp | drivers/gpu/drm/rockchip/cdn-dp-core.c drivers/gpu/drm/rockchip/cdn-dp-reg.c |
框架代码：drivers/base/component.c
功能：
component framework作者Russell King对该机制的描述:
Subsystems such as ALSA, DRM and others require a single card-level
device structure to represent a subsystem. However, firmware tends to
describe the individual devices and the connections between them.
Therefore, we need a way to gather up the individual component devices
together, and indicate when we have all the component devices.
We do this in DT by providing a “superdevice” node which specifies
the components, eg:
imx-drm {
compatible = "fsl,drm";
crtcs = <&ipu1>;
connectors = <&hdmi>;
};
The superdevice is declared into the component support, along with the
subcomponents. The superdevice receives callbacks to locate the
subcomponents, and identify when all components are present. At this
point, we bind the superdevice, which causes the appropriate subsystem
to be initialised in the conventional way.
When any of the components or superdevice are removed from the system,
we unbind the superdevice, thereby taking the subsystem down.
在dts中, 有一个总的设备节点, 所有的子设备信息都通过dts描述关联起来, 这样系统 开机后, 就能统一的管理各个设备.
设备device tree:
display_subsystem: display-subsystem {
compatible = “rockchip,display-subsystem”;
ports = <&vopl_out>, <&vopb_out>;
status = “disabled”;
};
代码位置：
drivers/gpu/drm/rockchip/rockchip_drm_drv.c
drivers/gpu/drm/rockchip/rockchip_drm_drv.h主体结构：
static struct drm_driver rockchip_drm_driver = {
.driver_features = DRIVER_MODESET | DRIVER_GEM |
DRIVER_PRIME | DRIVER_ATOMIC |
DRIVER_RENDER,
.preclose = rockchip_drm_preclose,
.lastclose = rockchip_drm_lastclose,
.get_vblank_counter = drm_vblank_no_hw_counter,
.open = rockchip_drm_open,
.postclose = rockchip_drm_postclose,
.enable_vblank = rockchip_drm_crtc_enable_vblank,
.disable_vblank = rockchip_drm_crtc_disable_vblank,
.gem_vm_ops = &rockchip_drm_vm_ops,
.gem_free_object = rockchip_gem_free_object,
.dumb_create = rockchip_gem_dumb_create,
.dumb_map_offset = rockchip_gem_dumb_map_offset,
.dumb_destroy = drm_gem_dumb_destroy,
.prime_handle_to_fd = drm_gem_prime_handle_to_fd,
.prime_fd_to_handle = drm_gem_prime_fd_to_handle,
.gem_prime_import = drm_gem_prime_import,
.gem_prime_export = drm_gem_prime_export,
.gem_prime_get_sg_table = rockchip_gem_prime_get_sg_table,
.gem_prime_import_sg_table = rockchip_gem_prime_import_sg_table,
.gem_prime_vmap = rockchip_gem_prime_vmap,
.gem_prime_vunmap = rockchip_gem_prime_vunmap,
.gem_prime_mmap = rockchip_gem_mmap_buf,
#ifdef CONFIG_DEBUG_FS
.debugfs_init = rockchip_drm_debugfs_init,
.debugfs_cleanup = rockchip_drm_debugfs_cleanup,
#endif
.ioctls = rockchip_ioctls,
.num_ioctls = ARRAY_SIZE(rockchip_ioctls),
.fops = &rockchip_drm_driver_fops,
.name = DRIVER_NAME,
.desc = DRIVER_DESC,
.date = DRIVER_DATE,
.major = DRIVER_MAJOR,
.minor = DRIVER_MINOR,
};代码位置:
drivers/gpu/drm/rockchip/rockchip_drm_vop.c
drivers/gpu/drm/rockchip/rockchip_vop_reg.c结构介绍：
struct vop;
// vop 驱动根结构, 一个vop对应一个struct vop结构
struct vop_win;
// 描述图层信息, 一个硬件图层对应一个struct vop_win结构寄存器读写：
为了兼容各种不同版本的vop, vop驱动里面使用了寄存器级的抽象, 由一个结构体来保
存抽象关系, 这样主体逻辑只需要操作抽象后的功能定义, 由抽象的读写接口根据抽象
关系写到真实的vop硬件中.示例:
static const struct vop_win_phy rk3288_win23_data = {
.enable = VOP_REG(RK3288_WIN2_CTRL0, 0x1, 4),
}
static const struct vop_win_phy rk3368_win23_data = {
.enable = VOP_REG(RK3368_WIN2_CTRL0, 0x1, 4),
}
rk3368和rk3288图层的地址分布不同, 但在结构定义的时候, 可以将不同的硬件图层bit
映射到同一个enable功能上, 这样vop驱动主体调用VOP_WIN_SET(vop, win, enable, 1);
时就能操作到真实的vop寄存器了.
图层接口：
static const struct drm_plane_helper_funcs plane_helper_funcs = {
// 预先对图层进行处理
.prepare_fb = vop_plane_prepare_fb,
// 图层显示完成后的处理
.cleanup_fb = vop_plane_cleanup_fb,
// 在显示前进行参数检查
.atomic_check = vop_plane_atomic_check,
// 更新图层参数
.atomic_update = vop_plane_atomic_update,
// 关闭图层
.atomic_disable = vop_plane_atomic_disable,
};vop接口:
static const struct drm_crtc_helper_funcs vop_crtc_helper_funcs = {
// 使能vop, 在这里面会将timing配好
.enable = vop_crtc_enable,
// 关闭vop
.disable = vop_crtc_disable,
// 对timing进行检查修正
.mode_fixup = vop_crtc_mode_fixup,
// 在一帧显示开始前做的处理
.atomic_begin = vop_crtc_atomic_begin,
// 检查显示的参数
.atomic_check = vop_crtc_atomic_check,
// 提交硬件显示
.atomic_flush = vop_crtc_atomic_flush,
};DRM_IGNORE_IOTCL_PERMIT
这个是由我们添加的, 用于解决android上其他进程模块无法访问drm的问题,目前仅使用在android项目上CONFIG_DRM_FBDEV_EMULATION
使能该功能后, drm将模拟一个framebuffer设备, 可用于基于fbdev的基础显示框架.CONFIG_DRM_LOAD_EDID_FIRMWARE
allow loading an EDID as firmware to override broken monitor
Broken monitors and/or broken graphic boards may send erroneous or no
EDID data. This also applies to broken KVM devices that are unable to
correctly forward the EDID data of the connected monitor but invent
their own fantasy data.
This patch allows to specify an EDID data set to be used instead of
probing the monitor for it. It contains built-in data sets of frequently
used screen resolutions. In addition, a particular EDID data set may be
provided in the /lib/firmware directory and loaded via the firmware
interface. The name is passed to the kernel as module parameter of the
drm_kms_helper module either when loaded
options drm_kms_helper edid_firmware=edid/1280x1024.bin
or as kernel commandline parameter
drm_kms_helper.edid_firmware=edid/1280x1024.bin
It is also possible to restrict the usage of a specified EDID data set
to a particular connector. This is done by prepending the name of the
connector to the name of the EDID data set using the syntax
edid_firmware=[<connector>:]<edid>
such as, for example,
edid_firmware=DVI-I-1:edid/1920x1080.bin
edid_firmware=eDP-1:edid/1280x480.bin,DP-2:edid/1920x1080.bin
in which case no other connector will be affected.
1024x768 edid/1024x768.bin
1280x1024 edid/1280x1024.bin
1680x1050 edid/1680x1050.bin
1920x1080 edid/1920x1080.bin
They are ignored, if a file with the same name is available in the
/lib/firmware directory.
The built-in EDID data sets are based on standard timings that may not
apply to a particular monitor and even crash it. Ideally, EDID data of
the connected monitor should be used. They may be obtained through the
drm/cardX/cardX-<connector>/edid entry in the /sys/devices PCI directory
of a correctly working graphics adapter.
总的drm device结构如下:
// rockchip drm core 设备
display_subsystem: display-subsystem {
compatible = “rockchip,display-subsystem”;
ports = <&vopl_out>, <&vopb_out>;
};
// 显示控制器vop驱动
vopl: vop@ff8f0000 {
compatible = “rockchip,rk3399-vop-lit”;
vopl_out: port {
vopl_out_edp: endpoint@1 {
reg = <1>;
remote-endpoint = <&edp_in_vopl>;
};
};
};
// edp驱动
edp: edp@ff970000 {
compatible = “rockchip,rk3399-edp”;
ports {
edp_in: port@0 {
edp_in_vopl: endpoint@1 {
reg = <1>;
remote-endpoint = <&vopl_out_edp>;
};
};
edp_out: port@1 {
edp_out_panel: endpoint@0 {
reg = <0>;
remote-endpoint = <&panel_in_edp>;
};
};
};
};
edp屏驱动
edp_panel: edp-panel {
compatible = “lg,lp079qx1-sp0v”, “panel-simple”;
//通过短字符串"lg,lp079qx1-sp0v"来匹配写死在kernel源码中的timing
ports {
panel_in_edp: endpoint {
remote-endpoint = <&edp_out_panel>;
};
};
};
通用屏驱动:
drivers/gpu/drm/panel/panel-simple.cdevice-tree:
Required properties:
power-supply: regulator to provide the supply voltage
Optional properties:
compatible: value maybe one of the following
“simple-panel”;
“simple-panel-dsi”;
ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
enable-gpios: GPIO pin to enable or disable the panel
backlight: phandle of the backlight device attached to the panel
Required properties when compatible is “simple-panel” or “simple-panel-dsi”:
Optional properties:
Optional properties when compatible is a dsi devices:
dsi,flags: dsi operation mode related flags
dsi,format: pixel format for video mode
dsi,lanes: number of active data lanes
屏幕的配置方式一：使用短字符串匹配写死的timing
1.把timings写在drivers/gpu/drm/panel/panel-simple.c中, 直接以短字符匹配, 该方式为upstream推荐的使用方式.
DeviceTree:
panel: panel {
compatible = “cptt,claa101wb01”;
ddc-i2c-bus = <&panelddc>;
power-supply = <&vdd_pnl_reg>;
enable-gpios = <&gpio 90 0>;
backlight = <&backlight>;
delay,prepare = <10>;
delay,enable = <10>;
delay,disable = <10>;
delay,unprepare = <10>;
};drivers/gpu/drm/panel/panel-simple.c:
static const struct drm_display_mode lg_lp097qx1_spa1_mode = {
.clock = 205210,
.hdisplay = 2048,
.hsync_start = 2048 + 150,
.hsync_end = 2048 + 150 + 5,
.htotal = 2048 + 150 + 5 + 5,
.vdisplay = 1536,
.vsync_start = 1536 + 3,
.vsync_end = 1536 + 3 + 1,
.vtotal = 1536 + 3 + 1 + 9,
.vrefresh = 60,
};
static const struct panel_desc lg_lp097qx1_spa1 = {
.modes = &lg_lp097qx1_spa1_mode,
.num_modes = 1,
.size = {
.width = 320,
.height = 187,
},
};
static const struct of_device_id platform_of_match[] = {
[…]
}, {
.compatible = “lg,lp097qx1-spa1”,
.data = &lg_lp097qx1_spa1,
}, {
[…]
}屏配置方式二: 直接将timing写在dts文件中
2.把使用display-timings结构, 直接把timing写在dts文件中, 这类适用于简单的屏配置
panel: panel {
compatible = “simple-panel-dsi”;
ddc-i2c-bus = <&panelddc>;
power-supply = <&vdd_pnl_reg>;
enable-gpios = <&gpio 90 0>;
backlight = <&backlight>;
dsi,flags = <MIPI_DSI_MODE_VIDEO |
MIPI_DSI_MODE_VIDEO_BURST |
MIPI_DSI_MODE_VIDEO_SYNC_PULSE>;
dsi,format = <MIPI_DSI_FMT_RGB888>;
dsi,lanes = <4>;
delay,prepare = <10>;
delay,enable = <10>;
delay,disable = <10>;
delay,unprepare = <10>;display-timings { native-mode = <&timing0>; timing0: timing0 { clock-frequency = <160000000>; hactive = <1200>; vactive = <1920>; hback-porch = <21>; hfront-porch = <120>; vback-porch = <18>; vfront-porch = <21>; hsync-len = <20>; vsync-len = <3>; hsync-active = <0>; vsync-active = <0>; de-active = <0>; pixelclk-active = <0>; }; };};
屏配置方式三: 使用edid
3.不填写任何timing, 直接使用edid来获取timing
panel: panel {
compatible = “simple-panel-dsi”;
//compatible = “simple-panel”;
ddc-i2c-bus = <&panelddc>;
power-supply = <&vdd_pnl_reg>;
enable-gpios = <&gpio 90 0>;
backlight = <&backlight>;
delay,prepare = <10>;
delay,enable = <10>;
delay,disable = <10>;
delay,unprepare = <10>;
};Document:
Documentation/devicetree/bindings/display/panel/simple-panel.txt步骤一：
参考《屏配置的几个方式》章节，先使用edid的方式，在dts里面写入:
panel: panel {
compatible = “simple-panel”;
ddc-i2c-bus = <&panelddc>;
power-supply = <&vdd_pnl_reg>;
enable-gpios = <&gpio 90 0>;
backlight = <&backlight>;
};如果屏的edid正常， power, gpio, backlight配置正常，应该就能看到显示了
步骤二：
由于屏的edid是有机率损坏的，做产品是有风险的，所以建议把timing写死到代码里面:
完成步骤一后，可以从uboot串口上获取当前的屏的信息:
Maximum visible display size: 26 cm x 17 cm
Power management features: no active off, no suspend, no standby
Estabilished timings:
Standard timings:
2400x1600 59 Hz (detailed)
Monitor name: LQ123P1JX31
Detailed mode clock 252750 kHz, flags[a]
H: 2400 2448 2480 2560
V: 1600 1603 1613 1646
bus_format: 1009
参考《屏配置的几个方式》章节, 屏配置方式一, 将该timing写死到kernel中.
驱动：
drivers/gpu/drm/rockchip/rockchip_lvds.c参考配置:
arch/arm64/boot/dts/rockchip/rk3368-sheep-lvds.dts文档：
Documentation/devicetree/bindings/video/rockchip-lvds.txt:
Required properties:
compatible: matching the soc type, one of
reg: physical base address of the controller and length
of memory mapped region.
reg-names: the name to indicate register. example:
clocks: must include clock specifiers corresponding to entries in the
clock-names property.
clock-names: must contain “pclk_lvds”
avdd1v0-supply: regulator phandle for 1.0V analog power
avdd1v8-supply: regulator phandle for 1.8V analog power
avdd3v3-supply: regulator phandle for 3.3V analog power
rockchip,grf: phandle to the general register files syscon
rockchip,data-mapping: should be “vesa” or “jeida”,
This describes how the color bits are laid out in the
serialized LVDS signal.
rockchip,data-width : should be <18> or <24>;
rockchip,output: should be “rgb”, “lvds” or “duallvds”,
This describes the output face.
Optional properties
Required nodes:
The lvds has two video ports as described by
Documentation/devicetree/bindings/media/video-interfaces.txt.
Their connections are modeled using the OF graph bindings specified in
Documentation/devicetree/bindings/graph.txt.
Example:
For Rockchip RK3288:
lvds: lvds@ff96c000 {
compatible = "rockchip,rk3288-lvds";
rockchip,grf = <&grf>;
reg = <0xff96c000 0x4000>;
clocks = <&cru PCLK_LVDS_PHY>;
clock-names = "pclk_lvds";
avdd1v0-supply = <&vdd10_lcd>;
avdd1v8-supply = <&vcc18_lcd>;
avdd3v3-supply = <&vcca_33>;
rockchip,data-mapping = "jeida";
rockchip,data-width = <24>;
rockchip,output = "rgb";
ports {
#address-cells = <1>;
#size-cells = <0>;
lvds_in: port@0 {
reg = <0>;
lvds_in_vopb: endpoint@0 {
reg = <0>;
remote-endpoint = <&vopb_out_lvds>;
};
lvds_in_vopl: endpoint@1 {
reg = <1>;
remote-endpoint = <&vopl_out_lvds>;
};
};
lvds_out: port@1 {
reg = <1>;
lvds_out_panel: endpoint {
remote-endpoint = <&panel_in>;
};
};
};
};
For Rockchip RK3368:
lvds: lvds@ff968000 {
compatible = "rockchip,rk33xx-lvds";
reg = <0x0 0xff968000 0x0 0x4000>, <0x0 0xff9600a0 0x0 0x20>;
reg-names = "mipi_lvds_phy", "mipi_lvds_ctl";
clocks = <&cru PCLK_DPHYTX0>, <&cru PCLK_MIPI_DSI0>;
clock-names = "pclk_lvds", "pclk_lvds_ctl";
power-domains = <&power RK3368_PD_VIO>;
rockchip,grf = <&grf>;
pinctrl-names = "lcdc", "gpio";
pinctrl-0 = <&lcdc_lcdc>;
pinctrl-1 = <&lcdc_gpio>;
ports {
...
};
};</code></pre></div><h2 id="h_534267979_19" data-into-catalog-status="">5.开机LOGO配置</h2><p data-pid="Ip-ervB7">参考配置: arch/arm64/boot/dts/rockchip/rk3399-android.dtsi</p><h3 id="h_534267979_20" data-into-catalog-status="">5.1DeviceTree 解析:</h3><div class="highlight"><pre><code class="language-text">reserved-memory {
//在reserved memory划一块内存做为logo使用
drm_logo: drm-logo@00000000 {
compatible = "rockchip,drm-logo";
//size填0, uboot将会根据实际logo占用buffer的大小分配
//用户无需填写
reg = <0x0 0x0 0x0 0x0>;
};
};
&display_subsystem {
//drm驱动将解析drm_logo的buffer, 用于logo显示
memory-region = <&drm_logo>;
route {
//每一组route_xxx代表一路显示输出
route_hdmi: route-hdmi {
//在uboot loader阶段所使用的图片, 名称可根据resource.img打包的logo图片名称定义.
//当该属性留空或者指定的图片找不到时, uboot将不显示
logo,uboot = "logo.bmp";
//在uboot loader阶段所使用的图片, 名称可根据resource.img打包的logo图片名称定义.
//当该属性留空或者指定的图片找不到时, uboot将不显示
logo,kernel = "logo_kernel.bmp";
//支持两种显示模式: "fullscreen"全屏和"center'居中
logo,mode = "fullscreen";
//充电logo, 支持两种显示模式: "fullscreen"全屏和"center'居中
charge_logo,mode = "center";
//指定具体的显示通路, 如下, 为hdmi使用vopb输出
connect = <&vopb_out_hdmi>;
};
route_mipi: route-mipi {
logo,uboot = "logo_mipi.bmp";
logo,kernel = "logo_kernel_mipi.bmp";
logo,mode = "fullscreen";
charge_logo,mode = "center";
connect = <&vopb_out_mipi>;
};
route_edp: route-edp {
logo,uboot = "logo_edp.bmp";
logo,kernel = "logo_kernel_edp.bmp";
logo,mode = "fullscreen";
charge_logo,mode = "center";
connect = <&vopb_out_edp>;
};
};
};
arch/arm64/boot/dts/rockchip/rk3399-android.dtsi
两路输出显示不同的内容:
如下, route_hdmi使用logo_hdmi.bmp, route_mipi使用logo_mipi.bmp
&display_subsystem {
route {
route_hdmi: route-hdmi {logo,uboot = "logo_hdmi.bmp"; logo,kernel = "logo_kernel_hdmi.bmp"; connect = <&vopl_out_hdmi>; }; route_mipi: route-mipi { logo,uboot = "logo_mipi.bmp"; logo,kernel = "logo_kernel_mipi.bmp"; logo,mode = "fullscreen"; charge_logo,mode = "center"; connect = <&vopb_out_mipi>; }; };
};
hdmi和mipi就将显示不同的图片内容.
两路输出同时显示:
不同route使用不同的vop即可实现显示的独立. 例如:
route_hdmi的connect配置成vopl_out_hdmi,
route_mipi的connect配置成vopb_out_hdmihdmi和edp就将使用不同的vop独立显示
&display_subsystem {
route {
route_hdmi: route-hdmi {
connect = <&vopb_out_hdmi>;
};route_mipi: route-mipi { connect = <&vopb_out_mipi>; }; route_edp: route-edp { connect = <&vopl_out_edp>; };
};
};
抢占：
oute的节点是有顺序优先关系的, 如上, route_hdmi在route_mipi之前, 且它们都使用vopb做为显示输出, 当hdmi和mipi同接入时, hdmi会先将vopb抢走, 这样mipi就分配不到vop了, 现象为: hdmi显示, mipi不显示。
热拔插
如上抢占内容可知, 当hdmi插入时, 现象为hdmi显示, mipi不显
但当hdmi处于拔出状态时, route_hdmi这一路将不会工作, 也即可以实现: hdmi不显示, mipi显示.
由此实现同一配置, 插入hdmi和拔出hdmi启动过程通路状态不同.
| 格式 | 生成方式 |
|---|---|
| 8bit rle8 bmp | convert -compress rle -colors 256 logo_old.bmp logo_new.bmp |
| 24 bit bmp | 非压缩 |
| 32 bit bmp | 非压缩 |
command：
cat /sys/kernel/debug/dri/0/summary打印信息：
vop name: ff900000.vop status=active
Display mode: 1280x1024 fps[75] clk[135000] type[64] flag[5]
H: 1280 1296 1440 1688
V: 1024 1025 1028 1066
win0-0: status=disabled
win1-0: status=disabled
win2-0: status=active
format: AB24 little-endian (0x34324241)
zpos: 0
src: pos[0x0] rect[1280x1024]
dst: pos[0x0] rect[1280x1024]
buf[0]: addr: 0x000000000370e000 pitch: 5120 offset: 0
win2-0: status=disabled
win2-1: status=disabled
win2-2: status=disabled
win3-0: status=disabled
win3-0: status=disabled
win3-1: status=disabled
win3-2: status=disabled
vop name: ff8f0000.vop status=disabled命令：
cat /sys/kernel/debug/dri/0/mm_dump打印信息：
0x0000000000000000-0x00000000004f2000: 5185536: used
0x00000000004f2000-0x0000000000d0a000: 8486912: used
0x0000000000d0a000-0x0000000001522000: 8486912: used
0x0000000001522000-0x0000000001d0b000: 8294400: used
0x0000000001d0b000-0x00000000024f4000: 8294400: used
0x00000000024f4000-0x0000000002d0c000: 8486912: used
0x0000000002d0c000-0x0000000002d0d000: 4096: used
0x0000000002d0d000-0x0000000002d0e000: 4096: used
0x0000000002d0e000-0x000000000320e000: 5242880: used
0x000000000320e000-0x000000000370e000: 5242880: used
0x000000000370e000-0x0000000003c0e000: 5242880: used
0x0000000003c0e000-0x0000000003d52000: 1327104: used
0x0000000003d52000-0x0000000004d24000: 16588800: free
0x0000000004d24000-0x000000000550d000: 8294400: used
0x000000000550d000-0x0000000005cf6000: 8294400: used
0x0000000005cf6000-0x00000000064df000: 8294400: free
0x00000000064df000-0x00000000080ff000: 29491200: used
0x00000000080ff000-0x0000000008101000: 8192: used
0x0000000008101000-0x00000000088ea000: 8294400: used
0x00000000088ea000-0x00000000090d3000: 8294400: used
0x00000000090d3000-0x00000000098bc000: 8294400: used
0x00000000098bc000-0x000000000a0a5000: 8294400: used
0x000000000a0a5000-0x0000000100000000: 4126519296: free
total: 4294967296, used 143564800 free 4151402496modetest是libdrm源码自带的调试工具, 可以对drm进行一些基础的调试.
android平台:
mmm external/libdrm/testslinux平台 - ARM64
git clone git://anongit.freedesktop.org/mesa/drm && cd drm
//ARM64
CC=aarch64-linux-gnu-gcc ./autogen.sh --host=aarch64-linux --disable-freedreno --disable-cairo-tests --enable-install-test-programs
//ARM32
CC=arm-linux-gnueabihf-gcc ./autogen.sh --host=arm-linux --disable-freedreno --disable-cairo-tests --enable-install-test-programs
make -j4 && make install DESTDIR=pwd/outmodetest帮助信息:
(shell)# modetest -h
usage: modetest [-cDdefMPpsCvw]
Query options:
-c list connectors
-e list encoders
-f list framebuffers
-p list CRTCs and planes (pipes)
Test options:
-P <crtc_id>:<w>x<h>[+<x>+<y>][*<scale>][@<format>] set a plane
-s <connector_id>[,<connector_id>][@<crtc_id>]:<mode>[-<vrefresh>][@<format>] set a mode
-C test hw cursor
-v test vsynced page flipping
-w <obj_id>:<prop_name>:<value> set property
Generic options:
-d drop master after mode set
-M module use the given driver
-D device use the given device
Default is to dump all info.使用案例:
modetest不带参(有非常多的打印,这边截取部分关键的):
//由于rockchip driver的一些配置未upstream到libdrm上, 所以从libdrm upstream
//下载编译的modetest默认不带rockchip支持, 需要在使用的时候加个-M rockchip.
(shell)# modetest -M rockchip
Encoders:
id crtc type possible crtcs possible clones
71 27 TMDS 0x00000001 0x00000000
73 0 TMDS 0x00000002 0x00000000
Connectors:
id encoder status name size (mm) modes encoders
72 71 connected HDMI-A-1 410x260 19 71
modes:
name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot)
1440x900 60 1440 1520 1672 1904 900 903 909 934 flags: nhsync, pvsync; type: preferred, driver
1280x1024 75 1280 1296 1440 1688 1024 1025 1028 1066 flags: phsync, pvsync; type: driver
[…]
74 0 disconnected DP-1 0x0 0 73
CRTCs:
id fb pos size
27 0 (0,0) (1280x1024)
64 0 (0,0) (0x0)
Planes:
id crtc fb CRTC x,y x,y gamma size possible crtcs
23 0 0 0,0 0,0 0 0x00000001
[…]如上modetest -M rockchip的信息,我们知道当前系统有两个vop, 有两个输出设备:
测试显示输出: 测试显示输出时要把当前系统其他的显示关掉, 因为drm只能允许一个显示输出程序.
android: adb shell stop
linux ubuntu: service lightdm stop显示输出命令
(shell)# modetest -M rockchip -s 72@27:1440x900 -v
setting mode 1440x900-60Hz@XR24 on connectors 72, crtc 27
freq: 60.53Hz
屏幕上即可看到闪烁的彩条显示,
如需使用dp输出,将命令中的connector的id换成dp的即可.
如需使用另一个crtc输出, 将命令中的crtc的id换成另一个crtc的id即可
如需使用别的分辨率输出, 将命令中1440x900换成connectors modes里面别的分辨率即可
sys结点位置: /sys/module/drm/parameters/debugdebug:Enable debug output, where each bit enables a debug category.
Bit 0 (0x01) will enable CORE messages (drm core code)
Bit 1 (0x02) will enable DRIVER messages (drm controller code)
Bit 2 (0x04) will enable KMS messages (modesetting code)
Bit 3 (0x08) will enable PRIME messages (prime code)
Bit 4 (0x10) will enable ATOMIC messages (atomic code)
Bit 5 (0x20) will enable VBL messages (vblank code) (int)
示例: echo 0x0c > /sys/module/drm/parameters/debug
打开了KMS, PRIME这些的打印, kernel驱动中使用DRM_DEBUG_KMS和
DRM_DEBUG_PRIME打印的信息都可以打印出来
查看显示时钟:
(shell)# cat /sys/kernel/debug/clk/clk_summary | grep vop
dclk_vop0 2 2 135000000 0 0
dclk_vop1 0 1 0 0 0
aclk_vop0 2 3 594000000 0 0
aclk_vop1 0 2 594000000 0 0
hclk_vop0 2 3 198000000 0 0
hclk_vop1 0 2 198000000 0 0需要关注的显示时钟为:
dclk_vop:
即pixel clock, 像素时钟, 该时钟由具体的显示timing决定, 如果dclk不正确, 可能导致fps不对或直接不显示. edp, mipi, lvds等显示接口对应dclk的容忍性较好, 有些偏差也不影响正常显示. 但hdmi, dp等高清显示接口, 是有严格要求的, 这类显示接口的频率要给的很精准.
aclk_vop:
如果该时钟频率太低, 可能会导致显示出现抖动, 另外如果aclk 没有使能的话, 访问vop的寄存器也可能引发总线挂死
hclk_vop:
如果该时钟未使能, 不能访问vop的寄存器, 一但访问vop寄存器, 会造成总线挂死.
(shell)# cat /sys/kernel/debug/gpio
GPIOs 0-31, platform/pinctrl, gpio0:
GPIOs 32-63, platform/pinctrl, gpio1:
GPIOs 64-95, platform/pinctrl, gpio2:
gpio-90 ( |bt_default_wake ) out hi
GPIOs 96-127, platform/pinctrl, gpio3:
gpio-98 ( |enable ) out hi
gpio-111 ( |mdio-reset ) out hi
GPIOs 128-159, platform/pinctrl, gpio4:
drm panel驱动默认使用enable做为屏的gpio使能脚, 所以这边重点看一下enable的状态, 是否与预期的一致.
不管hdmi接没接， 强行使能hdmi
echo on > /sys/devices/platform/display-subsystem/drm/card0/card0-HDMI-A-1/status关闭hdmi
echo off > /sys/devices/platform/display-subsystem/drm/card0/card0-HDMI-A-1/status监测hdmi插拔，正常情况以就是在这个状态
echo detect > /sys/devices/platform/display-subsystem/drm/card0/card0-HDMI-A-1/status