CROSS REFERENCE TO RELATED APPLICATION(S)

[0001] This application claims the benefit of U.S. Provisional Application No. 63/166,956, filed March 26, 2021 and U.S. Non-Provisional Application No. 17/565,394, filed December 29, 2021, which are incorporated by reference as if fully set forth herein.

BACKGROUND

[0002] Graphics processing includes the rendering of a three dimensional

(3D) scene onto a two dimensional (2D) screen. The 3D scene is rendered on a display screen, via a graphics pipeline, which includes different stages of processing. Graphics processing commands of a command stream are received (e.g., from an application) and computation tasks are provided (e.g., to an accelerated processing device, such as a GPU) for execution of the tasks.

[0003] Graphics are rendered on a display screen using primitives (e.g., triangles, quadrilaterals or other geometric shapes). The graphics processing commands include, for example, the number of primitives, the location of each primitive and attributes of each primitive to be rendered on the display screen.

BRIEF DESCRIPTION OF THE DRAWINGS [0004] A more detailed understanding can be had from the following description, given by way of example in conjunction with the accompanying drawings wherein:

[0005] FIG. 1 is a block diagram of an example device in which one or more features of the disclosure can be implemented;

[0006] FIG. 2 is a block diagram of the device of FIG. 1, illustrating additional detail;

[0007] FIG. 3 is a block diagram illustrating a graphics processing pipeline, according to an example; [0008] FIG. 4 is a block diagram illustrating example components of an accelerated processing device in which one or more features of the disclosure can be implemented;

[0009] FIG. 5 is a diagram of a portion a graphics processing pipeline illustrating the ordering of different rendering subpasses according to an example; [0010] FIG. 6 shows timing diagrams illustrating the performance benefits of implementing an example of interleaving subpasses of consecutive bins;

[0011] FIG. 7 is a timing diagrams illustrating the example shown in FIG. 6 for 3 bins;

[0012] FIG. 8 is a diagram illustrating a first example mode of interleaving subpasses of consecutive bins;

[0013] FIG. 9 is a diagram illustrating a second example mode of interleaving subpasses of consecutive bins;

[0014] FIG. 10 is a timing diagram illustrating the second example mode shown in FIG. 9; and

[0015] FIG. 11 is a flow diagram illustrating an example method of tiled image rendering according to features of the disclosure.

DETAILED DESCRIPTION

[0016] The terms “tile,” “bin,” “tiled,” “binned,” “tiling” and binning are used interchangeably herein.

[0017] The graphics pipleline can be simplified to include a front end geometry portion and a back end portion. For example, the front end geometry portion of the pipeline includes several shader stages (e.g., vertex shader stage, hull shader stage, tesselator stage, domain shader stage and geometry shader stage). During the shader stages, the primitives are received as 3D objects and transformed to 2D objects to be rendered onto a 2D screen. The back end portion includes a rasterizer stage and pixel shader stage. During the rasterizer stage, an on-screen location of each primitive to be projected onto the 2D screen is determined. For example, during rasterization, an accelerated processing device (e.g., GPU) determines, for each primitive, which pixels (or sub-pixel samples) correspond to each primitive to be rendered onto the 2D screen. During the pixel shader stage, values (e.g., brightness and color) are calculated for the pixels corresponding to the primitives.

[0018] Rendering a frame includes performing different tasks in a particular order. For example, frame rendering includes shadow rendering, a render pass and post processing. The render pass includes various subpasses (e.g., visibility subpasses) performed in a particular order. A subpass is a sequence of draw commands that render to the same render target.

[0019] The commands (i.e., instructions) for subpasses are stored (e.g., in a command buffer) in a particular order and issued to the processor (e.g., scheduler of a GPU) in the particular order in the buffer because, in some cases, subsequent subpasses depend on the output data from a previous subpass before executing. The data resulting from the execution of each subpasss is typically stored in a cache (e.g., a render backend (RB) cache). Execution of a subsequent task, however, relies on reading the data from another portion of memory (i.e., not from the RB cache). Therefore, the data from the RB cache is flushed and stored in another portion of memory, such as a lower level cache (e.g., level 2 (L2) cache or other lower level cache) or main memory so that the data can be read to execute the subsequent task.

