Data cascaded read-back control method and apparatus, and display system

Abstract

A data cascaded read-back control method and apparatus, and a display system. In the apparatus, each controller (11) corresponds to at least one drive unit (12), and each drive unit (12) comprises: a plurality of drivers sequentially cascaded from a first driver (121) to a last driver (122). The control method comprises: step S11, issuing a read-back instruction to a drive unit (12), such that the read-back instruction sequentially passes through a first driver (121) to a last driver (122) of the drive unit (12); and step S12, receiving the read-back instruction returned from the last driver (122) of the drive unit (12), wherein the returned read-back instruction comprises at least one data segment, and each data segment corresponds to one driver. The control method enables the completion of information read-back of all drivers requiring read-back in the entire drive unit by means of issuing only one read-back instruction, thereby improving the read-back efficiency, reducing the time consumption, and reducing the load of a controller.

Description

Data level back read control method and device, and display system TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, in particular to a data level back read control method and device, and display system. BACKGROUND

[0002] In a display system, drivers are often arranged in a cascaded manner, and a cascaded link is controlled by a controller to complete the issuing of instructions such as driver address allocation, register configuration, display data configuration, register information back read, and state back read.

[0003] A conventional cascaded link back read control method only supports the information of a single driver for one instruction, and in order to perform back read on all drivers on a cascaded link, the controller needs to send back read instructions a total number of times of the drivers, as shown in FIG. 1, to perform back read on N drivers, the controller needs to send back read instructions n times, and each driver writes its back read information into an empty data segment of the controller to form a corresponding data segment 1, and the back read instruction transmitted back one time only contains the back read information of one driver. The above back read control method generates a large load on the controller, and frequent sending of back read instructions also limits the operability space of other instructions in the same display refresh period.

[0004] Therefore, there is an urgent need to provide a novel data level back read control method to improve the back read efficiency and reduce the working load of the controller. SUMMARY

[0005] The present application provides a data level back read control method and device, and display system to solve the problem of large load of the controller and low back read efficiency in the prior art.

[0006] To solve the above technical problems, the present application is implemented by the following technical solutions:

[0007] According to a first aspect of the present application, a data level back read control method is provided, applied to a controller end, each controller corresponding to at least one driving unit, each driving unit including a plurality of drivers cascaded in turn from a first driver to a last driver, and the control method includes:

[0008] issuing a back read instruction to the driving unit, so that the back read instruction passes through the first driver to the last driver of the driving unit in turn;

[0009] receiving the back read instruction transmitted back from the last driver of the driving unit, wherein the transmitted back back read instruction includes at least one data segment, and each data segment corresponds to one driver.

[0010] Optionally, the issued readback instruction does not reserve a data segment.

[0011] Optionally, the issued readback instruction includes a frame header.

[0012] The frame header includes address information of a starting end drive requiring readback and address information of a terminal end drive requiring readback; or,

[0013] The frame header includes address information of a starting end drive requiring readback and a number of drives requiring readback.

[0014] According to a second aspect of the present application, a data level readback control method is provided, which is applied to a drive end, each controller corresponds to at least one drive unit, each drive unit includes a plurality of drives which are cascaded in sequence from a first drive to a last drive, and the control method includes:

[0015] The first drive of the drive unit receives a readback instruction issued by the controller, and generates a corresponding readback instruction.

[0016] The readback instruction passes through the second drive to the last drive of the drive unit in sequence.

[0017] The last drive transmits the corresponding readback instruction back to the controller; wherein the transmitted readback instruction includes at least one data segment, and each data segment corresponds to one drive.

[0018] Optionally, the issued readback instruction does not reserve a data segment, and the specific forming method of the data segment in the transmitted readback instruction is:

[0019] The drive expands its corresponding data segment to the frame tail of the corresponding readback instruction.

[0020] Optionally, the issued readback instruction includes a frame header.

[0021] The frame header includes address information of a starting end drive requiring readback and address information of a terminal end drive requiring readback; or,

[0022] The frame header includes address information of a starting end drive requiring readback and a number of drives requiring readback.

[0023] According to a third aspect of the present application, a data level readback control device is provided, each controller corresponds to at least one drive unit, each drive unit includes a plurality of drives which are cascaded in sequence from a first drive to a last drive, and the control device includes:

