Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Command Stream Format
The adreno GPU traces it's lineage back to ATI's Imageon line of mobile GPUs intended for SoC application. As such, it shares some similarities with the Radeon GPUs. In particular, the CP (command processor) appears to be identical. However, none of the op-codes or register addresses appear to the same.
Note that the basic packet format (described in this page) is same for a3xx and a2xx although all the registers and some of the packet types differ.
The canonical register level reference is the rnndb database. All known registers and bitfields for a2xx and a3xx (and display controller related blocks) are added there, and the register accessor headers used by kernel, gallium driver, etc, are generated from these xml files. Various parsing tools (demsm for parsing kernel register access traces, and cffdump for parsing cmdstream traces) also use the rnndb database.
Command Processor (CP)
This is the easiest part, as it is identical to radeon. The CP is the block that reads a series of rendering commands from a ringbuffer (the PM4 command stream) and either sets some register values or triggers some rendering action. It consists primarily of Type-0 (PKT0) and Type-3 (PKT3) commands
Writes N consecutive (32bit) dwords to N registers, starting with the register specified by
Perform the operation specified by
A few common actions are:
CP_SET_CONSTANT:0x2d- performs basically the same thing as a
0x00040000 | (BASE_INDEX - 0x2000), and
DATA_nare N-1 register values
CP_INDIRECT_BUFFER:0x3f- branch to a 2nd cmdstream buffer
CP_DRAW_INDX:0x22- trigger drawing
Currently the best reference is util/cffdump.c, the commandstream parser, and fdre-a2xx/freedreno.c or fdre-a3xx/freedreno.c. Also see the renders page which has example renders and corresponding cmdstream parses from fdre.