[0020] A subsequently ordered subpass in the command buffer depends on the data resulting from a previously ordered subpass Before a subsequently ordered subpass in the command buffer can begin executing (i.e., before any work can begin by the subsequently ordered subpass), the previously ordered subpass in the command buffer must finish executing (i.e., the output data is flushed from the cache and the data is stored in another portion of memory). Accordingly, in this case, when a subsequently ordered subpass has to wait for a previously ordered subpass to complete, overhead (e.g., latency) is introduced in the processing pipeline. In addition, during this waiting period, the processor is idle until the previously ordered subpass completes, resulting in inefficiencies in the pipeline and increased frame latency.

[0021] Tiling (or binning) is a technique which splits a frame into sections (e.g., tiles or bins) and renders one tile of a frame before rendering another tile of the frame. For example, if a frame (or image) is split into four equal tiles (i.e., top left quadrant, top right quadrant, bottom left quadrant and bottom right quadrant), a first tile (e.g., top left quadrant) is rendered before proceeding to render one of the next tiles. Then, one of the other tiles (e.g., top right quadrant) is rendered before proceeding to render one of the last two tiles, and so on, until each of the tiles of the frame are rendered.

[0022] In conventional tiled (binned) rendering, each of the bins are rendered independent of each other. When rendering a tile (or bin), different subpasses of the same tile (or bin) must execute in the order specified in the command buffer so that a subsequently ordered subpass of the same tile can read the data resulting from the execution of the previously ordered subpass. Accordingly, because a subsequently ordered subpass of a tile must wait for the previously ordered subpass of the same tile to complete, the latency is introduced in the processing pipeline.

[0023] The present application discloses apparatuses and methods which exploit these attributes of tiled (binned) rendering and provide a more efficient processing pipeline by interleaving same subpasses of multiple bins (e.g., a first lighting subpass of bin 1 and a same first lighting subpass of bin 2). Features of the present application interleave the execution of a same subpass (i.e., same subpass type) of a different tile during the time period when a subsequently ordered subpass (different from a previously ordered subpass) of a same tile is waiting for the previously ordered subpass of the same tile to complete. Accordingly, because these time periods, during which subsequently ordered subpasses of a same tile are waiting, are used to execute one or more subpasses of a different tile, the overall latency is reduced. In addition, because the processor is executing one or more subpasses of a different tile during this time period in which the subsequently ordered subpass of a same tile is waiting, the processor is not idle during this time period, resulting in a more efficient use of resources. In addition, features of the present application also utilize the ability to process subpasses in parallel, via an accelerated processing device (e.g., GPU), by overlapping (in time) the execution of same subpasses of different bins to further reduce the latency. [0024] In one example mode, subpasses of consecutive bins are interleaved by executing the subpasses in an order different from the order in which the subpass commands are stored (e.g., in a command buffer) and issued to the processor (e.g., scheduler of a GPU). In another example mode, subpasses of consecutive bins are interleaved by executing subpasses as skip operations such that the subpasses are executed in the same order in which the subpass commands are stored and issued to the processor. The interleaving mode to be implemented and the number of interleaved same subpasses of multiple bins are determined on a per frame basis or multiple frame basis prior to rendering a frame.

[0025] A method of tiled image rendering is provided which comprises dividing a frame to be rendered, into a plurality of tiles, receiving commands to execute a plurality of subpasses of the tiles and interleaving execution of same subpasses of multiple tiles of the frame.

[0026] A processing device used for tiled image rendering is provided which comprises memory and a processor. The processor is configured to: divide a frame to be rendered into a plurality of tiles, receive commands to execute a plurality of subpasses of the tiles; and interleave execution of same subpasses of multiple tiles of the frame.

[0027] A non-transitory computer readable medium is provided which comprises instructions for causing a computer to execute a method of tiled image rendering. The instructions comprise dividing a frame to be rendered, into a plurality of tiles, receiving commands to execute a plurality of subpasses of the tiles and interleaving execution of same subpasses of multiple tiles of the frame. [0028] FIG. 1 is a block diagram of an example device 100 in which one or more features of the disclosure can be implemented. The device 100 can include, for example, a computer, a gaming device, a handheld device, a set-top box, a television, a mobile phone, or a tablet computer. The device 100 includes a processor 102, a memory 104, a storage 106, one or more input devices 108, and one or more output devices 110. The device 100 can also optionally include an input driver 112 and an output driver 114. It is understood that the device 100 can include additional components not shown in FIG. 1. [0029] In various alternatives, the processor 102 includes a central processing unit (CPU), a graphics processing unit (GPU), a CPU and GPU located on the same die, or one or more processor cores, wherein each processor core can be a CPU or a GPU. In various alternatives, the memory 104 is located on the same die as the processor 102, or is located separately from the processor 102. The memory 104 includes a volatile or non-volatile memory, for example, random access memory (RAM), dynamic RAM, or a cache.