[0024] The read-back instruction issuing module is configured to issue a read-back instruction, so that the read-back instruction passes through the first driver to the last driver of the driving unit in sequence.

[0025] The read-back instruction receiving module is configured to receive a read-back instruction returned from the last driver of the driving unit, wherein the returned read-back instruction comprises at least a data segment, and each data segment corresponds to a driver.

[0026] Optionally, the display system further comprises:

[0027] The information expanding module is configured to expand the data segment corresponding to the driver to the frame tail of the corresponding read-back instruction.

[0028] According to a fourth aspect of the present application, a display system is provided, which comprises:

[0029] a controller;

[0030] a driving unit, each controller corresponding to at least one driving unit, and each driving unit comprising a plurality of drivers connected in sequence from a first driver to a last driver;

[0031] The data-level read-back control device is any of the above data-level read-back control devices.

[0032] According to a fifth aspect of the present application, an electronic device is provided, which comprises:

[0033] a processor; and a memory for storing processor-executable instructions.

[0034] The processor implements the steps in any of the above methods by running the executable instructions.

[0035] According to a sixth aspect of the present application, a storage medium is provided, which stores a computer program, and the computer program is executed by a processor to implement the steps in any of the above methods.

[0036] The data-level read-back control method and device, and the display system provided by the present application can complete the information read-back of all the drivers requiring read-back in the entire driving unit by issuing a read-back instruction only once, and the read-back can be completed by one read-back when multiple drivers require read-back, thereby improving the read-back efficiency. In addition, the controller only needs to send a read-back instruction once, thereby reducing the load of the controller and saving time occupation, and further increasing the operability space of other instructions in the same display refresh cycle.

[0037] In an optional solution of the present application, the read-back instruction issued does not reserve a data section, the single frame length of the instruction is shorter, and the working load of the controller is further reduced; in addition, the read-back instruction issued does not reserve a data section, the driver only needs to directly extend its corresponding data section to the frame tail of the corresponding read-back instruction, and does not need to modify the frame format of the data section, the read-back is simpler, and the read-back efficiency is faster.

[0038] In an optional solution of the present application, the frame header of the controller includes address information, if there is a fault or information needing adjustment in the read-back information, the address information can be used to determine which driver has a problem.

[0039] In an optional solution of the present application, the frame header of the controller can include address information of a start-end driver needing read-back and address information of a terminal-end driver needing read-back, because the drivers are sequentially cascaded, the read-back instruction sequentially passes through, and therefore, the address information of the start-end driver and the address information of the terminal-end driver are given, that is, the drivers needing read-back are given; through the above setting, the controller can freely specify which drivers in the driving unit to read back, only the drivers needing read-back need to be read back, all the drivers do not need to be read back every time, the read-back time is further saved, the read-back is more accurate, and the read-back data is more convenient to interpret.

[0040] In an optional solution of the present application, the frame header of the controller can include address information of a start-end driver needing read-back and the number of drivers needing read-back, because the drivers are sequentially cascaded, the read-back instruction sequentially passes through, and therefore, as long as the start-end driver and the number of drivers needing read-back are given, that is, the drivers needing read-back are given, the given number of drivers starting from the start-end driver are the drivers needing read-back; through the above setting, the controller can also freely specify which drivers in the driving unit to read back, only the drivers needing read-back need to be read back, all the drivers do not need to be read back every time, the read-back time is further saved, the read-back is more accurate, and the read-back data is more convenient to interpret. BRIEF DESCRIPTION OF DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or the prior art description. Obviously, the drawings in the following description only some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor.

[0042] FIG. 1 is a prior data read-back method;

[0043] FIG. 2 is a connection diagram of a controller and a driver in an embodiment of the present application;

[0044] Fig. 3 is a flow chart of a data level readback control method according to an embodiment of the present application;

[0045] Fig. 4 is a flow chart of a data level readback control method according to an embodiment of the present application;

[0046] Fig. 5 is a comparison of the working timing of a controller in a single display refresh period according to the present application and prior art;

[0047] Fig. 6 is a command schematic diagram of a data level readback control method according to a preferred embodiment of the present application;

[0048] Fig. 7 is a command schematic diagram of a data level readback control method according to a preferred embodiment of the present application;

[0049] Fig. 8 is a command schematic diagram of a data level readback control method according to an embodiment of the present application;

