Backlight control system and MiniLED display
By using a multi-buffered backlight control system, the problems of memory overhead and response latency in MiniLED local dimming backlight systems are solved. This decouples memory space from the number of screen partitions, reduces system cost and backlight response latency, and meets the display requirements of high refresh rates.
Patent Information
- Application Number
- CN202611373795.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-04
- Publication Date
- 2026-11-10
AI Technical Summary
Existing MiniLED local dimming backlight systems suffer from extremely high memory overhead and backlight response latency, leading to increased system costs and image ghosting.
The backlight control system with multiple buffer blocks receives backlight control data serially, retrieves allocation information by looking up a preset mapping table based on the sequence number, stores the data in the target buffer block, and outputs it to the physical link when a preset threshold is reached, releasing the buffer block binding and decoupling the memory space from the number of screen partitions.
It significantly reduces the SRAM space occupied by the backlight controller, reduces the system's dependence on high-capacity memory, reduces backlight response latency, and meets the display requirements of high refresh rate and imperceptible latency.
Smart Images

Figure CN123072345A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of MiniLED control technology, and in particular to a backlight control system and a MiniLED display. Background Technology
[0002] In existing MiniLED local dimming backlight systems, the main mechanism employed is a "full-frame buffer & centralized repack" mechanism. The specific process is as follows: The backlight controller (BCON MCU) allocates a large full-frame buffer (Ping-Pong Buffer) in its internal static random access memory (SRAM) to store the brightness data sent by the main controller (SOC). After receiving a whole frame of brightness data sent by the SOC, the BCON MCU uses the CPU to centrally reorganize the brightness data into a one-dimensional daisy-chain data stream adapted to the underlying hardware topology according to the mapping relationship. Finally, it uses Direct Memory Access (DMA) to send out all the brightness data.
[0003] The above solution has at least the following problems: Extremely high memory overhead: As the number of MiniLED partitions increases to tens of thousands, the amount of data per frame also increases dramatically. BCONMCU needs to cache the brightness data of an entire frame, consuming the valuable SRAM resources of BCONMCU, thus leading to a surge in system costs. Backlight response delay: Because the BCON MCU must wait for the brightness data of the last pixel to arrive before it can start processing and sending it, the backlight response is always one frame slower than the video signal, which causes serious image quality ghosting and brightness asynchrony problems. Summary of the Invention
[0004] This application provides a backlight control system and a MiniLED display to solve or at least partially solve the above-mentioned technical problems.
[0005] The first aspect of this application provides a backlight control system for use in a MiniLED display, comprising: The main controller is configured to parse the backlight control data of each zone of the MiniLED display for the image to be displayed. A backlight controller is serially connected to a main controller to receive backlight control data sequentially. The backlight controller includes multiple buffer blocks and is configured to look up a preset mapping table based on the sequence number of the backlight control data in the current batch, obtain the allocation information corresponding to the sequence number, and store the backlight control data of the current batch into a target buffer block based on the allocation information. The allocation information includes a target physical link number, and the target buffer block is a buffer block temporarily bound to the target physical link corresponding to the target physical link number. Multiple physical links are connected to the backlight controller, wherein the backlight controller is also configured to, in response to the size of the backlight control data stored in any buffer block reaching a preset threshold, output the backlight control data stored in the buffer block to the corresponding bound physical link, release the buffer block and unbind the buffer block from the corresponding bound physical link.
[0006] A second aspect of this application provides a MiniLED display, including a backlight control system as described above.
[0007] The backlight control system and MiniLED display provided in this application have at least the following beneficial effects: The backlight controller in this embodiment sets up multiple buffer blocks. For the received backlight control data, it looks up a preset mapping table based on the sequence number of the backlight control data in the current batch to obtain the corresponding allocation information, and stores the backlight control data of the current batch into the target buffer block based on the allocation information. The allocation information includes the target physical link number. The target buffer block is a buffer block temporarily bound to the target physical link corresponding to the target physical link number. When the size of the backlight control data stored in any buffer block reaches a preset threshold, the backlight control data stored in the buffer block is output to the corresponding bound physical link, the buffer block is released and the binding between the buffer block and the corresponding bound physical link is released.
[0008] This application enables the output of backlight control data stored in any buffer block to the corresponding bound physical link when the size of the backlight control data reaches a preset threshold, and releases the buffer block. This eliminates the need to wait for the entire frame of data to be received and eliminates the need for full-frame buffering. It achieves complete decoupling of memory space usage from the total number of screen partitions, significantly reduces the SRAM space usage in the backlight controller, and greatly reduces the system's dependence on high-capacity memory resources.
[0009] Meanwhile, this application significantly reduces the backlight response latency of the entire system, perfectly meeting the display requirements of high refresh rate and imperceptible latency.
[0010] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this application. Attached Figure Description
[0011] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with this application and, together with the specification, serve to explain the technical solutions of this application.
[0012] Figure 1 This is a schematic diagram of the backlight control system structure provided in the embodiments of this application; Figure 2 This is a schematic diagram of the hardware topology of the backlight control system provided in the embodiments of this application; Figure 3 This is a schematic diagram of the backlight controller storing backlight control data into a buffer block according to an embodiment of this application; Figure 4 This is a schematic diagram of asynchronous concurrent data on each physical link provided in the embodiments of this application; Figure 5 This is a schematic diagram of the MiniLED display structure provided in the embodiments of this application. Detailed Implementation
[0013] The embodiments of this application will now be described in detail with reference to the accompanying drawings.
[0014] In the following description, specific details such as particular system architectures, interfaces, and technologies are presented for illustrative purposes rather than for limiting purposes, in order to provide a thorough understanding of this application.
[0015] In this document, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " generally indicates that the preceding and following related objects have an "or" relationship. Furthermore, "many" in this document means two or more. Moreover, the term "at least one" in this document means any combination of at least two of any one or more of a plurality of objects. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.
[0016] Those skilled in the art will understand that, in the above-described method of the specific implementation, the order in which each step is written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.
[0017] See Figure 1 and Figure 2 , Figure 1 This is a schematic diagram of the backlight control system structure provided in the embodiments of this application; Figure 2 This is a schematic diagram of the hardware topology of the backlight control system provided in the embodiments of this application.
[0018] In some embodiments, such as Figure 1 As shown, the backlight control system includes: The main controller 11 is configured to parse the backlight control data of each zone of the MiniLED display for the image to be displayed.
[0019] In some embodiments, the backlight control data may be brightness data or other MiniLED backlight display control data.
[0020] In some embodiments, the main controller 11 can be a system on chip (SOC), which can output the backlight control data in pixel scan order via a serial peripheral interface (SPI) bus.
[0021] In some embodiments, the pixel scanning order can be from left to right and from top to bottom for the MiniLED display, and the backlight control data of each MiniLED zone can be scanned and sent in this scanning order.
[0022] In some embodiments, the main controller 11 uses a scanning window to scan each partition of the MiniLED in pixel scanning order to obtain the backlight control data of the current image to be displayed in each partition of the MiniLED. The current image to be displayed can be any frame of the video to be displayed. The above-described parsing, scanning, and output operations are performed for each frame of the video, thereby outputting the backlight control data of each frame of the image to be displayed in a streaming manner.
[0023] The backlight controller 12 is serially connected to the main controller 11 to receive backlight control data sequentially. The backlight controller 12 includes multiple buffer blocks and is configured to look up a preset mapping table based on the sequence number of the backlight control data in the current batch, obtain the allocation information corresponding to the sequence number, and store the backlight control data of the current batch into the target buffer block based on the allocation information. The allocation information includes the target physical link number, and the target buffer block is a buffer block temporarily bound to the target physical link corresponding to the target physical link number.
[0024] Multiple physical links 13 are connected to the backlight controller 12. The backlight controller 12 is also configured to, in response to the size of the backlight control data stored in any buffer block reaching a preset threshold, output the backlight control data stored in the buffer block to the corresponding bound physical link 13, release the buffer block and unbind the buffer block from the corresponding bound physical link 13.
[0025] In some embodiments, each physical link 13 includes multiple LED driver chips, wherein the multiple LED driver chips are connected in series using a daisy-chain protocol, and each LED driver chip includes multiple independent output channels.
[0026] like Figure 2 In the hardware topology example shown, the system contains 12 physical links (LANEs), namely LANE0, LANE1...LANE11, each with a unique physical link number; each LANE uses a daisy-chain protocol to connect multiple driver chips, and each driver chip has multiple PWM channels. Figure 2 In the example shown, each LANE is connected in series with N LED driver chips, namely: chip 0, chip 1, ... chip N. Each LED driver chip has 8 independent pulse width modulation (PWM) channels, namely: channel 0, channel 1 ... channel 7. Each PWM channel corresponds to one LED bead in the MiniLED display.
[0027] In some embodiments, the backlight controller 12 includes: CPU; The memory, in particular, loads the storage mapping table after the backlight control system is powered on; A buffer pool consists of multiple buffer blocks.
[0028] In some embodiments, a mapping table is pre-created, which uses the sequence number of the backlight control data as an index to store the mapping relationship between the sequence number and the physical link number, driver chip number, and output channel number. After receiving the backlight control data, the backlight controller 12 can look up the mapping table using the sequence number of the backlight control data as an index to obtain the target physical link number, target driver chip number, and target output channel number corresponding to the sequence number.
[0029] In some embodiments, such as Figure 2 As shown, the mapping table can be stored in the tightly-coupled memory (TCM) of the backlight controller 12 to ensure fast table lookup.
[0030] In some embodiments, the backlight controller 12 may immediately perform the lookup operation for streaming backlight control data to obtain the target physical link number, target driver chip number, and target output channel number corresponding to the sequence number of the batch of backlight control data.
[0031] In some embodiments, a fixed-size buffer pool, which includes multiple buffer blocks, can be set in the SRAM of the backlight controller 12.
[0032] In some embodiments, the number of multiple buffer blocks is less than the number of multiple physical links 13.
[0033] In some embodiments, the number of buffer blocks can be set such that it is related to the maximum number of physical links 13 corresponding to the scan data of each scan window of the main controller 11. Since the main controller 11 scans each partition of the MiniLED in pixel-by-pixel scan order using scan windows, and the data scanned in each scan window is typically mapped to only a limited number of physical links 13, the number of buffer blocks can be configured according to the number of physical links 13 simultaneously mapped to by the scan data of the scan window. For example, the number of buffer blocks can be set to be equal to the maximum number of physical links 13 corresponding to the scan data of the scan window, or the number of buffer blocks can be set to be greater than the maximum number of physical links 13 corresponding to the scan data of the scan window.
[0034] In some embodiments, the backlight controller 12 is configured to temporarily bind a target buffer block to the target physical link 13 corresponding to the target physical link number; for example, an idle buffer block is selected as the target buffer block and temporarily bound to the target physical link 13 corresponding to the target physical link number.
[0035] In some embodiments, the size of each buffer block corresponds to the maximum load of each physical link 13. For example... Figure 2 In the example shown, each LANE has N driver chips, and each driver chip has 8 PWM channels. Therefore, each LANE has 8N PWM channels, which is the maximum load of the LANE. Thus, the size of each buffer block is 8N, which is the maximum load of the LANE.
[0036] In this embodiment, the number of buffer blocks is set to be related to the maximum number of physical links 13 corresponding to the scan data of the scanning window. This number is much smaller than the total number of physical links 13. Furthermore, the size of each buffer block is set to correspond to the maximum load of each physical link 13. This completely decouples the memory space occupation of the buffer blocks from the total number of MiniLED partitions, thereby reducing the existing O(N×M) two-dimensional full-frame memory occupation to the O(1) constant level.
[0037] In some embodiments, after temporarily binding a target buffer block to the target physical link 13 corresponding to the target physical link number, the backlight controller 12 can also set a threshold for the backlight control data stored in the target buffer block. This threshold can be the maximum load of the temporarily bound target physical link 13, or it can be less than the maximum load of the temporarily bound target physical link 13. When the size of the backlight control data stored in the target buffer block reaches this threshold, the backlight control data stored in the target buffer block is triggered to be output to the corresponding bound physical link 13.
[0038] This application embodiment sets the threshold of the backlight control data stored in the target buffer block to be less than or equal to the maximum load of the temporarily bound target physical link 13. On the one hand, it can avoid the buffer overflow problem. On the other hand, it can trigger the overall output when the size of the backlight control data stored in the buffer block reaches the maximum load of the bound target physical link 13. This allows the backlight control data on the same physical link 13 to be loaded and output synchronously at the same time, avoiding the line-by-line scanning time difference caused by some channels updating first and some updating later within the same physical link 13. It also avoids the horizontal water ripples and alternating bright and dark stripes caused by asynchronous refresh, thereby improving the backlight uniformity.
[0039] In some embodiments, each position in the buffer block corresponds to the driver chip number and the corresponding output channel number of the driver chip.
[0040] In some embodiments, the allocation information further includes the target driver chip number and the target output channel number. The backlight controller 12 stores the backlight control data of the current batch into the target location of the target buffer block based on the target physical link number, target driver chip number, and target output channel number in the allocation information. For example, positions 0 to 7 in the buffer block sequentially store the backlight control data of the first driver chip's CH0 to CH7 (a total of 8 PWM channels); positions 8 to 15 in the buffer block sequentially store the backlight control data of the second driver chip's CH0 to CH7 (a total of 8 PWM channels); and so on. The backlight control data stored in the buffer block strictly follows the daisy-chain cascading order and the sequential arrangement of the corresponding PWM channel numbers of the driver chips, without any out-of-order insertion.
[0041] See Figure 3 The diagram shown illustrates how the backlight controller 12, according to an embodiment of this application, stores backlight control data into buffer blocks. In this example, four buffer blocks are configured: buffer block 1, buffer block 2, buffer block 3, and buffer block 4. Figure 3 The numbers 0, 1, ..., 8 represent the sequence numbers corresponding to eight backlight control data points. For the first sequence number 0, after looking up the mapping table, the target physical link number is determined to be L2, the target driver chip number is chip 0, and the target output channel number is CH3. The target buffer block bound to L2 is buffer block 2. The backlight control data for sequence number 0 is stored in the corresponding position in buffer block 2 according to the corresponding positions of chip 0 and channel CH3. For sequence number 1, after looking up the mapping table, the target physical link number is determined to be L1, the target driver chip number is chip 0, and the target output channel number is CH0. The target buffer block bound to L1 is buffer block 1. The backlight control data for sequence number 1 is stored in the corresponding position in buffer block 1 according to the corresponding positions of chip 0 and channel CH0. The same distribution operation is used to store all backlight control data into the buffer blocks.
[0042] In some embodiments, the backlight controller 12 is further configured to: In response to the failure of the target physical link number corresponding to the backlight control data of the current batch to be successfully bound to the target buffer block, a buffer block is selected according to the preset rules, the backlight control data stored in the selected buffer block is output to the corresponding bound physical link 13, the buffer block is released, and the released buffer block is used as the target buffer block and bound to the corresponding target physical link 13.
[0043] In some embodiments, the preset rules include: Select the buffer block with the largest amount of backlight control data currently stored as the target buffer block; or, select the buffer block whose last release time is the longest since the current time as the target buffer block.
[0044] In some embodiments, releasing the buffer block includes: outputting the backlight control data stored in the buffer block to the corresponding bound physical link 13, and unbinding it from the original physical link number.
[0045] In some embodiments, for buffer blocks whose stored backlight control data size does not reach a preset threshold and need to be released in advance according to the above rules, the missing data can be filled with historical values or default values before being sent out.
[0046] This application embodiment can forcibly trigger the release of buffer blocks when there are no free buffer blocks, thereby ensuring that the buffer block is successfully bound to the current physical link 13, which can prevent system deadlock problems caused by extreme physical wiring disorder or SPI communication packet loss.
[0047] In some embodiments, each buffer block is provided with a buffer block monitor, which monitors whether the size of the backlight control data stored in the buffer block reaches a preset threshold for triggering output through a counter. For example, the counter value is incremented by 1 for each backlight control data stored in the buffer block, and the counter value is used to monitor whether the size of the backlight control data stored in the buffer block reaches a preset quantity threshold.
[0048] In some embodiments, the backlight controller 12 outputs the backlight control data stored in the buffer block to the corresponding bound physical link 13, including: Protocol encapsulation: Preset protocol headers are added to the front and back of the buffer block. For example, a frame start marker, total number of channels, LANE number, etc. are added to the front, and a checksum and end marker are added to the backlight control data in the entire buffer block. This concatenates all backlight control data in the entire buffer block into a serial bit stream and encapsulates it into a continuous daisy chain data frame.
[0049] Start the DMA channel of physical link 13 bound to the buffer block and send out the entire string of consecutive daisy-chain data frames.
[0050] In some embodiments, after receiving a continuous daisy-chain data frame, each driver chip can latch the backlight control data of multiple PWM channels corresponding to its own end (for example, by using a shift register configured for each PWM channel to latch the backlight control data corresponding to each PWM channel). After all the cascaded driver chips in the physical link 13 have completed data latching, they are synchronously output through the corresponding PWM channels, that is, each PWM channel of each driver chip synchronously updates the duty cycle, so that each MiniLED partition synchronously adjusts the backlight of the MiniLED.
[0051] In the embodiments of this application, the distribution and scheduling operations of backlight control data and the receiving operations do not interfere with each other.
[0052] In some embodiments, after the backlight controller 12 outputs the backlight control data stored in the buffer block to the corresponding bound physical link 13, it unbinds the buffer block from the corresponding bound physical link 13, so that it can be used for subsequent backlight control data. This enables time-division multiplexing of the buffer block, saves storage space, and reduces resource consumption.
[0053] In some embodiments, the backlight controller 12 is further configured to forcibly release all buffer blocks in response to receiving the next frame video synchronization signal (VSYNC).
[0054] This application embodiment treats the video synchronization signal as the highest priority interrupt. When VSYNC is detected, regardless of whether the size of the backlight control data stored in each buffer block reaches a preset threshold, a "global forced clear" is immediately triggered. This outputs all unsent data in each buffer block, forcibly clears all binding relationships and counters, and resets the system to process the next frame of data. This operation avoids problems such as ghosting, afterimages, and trailing caused by frame residue, and also prevents buffer overflow and blocking, thereby improving system response speed.
[0055] See Figure 4 As shown, Figure 4 This is a schematic diagram of asynchronous concurrent data transmission on each physical link 13 provided in the embodiments of this application. The transmission time of one frame of data is between the falling edges of two VSYNC signals. SPI RX Data represents the data transmitted by the master controller 11 using SPI. Figure 4 As can be seen, this application can realize the asynchronous concurrent transmission of data by multiple LANEs without having to transmit data only after receiving a complete frame of data, thus effectively reducing the backlight response latency problem.
[0056] This application embodiment targets backlight control data received via streaming. It utilizes a mapping table to perform a real-time distribution operation of "one data arrives, one data is retrieved, and one data is stored". At the same time, the buffer block that first reaches the preset threshold (corresponding to a physical link where the data flowed in earlier) is triggered to output in advance, and then the buffer block is immediately released. This not only achieves constant-level memory compression, but also achieves visually imperceptible ultra-low latency data flow. Furthermore, each physical link 13 can be cached independently in parallel and sent out asynchronously, improving throughput and further enhancing backlight response speed.
[0057] In some embodiments, if packet loss occurs, packet replacement can be performed. For example, if packet loss is detected, backlight control data of the corresponding partition in the previous frame can be used for packet replacement. Furthermore, if the number of consecutive packet losses reaches a set threshold, a frame reduction and anti-shake mechanism can be triggered to avoid instantaneous black screen or dark area abruptness issues.
[0058] In some embodiments, to improve the synchronization of the output of each driver chip, the implementation deviation of the output of each driver chip can be detected, microsecond-level timing compensation can be performed for the lagging driver chip, and delay latching can be performed for the leading driver chip to ensure that the backlight of all MiniLED zones of the whole screen is refreshed synchronously, eliminating display defects caused by timing differences across driver chips and improving the uniformity of screen image display.
[0059] The backlight controller 12 of this application embodiment is provided with multiple buffer blocks. For the received backlight control data, it looks up a preset mapping table based on the sequence number of the backlight control data of the current batch to obtain the corresponding allocation information, and stores the backlight control data of the current batch into the target buffer block based on the allocation information. The allocation information includes the target physical link number. The target buffer block is a buffer block temporarily bound to the target physical link 13 corresponding to the target physical link number. When the size of the backlight control data stored in any buffer block reaches a preset threshold, the backlight control data stored in the buffer block is output to the corresponding bound physical link 13, the buffer block is released and the binding between the buffer block and the corresponding bound physical link 13 is released.
[0060] This application enables the output of backlight control data stored in any buffer block to the corresponding bound physical link 13 when the size of the backlight control data reaches a preset threshold, releasing the buffer block without waiting for the entire frame of data to be received or requiring full-frame buffering. This achieves complete decoupling of memory space usage from the total number of screen partitions, significantly reducing the SRAM space usage within the backlight controller and greatly alleviating the system's dependence on high-capacity memory resources. This allows for the use of lower-cost MCU solutions to achieve large-scale backlight driving. Simultaneously, this application significantly reduces the backlight response latency of the entire system, perfectly meeting the display requirements of high refresh rates and imperceptible latency.
[0061] An example of an application of the backlight control system of this application is as follows: Scenario: A TV has 5040 partitions and uses 12 LANEs. The number of driver chips mounted on each LANE has reached the physical limit (e.g., it can store a maximum of 840 partitions of data). Now, it is necessary to upgrade the TV to 10080 partitions (tens of thousands), but the number of LANEs remains the same.
[0062] In existing solutions, upgrading a TV to 10080 partitions requires allocating 10080 memory slots, leading to a linear increase in memory demand as the screen size increases. The solution proposed in this application ensures that regardless of the number of partitions on the screen, the number of adjacent physical links 13 mapped to the data within a scan window when the SOC scans a specific area of the screen is fixed. For example, it can be mapped to a maximum of 4 LANEs. Therefore, only 4 buffer blocks need to be set in the SRAM of the backlight controller 12, with each buffer block size matching the maximum load (840) of a single LANE. When one buffer block is full, a DMA transmission is immediately triggered. After transmission is complete, the buffer block is unbound from the LANE and released, allowing it to be used to buffer the next wave of data.
[0063] The above comparison shows that the backlight controller 12 of this application only needs to open 4 × 840 = 3360 memory slots. No matter how the screen partitions double, the cache size is always a fixed value, which completely decouples the memory space of the buffer block from the total number of MiniLED partitions, reducing the existing O(N × M) two-dimensional full frame memory occupation to O(1) constant level, and significantly reducing the SRAM space occupation of BCON MCU.
[0064] This application also provides a MiniLED display, including the backlight control system described above. See also... Figure 5 , Figure 5 This is a schematic diagram of the MiniLED display structure provided in an embodiment of this application. The MiniLED display 100 may further include a processor 110 with one or more processing cores and a memory 120 with one or more computer-readable storage media. The memory 120 stores a computer program, which the processor 110 can run. The processor 110 and the memory 120 are electrically connected.
[0065] Those skilled in the art will understand that the structure of the MiniLED display 100 shown in the figure does not constitute a limitation on the MiniLED display 100, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0066] The processor 110 is the control center of the MiniLED display 100. It connects various parts of the MiniLED display through various interfaces and lines. By running or loading computer programs and / or modules stored in the memory 120, and calling data stored in the memory 120, it performs various functions of the backlight control system and processes data, thereby controlling the MiniLED display 100.
[0067] The description of the various embodiments above tends to emphasize the differences between the various embodiments. The similarities or similarities between them can be referred to, and for the sake of brevity, they will not be repeated here.
[0068] In the several embodiments provided in this application, it should be understood that the disclosed methods and apparatus can be implemented in other ways. For example, the apparatus implementations described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection of devices or units may be electrical, mechanical, or other forms.
[0069] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0070] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
Claims
1. A backlight control system for use in a MiniLED display, characterized in that, include: The main controller is configured to parse the backlight control data of each zone of the MiniLED display for the image to be displayed. A backlight controller is serially connected to the main controller to receive backlight control data sequentially. The backlight controller includes multiple buffer blocks and is configured to look up a preset mapping table based on the sequence number of the current batch of backlight control data to obtain allocation information corresponding to the sequence number, and store the current batch of backlight control data into a target buffer block based on the allocation information. The allocation information includes a target physical link number, and the target buffer block is a buffer block temporarily bound to the target physical link corresponding to the target physical link number. Multiple physical links are connected to the backlight controller, wherein the backlight controller is further configured to, in response to the size of the backlight control data stored in any of the buffer blocks reaching a preset threshold, output the backlight control data stored in the buffer block to the corresponding bound physical link, release the buffer block and unbind the buffer block from the corresponding bound physical link.
2. The backlight control system according to claim 1, characterized in that, Each physical link includes multiple LED driver chips, wherein the multiple LED driver chips are connected in series using a daisy-chain protocol, and each LED driver chip includes multiple independent output channels; The allocation information also includes the target driver chip number and the target output channel number. The backlight controller stores the backlight control data of the current batch into the target location of the target buffer block based on the target physical link number, the target driver chip number and the target output channel number in the allocation information.
3. The backlight control system according to claim 1, characterized in that, The backlight controller includes: CPU; The memory, wherein, after the backlight control system is powered on, the memory loads and stores the preset mapping table; The buffer pool includes multiple buffer blocks.
4. The backlight control system according to claim 1, characterized in that, The size of each buffer block corresponds to the maximum load of each physical link.
5. The backlight control system according to claim 1, characterized in that, The number of the multiple buffer blocks is less than the number of the multiple physical links.
6. The backlight control system according to claim 1, characterized in that, The number of the multiple buffer blocks is related to the maximum number of physical links corresponding to the data scanned in each scanning window of the main controller.
7. The backlight control system according to claim 1, characterized in that, The backlight controller is also configured to, in response to the failure of the target physical link number corresponding to the backlight control data of the current batch to be successfully bound to the target buffer block, select a buffer block according to a preset rule, output the backlight control data stored in the selected buffer block to the corresponding bound physical link, release the buffer block, and bind the released buffer block as the target buffer block to the corresponding target physical link.
8. The backlight control system according to claim 7, characterized in that, The preset rules include: Select the buffer block with the largest amount of backlight control data currently stored as the target buffer block; or Select the buffer block whose last release time is the longest since the current time as the target buffer block.
9. The backlight control system according to claim 1, characterized in that, The backlight controller is also configured to forcibly release all of the buffer blocks in response to receiving the next frame video synchronization signal.
10. A MiniLED display, characterized in that, Includes the backlight control system as described in any one of claims 1-9.