[0030] The storage 106 includes a fixed or removable storage, for example, a hard disk drive, a solid state drive, an optical disk, or a flash drive. The input devices 108 include, without limitation, a keyboard, a keypad, a touch screen, a touch pad, a detector, a microphone, an accelerometer, a gyroscope, a biometric scanner, or a network connection (e.g., a wireless local area network card for transmission and/or reception of wireless IEEE 802 signals). The output devices 110 include, without limitation, a display, a speaker, a printer, a haptic feedback device, one or more lights, an antenna, or a network connection (e.g., a wireless local area network card for transmission and/or reception of wireless IEEE 802 signals).

[0031] The input driver 112 communicates with the processor 102 and the input devices 108, and permits the processor 102 to receive input from the input devices 108. The output driver 114 communicates with the processor 102 and the output devices 110, and permits the processor 102 to send output to the output devices 110. It is noted that the input driver 112 and the output driver 114 are optional components, and that the device 100 will operate in the same manner if the input driver 112 and the output driver 114 are not present. The output driver 116 includes an accelerated processing device (“APD”) 116 which is coupled to a display device 118. The APD accepts compute commands and graphics rendering commands from processor 102, processes those compute and graphics rendering commands, and provides pixel output to display device 118 for display. As described in further detail below, the APD 116 includes one or more parallel processing units to perform computations in accordance with a single-instruction- multiple-data (“SIMD”) paradigm. Thus, although various functionality is described herein as being performed by or in conjunction with the APD 116, in various alternatives, the functionality described as being performed by the APD 116 is additionally or alternatively performed by other computing devices having similar capabilities that are not driven by a host processor (e.g., processor 102) and provides graphical output to a display device 118. For example, it is contemplated that any processing system that performs processing tasks in accordance with a SIMD paradigm may perform the functionality described herein. Alternatively, it is contemplated that computing systems that do not perform processing tasks in accordance with a SIMD paradigm performs the functionality described herein.

[0032] FIG. 2 is a block diagram of the device 100, illustrating additional details related to execution of processing tasks on the APD 116. The processor 102 maintains, in system memory 104, one or more control logic modules for execution by the processor 102. The control logic modules include an operating system 120, a kernel mode driver 122, and applications 126. These control logic modules control various features of the operation of the processor 102 and the APD 116. For example, the operating system 120 directly communicates with hardware and provides an interface to the hardware for other software executing on the processor 102. The kernel mode driver 122 controls operation of the APD 116 by, for example, providing an application programming interface (“API”) to software (e.g., applications 126) executing on the processor 102 to access various functionality of the APD 116. The kernel mode driver 122 also includes a just-in-time compiler that compiles programs for execution by processing components (such as the SIMD units 138 discussed in further detail below) of the APD 116.

[0033] The APD 116 executes commands and programs for selected functions, such as graphics operations and non-graphics operations that may be suited for parallel processing. The APD 116 can be used for executing graphics pipeline operations such as pixel operations, geometric computations, and rendering an image to display device 118 based on commands received from the processor 102. The APD 116 also executes compute processing operations that are not directly related to graphics operations, such as operations related to video, physics simulations, computational fluid dynamics, or other tasks, based on commands received from the processor 102. [0034] The APD 116 includes compute units 132 that include one or more SIMD units 138 that perform operations at the request of the processor 102 in a parallel manner according to a SIMD paradigm. The SIMD paradigm is one in which multiple processing elements share a single program control flow unit and program counter and thus execute the same program but are able to execute that program with different data. In one example, each SIMD unit 138 includes sixteen lanes, where each lane executes the same instruction at the same time as the other lanes in the SIMD unit 138 but can execute that instruction with different data. Lanes can be switched off with predication if not all lanes need to execute a given instruction. Predication can also be used to execute programs with divergent control flow. More specifically, for programs with conditional branches or other instructions where control flow is based on calculations performed by an individual lane, predication of lanes corresponding to control flow paths not currently being executed, and serial execution of different control flow paths allows for arbitrary control flow.