[0050] Fig. 9 is a schematic diagram of a data level readback control device according to an embodiment of the present application;

[0051] Fig. 10 is a schematic diagram of an electronic device according to an embodiment of the present application;

[0052] Reference signs: 11-controller, 12-driving unit; 121-first driver, 122-last driver; 21-readback instruction issuing module; 22-readback instruction receiving module; 31-processor, 32-internal bus, 33-network interface, 34-internal memory, 35-external memory. DETAILED DESCRIPTION

[0053] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work fall within the scope of protection of the present application.

[0054] In the description of the present application, it should be understood that the terms "upper", "lower", "upper end", "lower end", "lower surface", "upper surface" and the like indicate the orientation or positional relationship shown in the drawings, and are only for the convenience of describing the present application and simplifying the description, and do not indicate or imply that the devices or elements referred to must have a particular orientation, be constructed and operated in a particular orientation, and therefore cannot be understood as a limitation on the present application.

[0055] In the description of the present application, the terms "first", "second" are only for descriptive purpose, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined with "first", "second" can be explicitly or implicitly included one or more of the features.

[0056] In the description of the present application, the meaning of "a plurality of" is a plurality, for example, two, three, four, etc., unless otherwise explicitly specified and limited.

[0057] In the description of the present application, unless otherwise explicitly specified and limited, the term "connection" and other terms should be understood broadly, for example, it can be fixed connection, or detachable connection, or integrated; it can be mechanical connection, or electrical connection or can communicate with each other; it can be directly connected, or indirectly connected through an intermediate medium, or the internal communication of two elements or the interaction relationship between two elements. For those skilled in the art, the specific meaning of the above terms in the present application can be understood according to the specific circumstances.

[0058] The technical solutions of the present application will be described in detail below with specific examples. The following specific examples can be combined with each other, and the same or similar concepts or processes can not be described in some examples.

[0059] The data level readback control of the present application is suitable for cascade driver, please refer to Fig. 2. Each controller 11 corresponds to at least one drive unit 12, and each drive unit 12 includes a plurality of drivers, which are cascaded in turn from the first driver 121 to the last driver 122.

[0060] In an embodiment, a data level readback control method is provided, applied to the controller end, please refer to Fig. 3, including:

[0061] S11: issuing a readback instruction to the drive unit, so that the readback instruction passes through the first driver to the last driver of the drive unit in turn, and the driver generates a corresponding readback instruction when the readback instruction passes through the driver;

[0062] S12: receiving the readback instruction returned from the last driver of the drive unit, wherein the returned readback instruction includes at least one data segment, and each data segment corresponds to a driver, that is, the number of data segments in the returned readback instruction is consistent with the number of drivers that need to be readback in the corresponding drive unit, and the readback of all drivers that need to be readback is completed at one time.

[0063] In an embodiment, a data level readback control method is provided, applied to the driver end, please refer to Fig. 4, including:

[0064] S21: The first driver of the driving unit receives the read-back instruction issued by the controller, generates a corresponding read-back instruction, and transmits the read-back instruction to the next driver;

[0065] S22: The read-back instruction is sequentially transmitted through the second driver to the last driver of the driving unit; specifically, each driver generates a corresponding read-back instruction and transmits the read-back instruction to the next driver;

[0066] S23: The last driver transmits the corresponding read-back instruction back to the controller; wherein the transmitted read-back instruction includes at least one data segment, and each data segment corresponds to one driver.

[0067] The data-level read-back control method of the above embodiment, the number of data segments in the transmitted read-back instruction corresponds to the number of drivers that need to be read back, and only one read-back instruction needs to be issued to complete the information read-back of all the drivers that need to be read back in the entire driving unit, thereby improving the read-back efficiency. Please refer to the comparison between (1) and (2) in FIG. 5, (2) is the read-back control method of the present application, in which the read-back of multiple drivers is performed in a single display refresh period, and the controller only needs to issue one read-back instruction; while (1) is the read-back control method of the prior art, in which the read-back of multiple drivers (N) is performed, and N read-back instructions (read-back 1…read-back N) need to be issued. One read-back is definitely faster than multiple read-backs, thereby improving the read-back efficiency; in addition, the remaining operability time margin of the single display refresh period of the present application is obviously more than the remaining operability time margin of the prior art, and the controller can process more other work by using the time margin.