[0035] The basic unit of execution in compute units 132 is a work-item. Each work-item represents a single instantiation of a program that is to be executed in parallel in a particular lane. Work-items can be executed simultaneously as a “wavefront” on a single SIMD processing unit 138. One or more wavefronts are included in a “work group,” which includes a collection of work-items designated to execute the same program. A work group can be executed by executing each of the wavefronts that make up the work group. In alternatives, the wavefronts are executed sequentially on a single SIMD unit 138 or partially or fully in parallel on different SIMD units 138. Wavefronts can be thought of as the largest collection of work-items that can be executed simultaneously on a single SIMD unit 138. Thus, if commands received from the processor 102 indicate that a particular program is to be parallelized to such a degree that the program cannot execute on a single SIMD unit 138 simultaneously, then that program is broken up into wavefronts which are parallelized on two or more SIMD units 138 or serialized on the same SIMD unit 138 (or both parallelized and serialized as needed). A scheduler 136 performs operations related to scheduling various wavefronts on different compute units 132 and SIMD units 138. [0036] The parallelism afforded by the compute units 132 is suitable for graphics related operations such as pixel value calculations, vertex transformations, and other graphics operations. Thus in some instances, a graphics pipeline 134, which accepts graphics processing commands from the processor 102, provides computation tasks to the compute units 132 for execution in parallel.

[0037] The compute units 132 are also used to perform computation tasks not related to graphics or not performed as part of the “normal” operation of a graphics pipeline 134 (e.g., custom operations performed to supplement processing performed for operation of the graphics pipeline 134). An application 126 or other software executing on the processor 102 transmits programs that define such computation tasks to the APD 116 for execution.

[0038] The APD 116 is configured to implement features of the present disclosure by executing a plurality of functions. For example, the APD 116 is configured to receive images (i.e., frames), divide images into a plurality of tiles, receive subpass commands, via user mode driver 200, interleave same subpasses of multiple bins by executing the subpasses in an order different from the order in which the subpass commands are stored and issued to the processor, interleave same subpasses of multiple bins by skipping execution of subpasses such that the subpasses are executed in the same order in which the subpass commands are stored and issued to the processor, determining an interleaving mode and a number of interleaved same subpasses of multiple bins on a per frame basis or multiple frame basis prior to rendering a frame.

[0039] FIG. 3 is a block diagram showing additional details of the graphics processing pipeline 134 illustrated in FIG. 2. The graphics processing pipeline 134 includes stages that each performs specific functionality. The stages represent subdivisions of functionality of the graphics processing pipeline 134. Each stage is implemented partially or fully as shader programs executing in the programmable processing units 202, or partially or fully as fixed-function, non programmable hardware external to the programmable processing units 202. [0040] Stages 302 to 313 represent the front end geometry processing portion of the graphics processing pipeline 134. Stages 314 to 318 represent the back end pixel processing portion of the graphics processing pipeline 134.

[0041] The input assembler stage 302 reads primitive data from user-filled buffers (e.g., buffers filled at the request of software executed by the processor 102, such as an application 126) and assembles the data into primitives for use by the remainder of the pipeline. The input assembler stage 302 can generate different types of primitives based on the primitive data included in the user-filled buffers. The input assembler stage 302 formats the assembled primitives for use by the rest of the pipeline.

[0042] The vertex shader stage 304 processes vertexes of the primitives assembled by the input assembler stage 302. The vertex shader stage 304 performs various per-vertex operations such as transformations, skinning, morphing, and per-vertex lighting. Transformation operations include various operations to transform the coordinates of the vertices. These operations include one or more of modeling transformations, viewing transformations, projection transformations, perspective division, and viewport transformations. Herein, such transformations are considered to modify the coordinates or “position” of the vertices on which the transforms are performed. Other operations of the vertex shader stage 304 modify attributes other than the coordinates.

[0043] The vertex shader stage 304 is implemented partially or fully as vertex shader programs to be executed on one or more compute units 132. The vertex shader programs are provided by the processor 102 and are based on programs that are pre-written by a computer programmer. The driver 122 compiles such computer programs to generate the vertex shader programs having a format suitable for execution within the compute units 132.

[0044] The hull shader stage 306, tessellator stage 308, and domain shader stage 310 work together to implement tessellation, which converts simple primitives into more complex primitives by subdividing the primitives. The hull shader stage 306 generates a patch for the tessellation based on an input primitive. The tessellator stage 308 generates a set of samples for the patch. The domain shader stage 310 calculates vertex positions for the vertices corresponding to the samples for the patch. The hull shader stage 306 and domain shader stage 310 can be implemented as shader programs to be executed on the programmable processing units 202.

[0045] The geometry shader stage 312 performs vertex operations on a primitive-by-primitive basis. A variety of different types of operations can be performed by the geometry shader stage 312, including operations such as point sprint expansion, dynamic particle system operations, fur-fin generation, shadow volume generation, single pass render-to-cubemap, per-primitive material swapping, and per-primitive material setup. In some instances, a shader program that executes on the programmable processing units 202 perform operations for the geometry shader stage 312.

[0046] The binner stage 313 is the last stage of the front end processing. The binner stage performs a coarse rasterization to determine if a tile (or bin) of the frame (or image) overlaps with primitives. For example, the binner stage includes visibility checking (i.e., a visibility pass) and tile walking for the primitives determined to be in each tile. The binner stage 313 is performed by fixed function hardware.

[0047] As described above, stages 314-318 represent the back end processing of the graphics processing pipeline 134. The rasterizer stage 314 accepts and rasterizes simple primitives and generated upstream. Rasterization includes determining which screen pixels (or sub-pixel samples) are covered by a particular primitive. For example, the rasterizer stage 314 converts the primitive (e.g., a triangle) to screen space pixels, testing which pixel is covered by the primitive. Rasterization is performed by fixed function hardware.

[0048] The pixel shader stage 316 calculates output values for screen pixels based on the primitives generated upstream and the results of rasterization. The pixel shader stage 316 may apply textures from texture memory. Operations for the pixel shader stage 316 are performed by a shader program that executes on the programmable processing units 202.

[0049] The output merger stage 318 accepts output from the pixel shader stage 316 and merges those outputs, performing operations such as z-testing and alpha blending to determine the final color for a screen pixel. [0050] Texture data, which defines textures, are stored and/or accessed by the texture unit 320. Textures are bitmap images that are used at various points in the graphics processing pipeline 134. For example, in some instances, the pixel shader stage 316 applies textures to pixels to improve apparent rendering complexity (e.g., to provide a more “photorealistic” look) without increasing the number of vertices to be rendered.

[0051] In some instances, the vertex shader stage 304 uses texture data from the texture unit 320 to modify primitives to increase complexity, by, for example, creating or modifying vertices for improved aesthetics. In one example, the vertex shader stage 304 uses a height map stored in the texture unit 320 to modify displacement of vertices. This type of technique can be used, for example, to generate more realistic looking water as compared with textures only being used in the pixel shader stage 316, by modifying the position and number of vertices used to render the water. In some instances, the geometry shader stage 312 accesses texture data from the texture unit 320.

[0052] FIG. 4 is a block diagram illustrating example components of the APD 116 shown in FIG. 2 in which one or more features of the disclosure can be implemented. As shown in FIG. 4, the APD 116 includes compute units 132, each having an LI cache. Each compute unit communicates with rendering back end (RB) which is implemented via fixed function hardware. The output data resulting from the execution of subpasses (e.g., subpass 0, subpass 1 and subpass 2 shown in FIG. 5) is stored in the RB cache. The output data from a previously ordered subpass is flushed from the RB cache and provided to another portion of memory, such as L2 cache 406 shown in FIG. 4, and the data is read by the subsequently ordered subpass for execution.