[0068] It can be understood that the generation of the corresponding read-back instruction by the driver is as follows: if the driver is a driver that needs to be read back, the corresponding read-back information is written into the read-back instruction, and then the read-back instruction is transmitted to the next driver; if the driver is a driver that does not need to be read back, the read-back instruction is not modified, and the read-back instruction is directly transmitted to the next driver.

[0069] Of course, each read-back can also be the read-back of all the drivers of the corresponding driving unit, and in this case, the generation of the corresponding read-back instruction by the driver is as follows: the corresponding read-back information is written into the read-back instruction, and then the read-back instruction is transmitted to the next driver.

[0070] Practically, it is assumed that the driver includes N drivers, and if all the drivers need to be read back, the transmitted read-back instruction includes N data segments.

[0071] Of course, not all the drivers need to be read back, and the following examples are given: if only N-2 drivers need to be read back, the transmitted read-back instruction includes N-2 data segments; if only one driver needs to be read back, the transmitted read-back instruction includes one data segment.

[0072] If each drive needs to be read back every time the drive unit is read back, the drive can be configured to write the corresponding read-back information into the read-back instruction as soon as it receives the read-back instruction, generating a corresponding read-back instruction. If not every drive needs to be read back, the read-back instruction can be configured to carry data on which drives need to be read back, and the drive can be configured to determine whether it is a drive that needs to be read back after receiving the read-back instruction. If it is not a drive that needs to be read back, the drive directly transmits the read-back instruction to the next drive. If it is a drive that needs to be read back, the drive writes the corresponding read-back information into the read-back instruction, generating a corresponding read-back instruction.

[0073] As an embodiment, the read-back instruction issued includes a frame header. The frame header includes address information of a start-end drive that needs to be read back and address information of a terminal-end drive that needs to be read back. For example, if the drive unit includes N drives, and the read-back information of the second to fifth drives needs to be read back, the frame header includes address information of the second drive and address information of the fifth drive. The drives within the range of the address information (the two address information or between the two address information) are drives that need to be read back. After receiving the read-back instruction, the drive determines whether its address information is within the range of the address information in the frame header. If it is, the drive writes its read-back information into the read-back instruction. If it is not, the drive does not write its read-back information into the read-back instruction.

[0074] As another embodiment, the frame header includes address information of a start-end drive that needs to be read back and the number of drives that need to be read back. For example, if the drive unit includes N drives, and the read-back information of the second to fifth drives needs to be read back, the frame header includes address information of the second drive and the number of drives that need to be read back, which is four. After receiving the read-back instruction, the drive determines whether its address information is within the range of the address information or the four drives starting from the address information in the frame header. If it is, the drive writes its read-back information into the read-back instruction. If it is not, the drive does not write its read-back information into the read-back instruction.

[0075] In the above two embodiments, the address information in the frame header not only enables selective read-back of some continuous drives, i.e., not necessarily all drives are read back every time, the number of drives read back every time is not necessarily the same, and the position of the drives read back every time is not necessarily the same, but also enables the correspondence between the data segment and the drive, so that it is easy to know which data segment corresponds to which drive and it is easy to find.

[0076] It should be noted that the frame header does not necessarily contain address information. All drivers can be read back each time; that is, as long as a driver receives a readback command, it performs the readback without needing to determine the address information. When reading back all drivers each time, the frame header can also contain address information. However, in this case, the address information does not need to indicate which drivers need to be read back. It's only for the convenience of mapping the quantity field to the driver; it can include only the address information of the first driver. This way, when each controller corresponds to multiple driver units, it's easy to know which driver unit the returned readback command corresponds to.

[0077] In one embodiment, the issued readback command may not reserve a data segment. The specific method for forming at least one data segment in the returned readback command is as follows: the driver expands its corresponding data segment to the beginning of the frame of the corresponding readback command. Since the controller's readback command does not reserve a data segment, the single frame length can be shorter, further reducing the controller's load. Furthermore, the transmission speed of the readback command is faster, thereby further improving readback efficiency. Additionally, if the issued readback command reserves a data segment, the driver needs to fill its readback information into the reserved data segment, requiring modification of the frame format. However, for commands without reserved data segments, the driver only needs to directly expand its readback information to the corresponding position without modifying the frame format, making readback simpler and faster.

[0078] In practice, the issued readback command includes, in sequence, a start field, a frame header, and a frame tail, as shown in Figure 6, which illustrates the transmission of a single readback command. Upon receiving the readback command, the driver extends its corresponding readback output to the beginning of the frame tail of the readback command before transmitting it to the next driver.

[0079] Figure 6 illustrates an example where each driver needs to read back. In different embodiments, when not every driver needs to read back, the driver that does not need to read back performs no operation upon receiving the read back command and directly transmits the read back command to the next driver. The driver that needs to read back, upon receiving the read back command, extends its corresponding read back output to the end of the read back command frame and then transmits it to the next driver. Please refer to Figure 7 for an example where driver 1 does not need to read back, while drivers 2-N do. In this case, the first driver does not generate a data segment, and data segment 1 corresponds to the read back information of driver 2, and so on.

[0080] Of course, in different embodiments, the issued readback command can also reserve data segments. There are multiple reserved data segments, and the number of reserved data segments can correspond to the number of drivers of the corresponding driving unit. Please refer to Figure 8. The driver only needs to fill its corresponding readback information into the corresponding data segment.

[0081] It should be noted that the number of reserved data segments is not limited, and the number of reserved data segments (blank data segments) is taken as N in FIG. 8; in different embodiments, the number of reserved data segments can be inconsistent with the number of drives, for example, for N drives, N-1 blank data segments can be reserved, and of course, at most N-1 drives can be read back at a time.

[0082] In an embodiment, a data-level readback control device is provided, as shown in FIG. 9, which includes:

[0083] The readback instruction issuing module 21 is configured to issue a readback instruction to the drive unit, so that the readback instruction passes through the first drive to the last drive of the drive unit in sequence, and when the readback instruction passes, the drive to be read back writes the readback information into the readback instruction;

[0084] The readback instruction receiving module 22 is configured to receive the readback instruction returned from the last drive of the drive unit, wherein the returned readback instruction includes at least one data segment, and each data segment corresponds to a drive, i.e., the number of data segments corresponds to the number of drives to be read back.

[0085] In an embodiment, when the readback instruction issuing module 21 does not reserve a data segment in the readback instruction, the control device further includes:

[0086] The information expansion module is configured to expand the data segment corresponding to the drive to the front of the frame tail of the corresponding readback instruction, to generate the readback instruction corresponding to the drive.

[0087] In an embodiment, a display system is provided, which includes a controller, a drive unit, and a data-level readback control device. The arrangement of the controller and the drive unit is shown in FIG. 2, each controller corresponds to at least one drive unit, and each drive unit includes a plurality of drives cascaded in sequence from the first drive to the last drive. The data-level readback control device is any of the data-level readback control devices described in the above embodiments.

[0088] In an embodiment, the readback instruction issuing module 21 and the readback instruction receiving module 22 can be arranged in the controller.

[0089] In an embodiment, the information expansion module can be arranged in the drive.

[0090] In one embodiment, an electronic device is provided, please refer to Fig. 10. At the hardware level, the device includes a processor 31, an internal bus 32, a network interface 33, a memory 34 and a storage 35, and of course, other hardware required by the business. One or more embodiments of the present application can be implemented in software, such as by the processor 31 reading corresponding computer programs from the storage 35 to the memory 34 and then running. Of course, in addition to the software implementation, one or more embodiments of the present application do not exclude other implementations, such as logic devices or a combination of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logical unit, but can also be hardware or logic devices.

[0091] The systems, apparatuses, modules or units illustrated in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, and the specific form of the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0092] In a typical configuration, a computer includes one or more processors (CPUs), input / output interfaces, network interfaces and memories.

[0093] The memory can include non-permanent memory in a computer readable medium, random access memory (RAM) and / or non-volatile memory such as read-only memory (ROM) or flash memory (flash RAM). The memory is an example of a computer readable medium.

[0094] The computer readable medium includes permanent and non-permanent, removable and non-removable media, which can be implemented by any method or technology to store information. The information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, disk storage, quantum memory, graphene-based storage medium or other magnetic storage device, or any other non-transmission medium that can be used to store information accessible by a computing device. According to the definition in this paper, computer readable medium does not include transitory computer readable medium, such as modulated data signals and carriers.