[0053] FIG. 5 is a diagram of a portion a graphics processing pipeline illustrating the ordering of different rendering subpasses according to an example. The frame rendering includes shadow rendering 502, a render pass 504 and post processing 506. For simplified explanation purposes, the render pass 504 in the example shown in FIG. 5 includes three subpasses, namely a geometry buffer (GBuffer) rendering subpass (i.e., subpass 0), a first lighting (light 1) subpass (i.e., subpass 1) and a second lighting subpass (i.e., subpass 2). The number of subpasses and the types of subpasses shown in FIG. 5 is merely an example. Features of the disclosure can be implemented using different numbers of subpasses and different types of subpasses different from those shown in FIG. 5. [0054] As described above, before a subsequently ordered subpass (e.g., subpass 1 in FIG. 5) in the command buffer can begin executing (i.e., before any work can begin by the subsequently ordered subpass), a previously ordered subpass (e.g., subpass 0 in FIG. 5) in the command buffer must finish executing (i.e., the output data is flushed from the cache and the data is stored in another portion of memory). Accordingly, when subpass 1 has to wait for subpass 0 to complete, overhead (e.g., latency) is introduced in the processing pipeline. In addition, during this waiting period, the processor is idle until subpass 0 completes, resulting in inefficiencies in the pipeline and increased frame latency. FIG. 6 shows timing diagrams illustrating the performance benefits of implementing an example of interleaving subpasses of consecutive bins. In particular, FIG. 6 illustrates the performance benefits (e.g., decreased latency) between the execution of two different subpasses of consecutive bins without interleaving and execution by interleaving the two different subpasses of the consecutive bins. Two subpasses and two bins are illustrated in FIG. 6 for simplified explanation. Features of the disclosure can be implemented using more than two subpasses and more than two bins.