[0095] The above described a particular embodiment of the present application. Other embodiments are within the scope of the following claims. In some cases, the acts or steps recited in the claims can be performed in a different order and still accomplish desirable results. Additionally, the processes depicted in the accompanying figures do not necessarily require the particular order shown or sequential order to achieve desirable results. In certain implementations, multitasking and parallel processing can be advantageous.

[0096] In the description of the present application, the description of the terms "one implementation", "one embodiment", "specific implementation process", "one example" and the like means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In the present specification, the illustrative description of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0097] It should be understood that although the terms first, second, third, etc. can be employed in describing various information in one or more embodiments of the present application, the information should not be limited to these terms. These terms are only used to distinguish one piece of information from another piece of information. For example, the first information can also be referred to as the second information, and similarly, the second information can also be referred to as the first information, without departing from the scope of one or more embodiments of the present application. Depending on the context, the word "if" as used herein can be interpreted as "when" or "upon" or "in response to determining".

[0098] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit it; although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that the technical solutions recorded in the above embodiments can still be modified, or some or all of the technical features can be replaced by equivalents; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A data level readback control method, applied to a controller end, characterized in that, Each controller corresponds to at least one drive unit, each drive unit comprises: a plurality of drivers cascaded in sequence from a first driver to a last driver; the control method comprises: issuing a read-back instruction to the drive unit, so that the read-back instruction passes through the first driver to the last driver of the drive unit in sequence; receiving the read-back instruction transmitted back from the last driver of the drive unit, wherein the transmitted-back read-back instruction comprises at least one data segment, and each data segment corresponds to one driver.

2. The data level readback control method of claim 1, wherein, The issued read-back instruction does not reserve a data segment.

3. The data level readback control method of claim 1 or 2, wherein, The issued read-back instruction comprises a frame header. The frame header comprises address information of a start-end driver requiring read-back and address information of a terminal-end driver requiring read-back; or The frame header comprises address information of a start-end driver requiring read-back and a number of drivers requiring read-back.

4. A data level readback control method, applied to a driver end, characterized in that, Each controller corresponds to at least one drive unit, each drive unit comprises: a plurality of drivers cascaded in sequence from a first driver to a last driver, and the control method comprises: The first driver of the drive unit receives a read-back instruction issued by the controller, and generates a corresponding read-back instruction; The read-back instruction passes through the second driver to the last driver of the drive unit in sequence; The last driver transmits the corresponding read-back instruction back to the controller; wherein the transmitted-back read-back instruction comprises at least one data segment, and each data segment corresponds to one driver.

5. The data level readback control method of claim 4, wherein, The issued read-back instruction does not reserve a data segment, and the specific forming method of the data segment in the transmitted-back read-back instruction is: The driver expands its corresponding data segment to the frame tail of the corresponding read-back instruction.

6. The data level readback control method of claim 4 or 5, wherein, The issued read-back instruction comprises a frame header. The frame header comprises address information of a start-end driver requiring read-back and address information of a terminal-end driver requiring read-back; or The frame header comprises address information of a start-end driver requiring read-back and a number of drivers requiring read-back.

7. A data level readback control device, characterized by, Each controller corresponds to at least one drive unit, each drive unit comprises: a plurality of drivers cascaded in sequence from a first driver to a last driver; and the control device comprises: A read-back instruction issuing module, configured to issue a read-back instruction, so that the read-back instruction passes through the first driver to the last driver of the drive unit in sequence; A read-back instruction receiving module, configured to receive the read-back instruction transmitted back from the last driver of the drive unit, wherein the transmitted-back read-back instruction comprises at least one data segment, and each data segment corresponds to one driver.

8. The data level back read control device of claim 7, wherein, Further comprising: An information expanding module, configured to expand the data segment corresponding to the driver to the frame tail of the corresponding read-back instruction.

9. A display system characterized by, Comprise: A controller; A drive unit, each controller corresponds to at least one drive unit, each drive unit comprises: a plurality of drivers cascaded in sequence from a first driver to a last driver; A data-level read-back control device, the data-level read-back control device is the data-level read-back control device of claim 7 or 8.

10. An electronic device, comprising: Comprise: A processor; And a memory for storing processor-executable instructions; The processor implements the steps of the method in any of claims 1-6 by running the executable instructions.

11. A storage medium having stored thereon a computer program, characterized in that The computer program, when executed by the processor, implements the steps of the method in any of claims 1-6.

Images