[0055] The timing diagram at the top portion of FIG. 6 illustrates execution of two different subpasses (i.e., Pass 1 and Pass 2) of two consecutive bins (i.e., bin 1 and bin 2) without interleaving. The timing diagram at the bottom portion of FIG. 6 illustrates interleaving the two different subpasses (i.e., Pass 1 and Pass 2) of bins 1 and 2 according to features of the present disclosure. For simplified explanation purposes, each of the example subpasses shown in FIG. 6 include 3 stages (i.e., a vertex shader (VS) stage, a pixel shader (PS) stage and an RB stage of a processing pipeline. Pipelines can, however, include additional or other stages, such as for example, the stages shown in pipeline 134 shown in FIG. 3.

[0056] As shown at the top portion of FIG. 6, a first subpass Pass 1 (i.e., a subpass of a first type, such as geometry buffer rendering subpass 0 in FIG. 5) is executed for bin 1, followed by execution of a second subpass Pass 2 (i.e., a subpass of a different second type, such as first lighting subpass 1 in FIG. 5) of bin 1. Then, the first subpass Pass 1 is executed for bin 2, followed by execution of the second subpass Pass 2 for bin 2.

[0057]

[0058] The curved arrows, extending from RB stages of Pass 1 to PS stages of Pass 2 in FIG. 6, indicate that the execution of the PS stage of a subsequently ordered subpass is dependent on the data resulting from the RB stage in a previously ordered subpass and a cache (e.g., the RB cache) being flushed (i.e., invalidated (INV)). That is, as shown at the top portion of FIG. 6, the subsequently ordered subpass (Pass 2) must wait for the previously ordered subpass (Pass 1) to complete execution, creating a latency in the pipeline. In addition, during this waiting period, the processor is idle which is a waste of resources.

[0059] As show in the bottom portion of FIG. 6, however, execution of the previously ordered subpass (i.e., Pass 1) of bin 2 is interleaved between the execution of the same previously ordered subpass (i.e., Pass 1) of bin 1 and the execution of the subsequently ordered subpass (Pass 2) of bin 1. Accordingly, the time period in which no subpass is executed and the processor is idle in the top portion of FIG. 6 is utilized by execution of the previously ordered subpass (i.e., Pass 1) of bin 2, decreasing the latency and improving the overall performance. In addition, as shown in the bottom portion of FIG. 6, latency is further reduced by overlapping (in time) a portion of the execution of the previously ordered subpass (i.e., Pass 1) of bin 1 and portion of the execution of the previously ordered subpass (i.e., Pass 1) of bin 2.

[0060] FIG. 7 is a timing diagram illustrating the same procedure shown in the bottom portion of FIG. 6, but implemented using 3 passes for 3 bins. The number of bins and subpasses (shown as passes in FIGS. 6 and 7) are merely examples for simplified explanation purposes. Features of the present application can be implemented for any number of bins and any number of subpasses. In the example shown in FIG. 7, each of the first subpass (Pass 1), the second subpass (Pass 2) and the third subpass (Pass 3) are different from each other. For example, Pass 1 corresponds to a geometry buffer rendering subpass, Pass 2 corresponds to a first lighting subpass and Pass 3 corresponds to a second lighting subpass. Although not shown for simplified explanation, it can be appreciated that features of the present disclosure, including those described with regard to FIG. 7, can be implemented for additional subpasses (i.e., more than three subpasses).

[0061] As shown in both the timing diagram at the bottom portion of FIG. 6 and the timing diagram of FIG. 7, execution of the previously ordered first subpass (i.e., Pass 1) of bin 2 is interleaved between the execution of the same previously ordered first subpass (i.e., Pass 1) of bin 1 and the execution of the subsequently ordered second subpass (i.e., Pass 2) of bin 1. In addition, as shown in the timing diagram of FIG. 7, execution of the subsequently ordered second subpass (i.e., Pass 2) of bin 2 is interleaved between the execution of the same subsequently ordered second subpass (i.e., Pass 2) of bin 1 and the execution of a next subsequently ordered third subpass (Pass 3) of bin 1. Accordingly, a time period, in which the processor would otherwise be idle if interleaving was not used, is utilized to execute Pass 2 of bin 2 and further decrease the latency and improve the overall performance. In addition, as shown in the bottom portion of FIG. 6, latency is further reduced by overlapping (in time) a portion of the execution of Pass 2 of bin 1 and a portion of the execution of Pass 2 of bin 2. As can be appreciated, additional latency is decreased for each additional passes of a frame and for a plurality of frames, significantly improving the overall performance.

[0062] FIGS. 8-11 illustrate examples of different interleaving modes which can be implemented according to features of the present application. The number of bins, subpasses (shown as passes in FIGS. 8-10 and subpasses in FIG. 11) and commands shown in FIGS. 8-11 are merely examples for simplified explanation purposes. Features of the present application can be implemented for any number of bins and any number of subpasses using any number of commands.

[0063] FIG. 8 is a diagram illustrating a first example mode of interleaving subpasses of consecutive bins. With reference to FIG. 8, commands (i.e., command for pass 1, command for pass 2 and command for pass 3) which are issued to the scheduler 136 of APD 115 (e.g., GPU), via user mode driver 200, are stored in a command buffer 802 in a particular order to be executed. When rendering a tile (or bin), different subpasses of the same tile (or bin) are executed in the order specified in the command buffer 802 so that a subsequently ordered subpass of the same tile can read the data resulting from the execution of the previously ordered subpass.

[0064] As shown in FIG. 8, the execution of subpass 1 of bin 2 is interleaved between the execution of subpass 1 of bin 1 and subpass 2 of bin 1, during the time period when subpass 2 of bin 1 is waiting for subpass 1 of bin 1 to complete execution. In addition, the execution of subpass 2 of bin 2 is interleaved between the execution of subpass 2 of bin 1 and subpass 3 of bin 1, during the time period when subpass 3 of bin 1 is waiting for subpass 2 of bin 1 to complete execution. As can be appreciated, this process can be continued for additional passes and bins (not shown in FIG. 8).

[0065] In the example interleaving mode illustrated in FIG. 8, the execution order of the subpasses are different from the order specified in the command buffer 802. That is, the order specified in the command buffer 802 is subpass 1 (Pass 1), subpass 2 (Pass 2) and then subpass 3 (Pass 3), but the interleaving described above causes the execution of the subpasses 1-3 to be different from the order specified in the command buffer 802 (e.g., subpass 1 for Bin 1, followed by subpass 1 for Bin 2 and then subpass 2 for Bin 1).

[0066] Because these time periods, during which subsequently ordered subpasses of a same bin are waiting, are used to execute one or more subpasses of a different tile, the overall latency is reduced. In addition, because the processor is executing one or more subpasses of a different tile during this time period in which the subsequently ordered subpass of a same tile is waiting, the processor is not idle during this time period, resulting in a more efficient use of resources. [0067] FIGS. 9 and 10 are diagrams illustrating a second example mode of interleaving subpasses of consecutive bins. In the second example mode, subpasses of consecutive bins are interleaved by executing subpasses as skip operations such that the subpasses are executed in the same order specified in the command buffer 802.

[0068] In FIG. 9, the order of execution of each subpass (i.e., subpass 1, subpass 2 and subpass 3) is shown in matrix form (and aligned vertically with the commands in the command buffer 802 at the top of FIG. 9) to better illustrate that the subpasses are executed in the same order specified in the command buffer 802. The order in which the subpasses and skips are executed are indicated by corresponding numbers 1-12. For example, subpass 1 of Bin 1 is executed, subpasses 2 and 3 of Bin 1 are executed as a skip execution and then subpass 1 of Bin 2 is executed.

[0069] In FIG. 10, the order of execution of each subpass (i.e., subpass 1, subpass 2 and subpass 3) is shown horizontally, over time, to better illustrate the interleaving of the subpasses. In the second example mode shown in FIGS. 9-11, there is some latency caused by the skips. As shown in FIGS. 9 and 10, however, the number of skips (skip operations) decreases over time to no skips.

[0070] FIG. 11 is a flow diagram illustrating an example method 1100 of tiled image rendering according to features of the disclosure. As shown at block 1102 in FIG. 11, the method 1100 includes dividing a frame to be rendered, into a plurality of tiles. A frame to be rendered can be split into any number of tiles. Each tile of the frame is rendered before rendering another tile of the frame. For example, if a frame is split into four equal tiles (i.e., top left quadrant, top right quadrant, bottom left quadrant and bottom right quadrant), a first tile (e.g., top left quadrant) is rendered before proceeding to render one of the next tiles. Then, one of the other tiles (e.g., top right quadrant) is rendered before proceeding to render one of the last two tiles, and so on, until each of the tiles of the frame are rendered.

[0071] As shown at block 1104 in FIG. 11, the method 1100 includes receiving commands to execute a plurality of subpasses of the tiles. For example, commands to execute a plurality of subpasses (i.e., Pass 1, Pass 2 and Pass 3 shown in FIGS. 7 and 8) are received via command buffer 802 (shown in FIGS. 8 and 9) are issued to and received by the scheduler 136 of APD 115 (e.g., GPU) via user mode driver 200. The commands are stored in command buffer 802 in a particular order to be executed. When rendering a tile (or bin), different subpasses of the same tile (or bin) are executed in the order specified in the command buffer 802 so that a subsequently ordered subpass of the same tile can read the data resulting from the execution of the previously ordered subpass.

[0072] As shown at block 1106 in FIG. 11, the method 1100 includes interleaving execution of same subpasses of multiple tiles (e.g., a subpass of a first tile and a same subpass of a second tile) of the frame. For example, a previously ordered (e.g., order in the command buffer 802) first subpass of a second tile is executed between the execution of previously ordered first subpass of a first tile and execution of a subsequently ordered second subpass of the first tile.

[0073] The execution of same subpasses of multiple tiles is interleaved, for example, by executing the plurality of subpasses in an order different from the order in which the commands to execute the plurality of subpasses are stored and issued, Alternatively, execution of same subpasses of multiple tiles is interleaved by skipping execution of one or more subpasses such that the plurality of subpasses are executed in the same order in which the commands to execute the plurality of subpasses are stored and issued.

[0074] It should be understood that many variations are possible based on the disclosure herein. Although features and elements are described above in particular combinations, each feature or element can be used alone without the other features and elements or in various combinations with or without other features and elements.

[0075] The various functional units illustrated in the figures and/or described herein (including, but not limited to, the processor 102, the input driver 112, the input devices 108, the output driver 114, the output devices 110, the APD 116, the scheduler 136, the graphics processing pipeline 134, the compute units 132 and the SIMD units 138, maybe implemented as a general purpose computer, a processor, or a processor core, or as a program, software, or firmware, stored in a non-transitory computer readable medium or in another medium, executable by a general purpose computer, a processor, or a processor core. The methods provided can be implemented in a general purpose computer, a processor, or a processor core. Suitable processors include, by way of example, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), and/or a state machine. Such processors can be manufactured by configuring a manufacturing process using the results of processed hardware description language (HDL) instructions and other intermediary data including netlists (such instructions capable of being stored on a computer readable media). The results of such processing can be maskworks that are then used in a semiconductor manufacturing process to manufacture a processor which implements features of the disclosure.

[0076] The methods or flow charts provided herein can be implemented in a computer program, software, or firmware incorporated in a non-transitory computer-readable storage medium for execution by a general purpose computer or a processor. Examples of non-transitory computer-readable storage mediums include a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).