Image data processing method and device
By processing even-line and odd-line image data respectively in the synchronous FIFO controller and using even-line and odd-line buffers for access, the problem that the synchronous FIFO controller cannot process z-font image data is solved, reducing system complexity and function This improves image data processing efficiency.
Patent Information
- Application Number
- CN202411223216.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-03
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2044-09-03
AI Technical Summary
The synchronous FIFO controller cannot process the z-font image data, resulting in the later-stage image processing module requiring additional cache, increasing system complexity and power consumption.
By reading and buffering even-line and odd-line image data in memory, and using even-line buffers and odd-line buffers for access, it is ensured that the later-level image processing module can read image data on demand.
It reduces system complexity and power consumption, improves the efficiency of image data processing, and supports the processing of z-shaped image data without additional cache.
Smart Images

Figure CN118735766B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of image data processing, and in particular to an image data processing method and device. Background Art
[0002] A synchronous First In First Out (FIFO) controller is a circuit or module used to control the first-in-first-out storage and transmission of data, and can provide a buffer between the memory and the subsequent image processing module. The synchronous FIFO controller can read image data from the memory and cache it in a First In First Out (FIFO) buffer so that the subsequent image processing module can read the image data on demand, improving the stability and efficiency of the data flow.
[0003] However, the above-mentioned synchronous FIFO controller can only process by row and cannot process zigzag image data, such as frame buffer decompression data (Frame Buffer De-Compression, FBDC). If the synchronous FIFO controller does not distinguish between odd-row or even-row image data in the zigzag image data for processing, the post-stage image processing module needs to add additional cache to split the zigzag data, thereby increasing the area and power consumption of the system, and the control circuit for splitting the zigzag image data is more complicated, thereby increasing the complexity of the system. Summary of the invention
[0004] The present application provides an image data processing method and device to solve the problem that a synchronous FIFO controller cannot process zigzag image data.
[0005] In a first aspect, the present application provides an image data processing method, the method comprising:
[0006] Reading row image data of image data to be processed from the memory;
[0007] Cache the even-row image data in the even-row buffer, and cache the odd-row image data in the odd-row buffer, wherein the even-row image data is pixel data located in the even-numbered rows of the image data to be processed, and the odd-row image data is pixel data located in the odd-numbered rows of the image data to be processed;
[0008] Reading the even-line image data in the even-line buffer, and reading the odd-line image data in the odd-line buffer;
[0009] The even-row image data and the odd-row image data are sent to a subsequent image processing module.
[0010] In an optional implementation, the step of caching the even-line image data into an even-line buffer, and caching the odd-line image data into an odd-line buffer, further includes:
[0011] Reading a line of even-line image data in the memory;
[0012] Buffering a row of the even-row image data into the even-row buffer;
[0013] Reading an odd-row image data in a memory;
[0014] A row of the odd-row image data is cached in the odd-row buffer, and after the cache is completed, the step of reading a row of the even-row image data in the memory is performed again until the cache of the image data to be processed is completed.
[0015] In an optional implementation manner, the step of reading the even line image data in the even line buffer and reading the odd line image data in the odd line buffer further includes:
[0016] Reading a line of the even-line image data in the even-line buffer;
[0017] A line of the odd-line image data is read in the odd-line buffer, and after the reading is completed, a step of reading a line of the even-line image data in the even-line buffer is performed again until the image data to be processed is read completely.
[0018] In an optional embodiment, the method further comprises:
[0019] Reading compressed data from a memory, wherein the compressed data is data obtained after compressing the image data to be processed;
[0020] Performing decompression processing on the compressed data to obtain decompressed data, the decompressed data comprising a plurality of decompressed data units, the decompressed data units comprising pixel points located in even-numbered rows in the image data to be processed and pixel points located in odd-numbered rows in the image data to be processed;
[0021] Buffering the pixels located in the even-numbered rows in the decompressed data unit into an even-row buffer;
[0022] The pixels in the odd rows of the decompressed data unit are cached in the odd row cache, and after the caching is completed, the step of caching the pixels in the even rows of the decompressed data unit in the even row cache is performed again until the decompressed data is cached.
[0023] In an optional implementation manner, the step of caching the pixels located in the even-numbered rows in the decompressed data unit into the even-row buffer further includes:
[0024] Setting a count value of a first counter to 0, wherein the first counter is used to count pixels;
[0025] Cache the pixels in the decompressed data unit to the even-row buffer, and control the count value of the first counter to increase until the count value of the first counter reaches a target count value, the target count value being the number of pixels in the decompressed data unit located in the same row, and the number of pixels in the even-row of the decompressed data unit is equal to the number of pixels in the odd-row;
[0026] The step of caching the pixels located in odd rows in the decompressed data unit into an odd row buffer further includes:
[0027] Setting the count value of the first counter to 0;
[0028] The pixels in the decompressed data unit are cached in the odd row cache, and the count value of the first counter is controlled to increase until the count value of the first counter reaches a target count value, which is the number of pixels in the decompressed data unit located in odd rows.
[0029] In an optional embodiment, the method further comprises:
[0030] Setting a second counter, wherein the second counter is used to count the number of pixels located in even-numbered rows or the number of pixels located in odd-numbered rows in the decompressed data unit;
[0031] When the target count value of pixels is cached in the even row buffer, the count value of the second counter is controlled to be set to 1, and the pixels in the decompressed data unit are cached in the odd row buffer;
[0032] When the target count value of pixels is cached in the odd-row buffer, the count value of the second counter is controlled to be set to 0, and the pixels in the decompressed data unit are cached in the even-row buffer.
[0033] In an optional embodiment, the method further comprises:
[0034] Setting a third counter and a fourth counter, wherein the third counter is used to count the number of row pixels, and the fourth counter is used to count the number of rows read;
[0035] Reading pixel points in the even-row buffer row by row, and controlling the count value of the third counter and the count value of the fourth counter to increase;
[0036] When the count value of the third counter is the number of row pixels and the count value of the fourth counter is an odd number, the count value of the third counter is set to 0; the number of row pixels is the number of pixel points in a row in the image data to be processed;
[0037] Reading pixel points row by row in the odd row buffer, and controlling the count value of the third counter and the count value of the fourth counter to increase;
[0038] When the count value of the third counter is the number of row pixels and the count value of the fourth counter is an even number, setting the count value of the third counter to 0;
[0039] The step of reading pixel points row by row in the even row buffer is performed again.
[0040] In an optional implementation manner, the image data to be processed includes brightness component data and chrominance component data, and further includes:
[0041] Cache the even-row brightness component data in an even-row buffer, and cache the odd-row brightness component data in an odd-row buffer; the even-row brightness component data is the brightness component data located in the even-numbered rows of the image data to be processed, and the odd-row brightness component data is the brightness component data located in the odd-numbered rows of the image data to be processed;
[0042] Reading the even-line brightness component data in the even-line buffer, and reading the odd-line brightness component data in the odd-line buffer;
[0043] Sending the even-row brightness component data and the odd-row brightness component data to a subsequent image processing module;
[0044] Cache the even-row chroma component data in an even-row buffer, and cache the luminance component data of the odd-row chroma component data in an odd-row buffer; the even-row luminance component data is the chroma component data located in the even-numbered rows of the image data to be processed, and the odd-row luminance component data is the chroma component data located in the odd-numbered rows of the image data to be processed;
[0045] Reading the even-line chrominance component data in the even-line buffer, and reading the odd-line chrominance component data in the odd-line buffer;
[0046] The even-row chrominance component data and the odd-row chrominance component data are sent to a subsequent image processing module.
[0047] In an optional implementation manner, the step of reading the even line chrominance component data in the even line buffer and reading the odd line chrominance component data in the odd line buffer, the method further comprises:
[0048] Reading the even-row chrominance component data of the current row in the even-row buffer;
[0049] After reading two lines of the current even-line chrominance component data, reading the current odd-line chrominance component data in the odd-line buffer;
[0050] After reading the chrominance component data of the odd lines of the current line of 2 lines, reading the image data of the next even line in the even line buffer until the reading of the chrominance component data is completed;
[0051] The step of caching the even-row chrominance component data into the even-row buffer and caching the luminance component data of the odd-row chrominance component data into the odd-row buffer also includes:
[0052] After reading the even-row chrominance component data of the current row of 2 rows, buffering the even-row chrominance component data of the next row into the even-row buffer;
[0053] After reading 2 lines of the odd-line chrominance component data of the current line, buffering the odd-line chrominance component data of the next line into the odd-line buffer.
[0054] In an optional embodiment, the method further comprises:
[0055] Setting a fifth counter and a sixth counter, wherein the fifth counter is used to count the number of times a single line of chrominance component data is read, and the sixth counter is used to count the number of lines read;
[0056] Reading the even-row chrominance component data of the current row in the even-row buffer, and controlling the count value of the fifth counter to increase;
[0057] When the count value of the fifth counter is 2, the count value of the sixth counter is set to 1;
[0058] The count value of the fifth counter is set to 0, the odd-row chrominance component data of the current row is read from the odd-row buffer, and the count value of the fifth counter is controlled to increase;
[0059] When the count value of the fifth counter is 2, the count value of the sixth counter is set to 0;
[0060] The count value of the fifth counter is set to 0, and the next line of even-line image data is read from the even-line buffer.
[0061] In a second aspect, the present application provides an image data processing device, the image data processing device comprising an even row buffer, an even row write controller, an even row read controller, an odd row buffer, an odd row write controller and an odd row read controller;
[0062] The even row write controller is configured as:
[0063] Reading even-row image data of the image data to be processed from the memory; the even-row image data is pixel data located in even-numbered rows of the image data to be processed;
[0064] Buffering the even-row image data into the even-row buffer;
[0065] The odd row write controller is configured as:
[0066] Reading odd-row image data of the image data to be processed from the memory; the odd-row image data is pixel data located in odd-numbered rows of the image data to be processed;
[0067] Buffering the odd-row image data into the odd-row buffer;
[0068] The even row read controller is configured as:
[0069] reading the even-line image data in the even-line buffer;
[0070] Sending the even-row image data to a subsequent image processing module;
[0071] The odd row read controller is configured as:
[0072] Reading the odd-row image data in the odd-row buffer;
[0073] The odd-row image data is sent to a subsequent image processing module.
[0074] In an optional embodiment, the image data processing device further includes a selector, the selector including a first input port, a second input port, a selection port and an output port; the first input port is connected to the even row buffer; the second input port is connected to the odd row buffer; the output port is connected to the post-stage image processing module; the selection port is connected to the even row read controller and the odd row read controller;
[0075] The even row read controller is configured as:
[0076] Input a first signal to the selector through the selection port, so that the selector outputs the even-line image data in the even-line buffer to the subsequent image processing module through the output port;
[0077] The odd row read controller is configured as:
[0078] A second signal is input to the selector through the selection port, so that the selector outputs the odd-row image data in the odd-row buffer to the subsequent image processing module through the output port.
[0079] It can be seen from the above technical solutions that the present application provides an image data processing method and device. When performing a write operation, the method can read row image data of the image data to be processed from the memory, cache the even row image data to the even row buffer, and cache the odd row image data to the odd row buffer. The even row image data is the pixel data located in the even rows of the image data to be processed, and the odd row image data is the pixel data located in the odd rows of the image data to be processed. When performing a read operation, the even row image data can be read in the even row buffer, and the odd row image data can be read in the odd row buffer, and the even row image data and the odd row image data can be sent to the subsequent image processing module. The method accesses the even row image data and the odd row image data respectively through the even row buffer and the odd row buffer, which is convenient for use by the subsequent module. BRIEF DESCRIPTION OF THE DRAWINGS
[0080] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0081] Figure 1 A schematic diagram of the architecture of an image data processing device provided in an embodiment of the present application;
[0082] Figure 2 A schematic diagram of a read operation provided in an embodiment of the present application;
[0083] Figure 3 A schematic diagram of a write operation provided in an embodiment of the present application;
[0084] Figure 4 A schematic diagram of a write operation of decompressed data provided in an embodiment of the present application;
[0085] Figure 5 A schematic diagram of another architecture of an image data processing device provided in an embodiment of the present application;
[0086] Figure 6 A schematic diagram of the read and write operations of image format conversion provided in an embodiment of the present application;
[0087] Figure 7 A schematic diagram of the read and write operations for decompressed data image format conversion provided by an embodiment of the present application;
[0088] Figure 8 A connection diagram of a selector provided in an embodiment of the present application. DETAILED DESCRIPTION
[0089] The embodiments will be described in detail below, and examples thereof are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation methods described in the following embodiments do not represent all implementation methods consistent with the present application. They are only examples of systems and methods consistent with some aspects of the present application.
[0090] Image data includes RAW data, RGB data, YUV data, frame buffer compression data (Frame Buffer Compression, FBC), etc., where RAW data or RGB data is stored in an area of memory (such as double data rate synchronous dynamic random access memory (Double Data Rate, DDR)). For YUV data, since YUV data contains two components, Y (brightness) and UV (chrominance), they need to be stored in different areas of the memory respectively. For FBC data, FBC data in YUV format contains two components, Y (brightness) and UV (chrominance), which are stored in different areas of the memory respectively, and FBC data in non-YUV format is stored in one area of the memory.
[0091] A synchronous First In First Out (FIFO) controller is a circuit or module used to control the first-in-first-out storage and transmission of data, and can provide a buffer between the memory and the subsequent image processing module. The synchronous FIFO controller can read image data from the memory and cache it in a First In First Out (FIFO) buffer so that the subsequent image processing module can read the image data on demand, improving the stability and efficiency of the data flow.
[0092] However, the above-mentioned synchronous FIFO controller can only process by row and cannot process zigzag image data, such as frame buffer decompression data (Frame Buffer De-Compression, FBDC), wherein the zigzag image data refers to 2N image data per piece, including N even-row image data and N odd-row image data. If the synchronous FIFO controller does not distinguish between odd-row or even-row image data in the zigzag image data for processing, the subsequent image processing module needs to add additional cache to split the zigzag data, thereby increasing the area and power consumption of the system, and the control circuit for splitting the zigzag image data is more complicated.
[0093] For image data in formats such as YUV422 and YUV444, directly storing them in the memory will take up a lot of storage space. In addition, for converting image data in YUV420 format into image data in YUV422 format, or converting data in YUV422 format into data in YUV444 format, the post-stage image processing module needs to add additional row cache for data conversion, thereby increasing the area and power consumption of the system.
[0094] Therefore, in order to solve the above problems, some embodiments of the present application provide an image data processing device. Figure 1 As shown, Figure 1 The schematic diagram of the architecture of the image data processing device provided in the embodiment of the present application includes two synchronous FIFO controllers. The access of even-row image data and odd-row image data is controlled by the two synchronous FIFO controllers respectively. That is, the image data interface conversion device includes an even-row buffer 110, an even-row write controller 120, an even-row read controller 130, an odd-row buffer 210, an odd-row write controller 220 and an odd-row read controller 230.
[0095] For the write operation of the synchronous FIFO controller, the even-row write controller 120 reads the even-row image data of the image data to be processed from the memory and buffers the even-row image data to the even-row buffer 110. The even-row image data is pixel data located in even-numbered rows of the image data to be processed.
[0096] The odd-row write controller 220 reads the odd-row image data of the image data to be processed from the memory, and buffers the odd-row image data to the odd-row buffer 210. The odd-row image data is pixel data located in odd-numbered rows of the image data to be processed.
[0097] For the read operation of the synchronous FIFO controller, the even-line read controller 130 reads the even-line image data from the even-line buffer 110 and sends the even-line image data to the subsequent image processing module.
[0098] The odd-row read controller 230 reads the odd-row image data in the odd-row buffer 210 and sends the odd-row image data to a subsequent image processing module.
[0099] In some embodiments, the synchronous FIFO controller caches and reads even-row image data and odd-row image data by row. For the write operation of the synchronous FIFO controller, the even-row write controller 120 reads a row of even-row image data in the memory, caches a row of even-row image data to the even-row buffer 110, and switches to the odd-row write controller 220 after the caching is completed.
[0100] The odd row write controller 220 reads a row of odd row image data in the memory, caches a row of odd row image data to the odd row cache 210, and after the caching is completed, switches to the even row write controller 120, and the even row write controller 120 again executes the step of reading a row of even row image data in the memory until the image data to be processed is cached.
[0101] For the read operation of the synchronous FIFO controller, the even row read controller 130 reads one row of even row image data in the even row buffer 110, and after the reading is completed, switches to the odd row read controller 230. The odd row read controller 230 reads one row of odd row image data in the odd row buffer 210, and after the reading is completed, switches to the even row read controller 130, and the even row read controller 130 again performs the step of reading one row of even row image data in the even row buffer 110 until the image data to be processed is read.
[0102] For example, for image data such as RAW data, RGB data, and FBC data, the image data includes 2n lines of image data, such as Figure 2 As shown, for the write operation of the synchronous FIFO controller, the even row write controller 120 first caches the image data of row 0 in the even row buffer 110, and when the image data of row 0 is cached, it switches to the odd row write controller 220. The odd row write controller 220 caches the image data of row 1 in the odd row buffer 210, and when the image data of row 1 is cached, it switches to the even row write controller 120 again, and the even row write controller 120 caches the image data of row 2 in the even row buffer 110, and so on, until the odd row write controller 220 caches the image data of row 2n-1 in the odd row buffer 210, and when the image data of row 2n-1 is cached, the image data cache is completed.
[0103] Similarly, if Figure 3 As shown, for the read operation of the synchronous FIFO controller, the even row read controller 130 first reads the 0th row image data in the even row buffer 110, and when the 0th row image data is read, it switches to the odd row read controller 230. The odd row read controller 230 reads the 1st row image data in the odd row buffer 210, and when the 1st row image data is read, it switches to the even row read controller 130, and the even row read controller 130 reads the 2nd row image data in the even row buffer 110, and so on, until the odd row read controller 230 reads the 2n-1th row image data in the odd row buffer 210, and when the 2n-1th row image data is read, the image data reading is completed.
[0104] In some embodiments, for the convenience of storage, compressed data is stored in the memory, and the compressed data is data obtained after the image data to be processed is compressed. A decompression module can be set between the memory and the image data processing device, and the decompression module performs decompression processing on the compressed data according to preset units to obtain decompressed data. The decompressed data includes multiple decompressed data units, and the decompressed data units include pixel points located in even rows of the image data to be processed and pixel points located in odd rows of the image data to be processed. That is, the compressed data is decompressed for multiple times, and the decompressed data unit is a single decompressed data obtained by one decompression process.
[0105] The even row write controller 120 caches the pixel points located in the even row of the decompressed data unit to the even row buffer 110, and after the cache is completed, switches to the odd row write controller 220. The odd row write controller 220 caches the pixel points located in the odd row of the decompressed data unit to the odd row buffer 210, and after the cache is completed, switches to the even row write controller 120, and the even row write controller 120 again executes the step of caching the pixel points located in the even row of the decompressed data unit to the even row buffer 110 until the decompressed data is cached.
[0106] In some embodiments, in order to distinguish the pixels of the odd and even rows of image data in the decompressed data unit, a first counter may be set, and the first counter is used to count the pixels. That is, for the read operation of the synchronous FIFO controller, the even row read controller 130 may set the count value of the first counter to 0, cache the pixels in the decompressed data unit to the even row buffer 110, and control the count value of the first counter to increase until the count value of the first counter is the target count value, and the target count value is the number of pixels in the same row in the decompressed data unit, and the number of pixels in the even rows in the decompressed data unit is equal to the number of pixels in the odd rows. Thus, the pixels in the even rows in the decompressed data unit are cached.
[0107] Similarly, after switching to the odd-row read controller 230, the odd-row read controller 230 can set the count value of the first counter to 0, continue to cache the pixels in the decompressed data unit to the odd-row buffer 210, and control the count value of the first counter to increase until the count value of the first counter reaches the target count value, thereby completing the cache of the pixels in the odd-rows in the decompressed data unit.
[0108] In some embodiments, in order to distinguish between odd and even lines of image data in the decompressed data unit, a second counter may be set, and the second counter is used to count the number of pixels located in the even lines or the number of pixels located in the odd lines in the decompressed data unit. That is, after the target count value of pixels is cached in the even line buffer 110, the even line write controller 120 controls the count value of the second counter to be set to 1, indicating that subsequent pixels need to be written to the odd line buffer 210. After the target count value of pixels is cached in the odd line buffer 210, the odd line write controller 220 controls the count value of the second counter to be set to 0, indicating that subsequent pixels need to be written to the even line buffer 110.
[0109] That is, the count value of the second counter will be flipped based on the count value in the first counter, and when the count value of the first counter becomes the target count value, the count value of the second counter is 1. When the count value of the first counter becomes the target count value next time, the count value of the second counter is 0.
[0110] Therefore, when the second counter is 1, the controller switches to the odd row write controller 220, and the odd row write controller 220 caches the pixels in the decompressed data unit to the odd row buffer 210. When the second counter is 0, the controller switches to the even row write controller 120, and the even row write controller 120 caches the pixels in the decompressed data unit to the even row buffer 110.
[0111] In some embodiments, for the read operation of the synchronous FIFO controller, a third counter and a fourth counter may be set, the third counter is used to count the row pixels, and the fourth counter is used to count the number of rows read. The even row read controller 130 reads the pixels in the even row buffer 110 by row, and controls the count value of the third counter and the count value of the fourth counter to increase. When the count value of the third counter is the number of row pixels and the count value of the fourth counter is an odd number, the count value of the third counter is set to 0, indicating that a row of even row image data has been read, and the subsequent pixels need to be written into the odd row buffer 210, then switch to the odd row read controller 230.
[0112] The odd-row read controller 230 reads pixels in the odd-row buffer 210 by row, and controls the count value of the third counter to increase. When the count value of the third counter is the number of row pixels and the count value of the fourth counter is an even number, the count value of the third counter is set to 0, indicating that a row of odd-row image data has been read. If subsequent pixels need to be written into the even-row buffer 110, the controller switches to the even-row read controller 130, and the even-row read controller 130 again executes the step of reading pixels in the even-row buffer 110 by row until the data to be processed is read.
[0113] For example, for the decompressed zigzag FBDC image data, each piece of FBDC image data includes 2N pixel data, wherein the first N pixel data are even-row image data, and the last N pixel data are odd-row image data. Therefore, a counter can be set to count N to distinguish the number of N pixels in the odd-row and even-row image data, and a counter can also be set to count the number of pixels in a single row of FBDC image data to distinguish the odd-row and even-row image data.
[0114] A first counter, a second counter, a third counter and a fourth counter may be set. In a write operation, the first counter counts N pixels to distinguish the number of N pixels in odd and even rows. The second counter counts the number of pixels in a single row of image data to distinguish between odd and even rows. In a read operation, the third counter counts row pixels to distinguish between pixels in odd and even rows, and the fourth counter counts the number of rows read to distinguish between odd and even rows.
[0115] like Figure 4 As shown, for the write operation of the synchronous FIFO controller, the even-row write controller 120 starts the first counter and the second counter, and caches pixels in the even-row buffer 110, and the count value of the first counter increases with the number of cached pixels. When the count value of the first counter becomes N and the count value of the second counter becomes 1, it means that the first N pixels of the first stroke of row 0 have been cached in the even-row buffer 110, then the controller switches to the odd-row write controller 220, and sets the count value of the first counter to 0.
[0116] The odd-row write controller 220 continues to cache pixels in the odd-row buffer 210, and the count value of the first counter increases with the amount of cached image data. When the count value of the first counter becomes N and the count value of the second counter becomes 0, it means that the odd-row buffer 210 has cached N pixels after the first stroke of the first row, and then switches to the even-row write controller 120, and sets the count value of the first counter to 0.
[0117] The even row write controller 120 continues to cache the first N pixels of the second stroke of the image data in row 0 in the even row buffer 110, and after the first N pixels of the second stroke of row 0 are cached, it switches to the odd row write controller 220. The odd row write controller 220 continues to cache the last N pixels of the second stroke of row 1 in the odd row buffer 210, and after the last N pixels of the second stroke of row 1 are cached, it switches to the even row write controller 120.
[0118] This goes back and forth, assuming that the number of pixels in a single row of odd and even row image data is 4N, when the even row write controller 120 caches the first N image data of the fourth entry of row 0 in the even row buffer 110, it means that the image data of row 0 has been cached. Similarly, when the odd row write controller 220 caches the N image data after the fourth entry of row 1 in the odd row buffer 210, it means that the image data of row 1 has been cached.
[0119] Based on the above steps, the decompressed data units are split and cached until the odd row write controller 220 completes caching of the 2n-1th row of image data in the odd row buffer 210, and the image data caching is completed.
[0120] For the read operation of the synchronous FIFO controller, the even row read controller 130 starts the third counter and the fourth counter, and reads the image data of row 0 in the even row buffer 110. When the count value of the third counter becomes 4N and the count value of the fourth counter becomes 1 (odd number), it indicates that the reading of the image data of row 0 is completed, and then switches to the odd row read controller 230, and sets the count value of the third counter to 0.
[0121] The odd-row read controller 230 reads the first row of image data from the odd-row buffer 210. When the count value of the third counter becomes 4N and the count value of the fourth counter becomes 2 (an even number), it indicates that the reading of the first row of image data is completed, and the controller switches to the even-row read controller 130, and sets the count value of the third counter to 0. The even-row read controller 130 reads the second row of image data from the even-row buffer 110, and repeats this process until the odd-row read controller 230 reads the 2n-1th row of image data from the odd-row buffer 210. When the reading of the 2n-1th row of image data is completed, the image data reading is completed.
[0122] Since each FBDC data contains odd and even row image data, in the synchronous read operation, the even row read controller 130 needs to read all the row image data in the even row buffer 110, and the odd row read controller 230 needs to read the Nth pixel data in the odd row buffer 210 before the synchronous FIFO controller requests the decompressed FBDC data from the front-level FBDC module.
[0123] In some embodiments, for image data in YUV format, the image data to be processed includes brightness component (Y) data and chrominance component (UV) data. In order to facilitate the processing of image data, the brightness component data and the chrominance component data can be processed separately. Figure 5 As shown, Figure 5Another schematic diagram of the architecture of an image data processing device provided in an embodiment of the present application, wherein the image data processing device includes four synchronous FIFO controllers. Two synchronous FIFO controllers are used to control the access of even-row luminance component data and odd-row luminance component data respectively. Two synchronous FIFO controllers are used to control the access of even-row chrominance component data and odd-row chrominance component data respectively.
[0124] For the write operation of the brightness component data, the even row write controller 120 reads the even row brightness component data in the memory, caches the even row brightness component data to the even row buffer 110, and after the cache is completed, switches to the odd row write controller 220. The even row brightness component data is the brightness component data located in the even row of the image data to be processed.
[0125] After switching to the odd-row write controller 220, the odd-row write controller 220 reads the odd-row brightness component data in the memory, caches the odd-row brightness component data to the odd-row buffer 210, and after the cache is completed, switches to the even-row write controller 120. The odd-row brightness component data is the brightness component data located in the odd-numbered rows of the image data to be processed. This process is repeated until the cache of the image data to be processed is completed.
[0126] For the read operation of the brightness component data, the even row read controller 130 reads the even row brightness component data in the even row buffer 110, and after the reading is completed, switches to the odd row read controller 230. The odd row read controller 230 reads the odd row brightness component data in the odd row buffer 210, and after the reading is completed, switches to the even row read controller 130, and so on, until the image data to be processed is read.
[0127] Similarly, for the write operation of the chrominance component data, the even row write controller 120 reads the even row chrominance component data in the memory, caches the even row chrominance component data to the even row buffer 110, and after the cache is completed, switches to the odd row write controller 220. The even row chrominance component data is the chrominance component data located in the even rows of the image data to be processed.
[0128] After switching to the odd-row write controller 220, the odd-row write controller 220 reads the odd-row chroma component data in the memory, caches the odd-row chroma component data to the odd-row buffer 210, and after the cache is completed, switches to the even-row write controller 120. The odd-row chroma component data is the chroma component data located in the odd-numbered rows of the image data to be processed. This is repeated until the cache of the image data to be processed is completed.
[0129] For the read operation of the chrominance component data, the even row read controller 130 reads the even row chrominance component data in the even row buffer 110, and after the reading is completed, switches to the odd row read controller 230. The odd row read controller 230 reads the odd row chrominance component data in the odd row buffer 210, and after the reading is completed, switches to the even row read controller 130, and so on, until the image data to be processed is read.
[0130] In some embodiments, image format conversion of image data can be implemented during data access, such as conversion of YUV420 format to YUV422, YUV422 format to YUV444 format, etc. In this regard, in the step of reading the even line chromaticity component data of the even line in the even line buffer 110, the even line chromaticity component data of the current line is read in the even line buffer 110, and after reading 2 lines of the even line chromaticity component data of the current line, the controller 230 is switched to the odd line read controller.
[0131] In the step of reading the odd row chroma component data in the odd row buffer 210, the odd row read controller 230 reads the current row of odd row chroma component data in the odd row buffer 210. After reading 2 rows of the current row of odd row chroma component data, it switches to the even row read controller 130, and the even row read controller 130 reads the next row of even row image data in the even row buffer 110 until the chroma component data is read.
[0132] Since the odd and even row chrominance component data need to be read multiple times, in order to ensure that the data is read in the correct order, in the step of the even row write controller 120 caching the even row chrominance component data to the even row buffer 110, after the even row read controller 130 reads 2 rows of the current row of even row chrominance component data, the even row write controller 120 can cache the next row of even row chrominance component data to the even row buffer 110, and after the caching is completed, switch to the odd row write controller 220.
[0133] In the step where the odd row write controller 220 caches the brightness component data of the odd row chromaticity component data to the odd row buffer 210, after the odd row read controller 230 reads 2 rows of the current row odd row chromaticity component data, the odd row write controller 220 can cache the next row of odd row chromaticity component data to the odd row buffer 210, and after the caching is completed, switch to the even row write controller 120.
[0134] In some embodiments, in order to facilitate counting the number of reads, a fifth counter and a sixth counter may be set, the fifth counter is used to count the number of reads of a single row of chroma component data, and the sixth counter is used to count the number of rows read. The even row read controller 130 reads the even row chroma component data of the current row in the even row buffer 110, and controls the count value of the fifth counter to increase. When the count value of the fifth counter is 2, the count value of the sixth counter is set to 1, indicating that 2 rows of the even row chroma component data of the current row have been read, and then the controller switches to the odd row read controller 230, and the count value of the fifth counter is set to 0.
[0135] After switching to the odd row read controller 230, the odd row read controller 230 reads the odd row chroma component data of the current row in the odd row buffer 210, and controls the count value of the fifth counter to increase. When the count value of the fifth counter is 2, the count value of the fifth counter is set to 0, indicating that 2 rows of odd row chroma component data of the current row have been read, and then switching to the even row read controller 130, and setting the count value of the sixth counter to 0. The even row read controller 130 reads the next row of even row image data in the even row buffer 110.
[0136] For example, Figure 6 As shown, taking the conversion of YUV420 format to YUV422 format as an example, since the format conversion process requires multiplexing of chrominance component (UV) image data to realize the conversion of YUV420 data to YUV422 data, it does not involve brightness component (Y) image data. For the read and write operations of Y image data, please refer to Figure 2 , Figure 3 The following specifically describes the read and write operations of UV image data during format conversion.
[0137] For the write operation of the synchronous FIFO controller, the even row write controller 120 caches the UV image data of row 0 in the even row buffer 110 , and switches to the odd row write controller 220 after the cache of the UV image data of row 0 is completed.
[0138] The odd-row write controller 220 caches the first row of UV image data in the odd-row buffer 210. When the cache of the first row of UV image data is completed, it switches to the even-row write controller 120. When the even-row read controller 130 has finished reading the 0th row of UV image data for the second time and the odd-row buffer has finished caching the first row of UV image data, the even-row write controller 120 can cache the second row of UV image data in the even-row buffer 110. When the cache of the second row of UV image data is completed, it switches to the odd-row write controller 220. Similarly, when the odd-row read controller 230 has finished reading the first row of UV image data for the second time and the even-row read controller 130 has finished caching the second row of UV image data, the odd-row write controller 220 can cache the third row of UV image data in the odd-row buffer 210. This process is repeated until the odd-row write controller 220 caches the 2n-1th row of UV image data in the odd-row buffer 210. When the cache of the 2n-1th row of UV image data is completed, the image data cache is completed.
[0139] For the read operation of the synchronous FIFO controller, since the image data in the YUV420 format is converted into the image data in the YUV422 format, each line of UV image data needs to be multiplexed once.
[0140] The even-row read controller 130 starts the fifth counter and the sixth counter, and reads the UV image data of row 0 twice from the even-row buffer 110. When the count value of the fifth counter becomes 2 and the count value of the sixth counter becomes 1, it indicates that the image data of row 0 has been read twice, and then the controller switches to the odd-row read controller 230, and sets the count value of the fifth counter to 0. The odd-row read controller 230 reads the UV image data of row 1 twice from the odd-row buffer 210. When the count value of the fifth counter becomes 2 and the count value of the sixth counter becomes 0, it indicates that the image data of row 1 has been read twice, and then the controller switches to the even-row read controller 130, and sets the count value of the fifth counter to 0, and then the even-row read controller 130 reads the UV image data of row 2 twice from the even-row buffer 110. This process is repeated until the odd-row read controller 230 reads the UV image data of row 2n-1 twice from the odd-row buffer 210. When the UV image data of row 2n-1 has been read twice, the image data reading is completed.
[0141] In the read operation of the synchronous FIFO controller, multiple address pointers can be set to distinguish different read operations, and the address pointers are used to indicate the current position of the data in the buffer.
[0142] For the two readings of the UV image data of the 0th row, address pointer 0 and address pointer 1 may be set, and address pointer 0 is used to indicate the position of the UV image data of the 0th row in the even row buffer 110 for the first reading. Address pointer 1 is used to indicate the position of the UV image data of the 0th row in the even row buffer 110 for the second reading. The even row read controller 130 uses address pointer 0 to read the UV image data of the 0th row in the even row buffer 110 for the first time. When the first reading of the image data of the 0th row is completed, the even row read controller 130 uses address pointer 1 to read the UV image data of the 0th row in the even row buffer 110 for the second time. When the second reading of the image data of the 0th row is completed, the multiplexing of the UV image data of the 0th row is completed, and the controller 230 is switched to the odd row read controller 230.
[0143] Similarly, for the two readings of the first line of UV image data, address pointer 2 and address pointer 3 can be set, and address pointer 2 is used to indicate the position of the first line of UV image data in the odd line buffer 210 for the first reading. Address pointer 3 is used to indicate the position of the first line of UV image data in the odd line buffer 210 for the second reading. The odd line read controller 230 uses address pointer 2 to read the first line of UV image data in the odd line buffer 210 for the first time. After the first reading of the first line of image data is completed, the odd line read controller 230 uses address pointer 3 to read the first line of UV image data in the odd line buffer 210 for the second time. When the second reading of the first line of image data is completed, the first line of UV image data is multiplexed and switched to the even line read controller 130.
[0144] The reading operation of UV image data of other rows can refer to the above steps and will not be described in detail here.
[0145] It should be noted that in the YUV420 format, each pixel has one Y component, and every four pixels have one group of UV components. In the YUV422 format, each pixel has one Y component, and every two pixels have one group of UV components. In the YUV444 format, each pixel has one Y component and one group of UV components. For the conversion of the YUV420 format to the YUV422 format, the UV image data needs to be read twice in the read operation of the synchronous FIFO controller. For the conversion of the YUV422 format to the YUV444 format, the UV image data needs to be read twice. The step flow of converting the YUV422 format to the YUV444 format can refer to the steps of converting the YUV420 format to the YUV422 format mentioned above.
[0146] For example, Figure 7 As shown, for the z-shaped FBDC image data, take the conversion of YUV420 format to YUV422 format as an example. For the read and write operations of Y image data, refer to Figure 4The following specifically describes the read and write operations of UV image data during format conversion. Each FBDC image data includes 2N UV image data, where the first N UV image data are even-row image data and the last N UV image data are odd-row image data.
[0147] For the write operation of the synchronous FIFO controller, according to the first counter and the second counter, the even row write controller 120 caches the first N UV image data of the 0th row in the even row buffer 110, and after the first N UV image data of the 0th row are cached, it switches to the odd row write controller 220.
[0148] The odd row write controller 220 caches the N UV image data after the first entry of the first row in the odd row buffer 210 according to the first counter and the second counter. After the cache of the N UV image data after the first entry of the first row is completed, the controller switches to the even row write controller 120. The even row write controller 120 caches the N UV image data before the second entry of the 0th row in the even row buffer 110.
[0149] This goes back and forth, assuming that the number of pixels in a single row of the odd and even rows of UV image data is 4N, when the even row write controller 120 caches the first N UV image data of the fourth entry of row 0 in the even row buffer 110, the cache of the image data of row 0 is completed. When the odd row write controller 220 caches the N image data after the fourth entry of row 1 in the odd row buffer 210, the cache of the image data of row 1 is completed.
[0150] Based on the above steps, the decompressed data units are split and cached until the odd row write controller 220 completes caching of the 2n-1th row of image data in the odd row buffer 210, and the image data caching is completed.
[0151] For the read operation of the synchronous FIFO controller, since the image data in the YUV420 format is converted into the image data in the YUV422 format, the UV data of each row also needs to be reused once. The even row read controller 130 uses the address pointer 0 to read the UV image data of row 0 in the even row buffer 110 for the first time according to the fifth counter and the sixth counter. After the first reading of the image data of row 0 is completed, the even row read controller 130 uses the address pointer 1 to read the UV image data of row 0 in the even row buffer 110 for the second time. When the second reading of the image data of row 0 is completed, the multiplexing of the UV image data of row 0 is completed and switched to the odd row read controller 230.
[0152] The odd-row read controller 230 uses the address pointer 2 to read the first row of UV image data in the odd-row buffer 210 for the first time. After the first row of image data is read, the odd-row read controller 230 uses the address pointer 3 to read the first row of UV image data in the odd-row buffer 210 for the second time. After the second row of image data is read, the first row of UV image data is multiplexed and switched to the even-row read controller 130. This process is repeated until all UV image data are read.
[0153] Since each FBDC data contains odd and even rows of UV image data, in the synchronous read operation, only after the odd row read controller 230 finishes reading the first row of UV image data for the second time can the even row write controller 120 and the odd row write controller 220 cache the second row of UV image data and the third row of UV image data in the even row buffer 110 and the odd row buffer 210, respectively.
[0154] This process is repeated until the odd-row read controller 230 reads the UV image data of the 2n-1th row twice from the odd-row buffer 210 . When the UV image data of the 2n-1th row is read twice, the image data reading is completed.
[0155] In some embodiments, in order to realize the selective output of data, the image data output by the odd-line buffer 210 and the even-line buffer 110 can use a two-to-one data selector to select whether to output the odd-line image data or the even-line image data. Figure 1 , Figure 8 As shown, the image data processing device further includes a selector 300, and the selector 300 includes a first input port A, a second input port B, a selection port C, and an output port D. The first input port A is connected to the even row buffer 110. The second input port B is connected to the odd row buffer 210. The output port D is connected to the post-stage image processing module. The selection port C is connected to the even row read controller 130 and the odd row read controller 230.
[0156] When the even-line read controller 130 reads the even-line image data in the even-line buffer 110 and needs to output the even-line image data, a first signal can be input to the selector 300 through the selection port C to connect the first input port A and the output port D in the selector 300, so that the selector 300 outputs the even-line image data in the even-line buffer 110 to the subsequent image processing module through the output port D.
[0157] When the odd-row read controller 230 reads the odd-row image data in the odd-row buffer 210 and needs to output the odd-row image data, a second signal can be input to the selector 300 through the selection port C to connect the second input port B in the selector 300 with the output port D, so that the selector 300 outputs the odd-row image data in the odd-row buffer 210 to the subsequent image processing module through the output port D.
[0158] In this embodiment, the image processing device supports the original synchronous FIFO function, and can cache the zigzag FBDC image data according to odd and even lines, which is beneficial to the use of the subsequent modules. At the same time, without adding additional line cache, image format conversion can be achieved, such as converting image data in YUV420 format into image data in YUV422 format, or converting image data in YUV422 format into image data in YUV444 format. The storage space occupancy of the memory is reduced, and the area and power consumption of the subsequent modules are reduced.
[0159] Based on the above-mentioned image data processing device, some embodiments of the present application also provide an image data processing method, which includes the following steps:
[0160] Reading row image data of image data to be processed from the memory;
[0161] Cache the even-row image data in the even-row buffer 110, and cache the odd-row image data in the odd-row buffer 210, wherein the even-row image data is pixel data located in the even-rows of the image data to be processed, and the odd-row image data is pixel data located in the odd-rows of the image data to be processed;
[0162] Reading the even line image data in the even line buffer 110, and reading the odd line image data in the odd line buffer 210;
[0163] The even-row image data and the odd-row image data are sent to a subsequent image processing module.
[0164] It can be known from the above technical scheme that the image data processing method and device provided by the above embodiment can read the row image data of the image data to be processed from the memory, cache the even row image data to the even row buffer, and cache the odd row image data to the odd row buffer when performing a write operation. The even row image data is the pixel data located in the even row of the image data to be processed, and the odd row image data is the pixel data located in the odd row of the image data to be processed. When performing a read operation, the even row image data can be read in the even row buffer, and the odd row image data can be read in the odd row buffer, and the even row image data and the odd row image data can be sent to the subsequent image processing module. The method accesses the even row image data and the odd row image data respectively through the even row buffer and the odd row buffer, so as to facilitate the use of the subsequent module.
[0165] Similar parts between the embodiments provided in this application can be referenced to each other. The specific implementation methods provided above are only a few examples under the general concept of this application and do not constitute a limitation on the protection scope of this application. For those skilled in the art, any other implementation methods expanded based on the scheme of this application without creative work belong to the protection scope of this application.
Claims
1. A method for processing image data, characterized in that: The method comprises: Reading row image data of image data to be processed from the memory; Cache the even-row image data in the even-row buffer, and cache the odd-row image data in the odd-row buffer, wherein the even-row image data is pixel data located in the even-numbered rows of the image data to be processed, and the odd-row image data is pixel data located in the odd-numbered rows of the image data to be processed; Reading the even-line image data in the even-line buffer, and reading the odd-line image data in the odd-line buffer; Sending the even-row image data and the odd-row image data to a subsequent image processing module; The method further comprises: Reading compressed data from a memory, wherein the compressed data is data obtained after compressing the image data to be processed; Performing decompression processing on the compressed data to obtain decompressed data, the decompressed data comprising a plurality of decompressed data units, the decompressed data units comprising pixel points located in even-numbered rows in the image data to be processed and pixel points located in odd-numbered rows in the image data to be processed; Buffering the pixels located in the even-numbered rows in the decompressed data unit into an even-row buffer; The pixels in the odd rows of the decompressed data unit are cached in the odd row cache, and after the caching is completed, the step of caching the pixels in the even rows of the decompressed data unit in the even row cache is performed again until the decompressed data is cached.
2. The image data processing method according to claim 1, characterized in that: The steps of caching the even-row image data into the even-row buffer and caching the odd-row image data into the odd-row buffer further include: Reading a line of even-line image data in the memory; Buffering a row of the even-row image data into the even-row buffer; Reading an odd-row image data in a memory; A row of the odd-row image data is cached in the odd-row buffer, and after the cache is completed, the step of reading a row of the even-row image data in the memory is performed again until the cache of the image data to be processed is completed.
3. The image data processing method according to claim 1, characterized in that: The step of reading the even line image data in the even line buffer and reading the odd line image data in the odd line buffer further includes: Reading a line of the even-line image data in the even-line buffer; A line of the odd-line image data is read in the odd-line buffer, and after the reading is completed, a step of reading a line of the even-line image data in the even-line buffer is performed again until the image data to be processed is read completely.
4. The image data processing method according to claim 1, characterized in that: The step of caching the pixel points located in the even-numbered rows in the decompressed data unit into the even-row buffer also includes: Setting a count value of a first counter to 0, wherein the first counter is used to count pixels; Cache the pixels in the decompressed data unit to the even-row buffer, and control the count value of the first counter to increase until the count value of the first counter reaches a target count value, the target count value being the number of pixels in the decompressed data unit located in the same row, and the number of pixels in the even-row of the decompressed data unit is equal to the number of pixels in the odd-row; The step of caching the pixels located in odd rows in the decompressed data unit into an odd row buffer further includes: Setting the count value of the first counter to 0; The pixel points in the decompressed data unit are cached in the odd row buffer, and the count value of the first counter is controlled to increase until the count value of the first counter reaches the target count value.
5. The image data processing method according to claim 4, characterized in that: The method further comprises: Setting a second counter, wherein the second counter is used to count the number of pixels located in even-numbered rows or the number of pixels located in odd-numbered rows in the decompressed data unit; When the target count value of pixels is cached in the even row buffer, the count value of the second counter is controlled to be set to 1, and the pixels in the decompressed data unit are cached in the odd row buffer; When the target count value of pixels is cached in the odd-row buffer, the count value of the second counter is controlled to be set to 0, and the pixels in the decompressed data unit are cached in the even-row buffer.
6. The image data processing method according to claim 5, characterized in that: The method further comprises: Setting a third counter and a fourth counter, wherein the third counter is used to count the number of row pixels, and the fourth counter is used to count the number of rows read; Reading pixel points in the even-row buffer row by row, and controlling the count value of the third counter and the count value of the fourth counter to increase; When the count value of the third counter is the number of row pixels and the count value of the fourth counter is an odd number, the count value of the third counter is set to 0; the number of row pixels is the number of pixel points in a row in the image data to be processed; Reading pixel points row by row in the odd row buffer, and controlling the count value of the third counter and the count value of the fourth counter to increase; When the count value of the third counter is the number of row pixels and the count value of the fourth counter is an even number, setting the count value of the third counter to 0; The step of reading pixel points row by row in the even row buffer is performed again.
7. The image data processing method according to claim 1, characterized in that: The image data to be processed includes brightness component data and chrominance component data, and also includes: Cache the even-row brightness component data in an even-row buffer, and cache the odd-row brightness component data in an odd-row buffer; the even-row brightness component data is the brightness component data located in the even-numbered rows of the image data to be processed, and the odd-row brightness component data is the brightness component data located in the odd-numbered rows of the image data to be processed; Reading the even-line brightness component data in the even-line buffer, and reading the odd-line brightness component data in the odd-line buffer; Sending the even-row brightness component data and the odd-row brightness component data to a subsequent image processing module; Cache the even-row chroma component data in an even-row buffer, and cache the luminance component data of the odd-row chroma component data in an odd-row buffer; the even-row luminance component data is the chroma component data located in the even-numbered rows of the image data to be processed, and the odd-row luminance component data is the chroma component data located in the odd-numbered rows of the image data to be processed; Reading the even-line chrominance component data in the even-line buffer, and reading the odd-line chrominance component data in the odd-line buffer; The even-row chrominance component data and the odd-row chrominance component data are sent to a subsequent image processing module.
8. The image data processing method according to claim 7, characterized in that: The method further comprises the steps of reading the even line chrominance component data in the even line buffer and reading the odd line chrominance component data in the odd line buffer: Reading the even-row chrominance component data of the current row in the even-row buffer; After reading two lines of the current even-line chrominance component data, reading the current odd-line chrominance component data in the odd-line buffer; After reading 2 lines of the odd-line chrominance component data of the current line, reading the next line of even-line image data in the even-line buffer until the reading of the chrominance component data is completed; The step of caching the even-row chrominance component data into the even-row buffer and caching the luminance component data of the odd-row chrominance component data into the odd-row buffer also includes: After reading the even-row chrominance component data of the current row of 2 rows, buffering the even-row chrominance component data of the next row into the even-row buffer; After reading 2 lines of the odd-line chrominance component data of the current line, buffering the odd-line chrominance component data of the next line into the odd-line buffer.
9. The image data processing method according to claim 8, characterized in that: The method further comprises: Setting a fifth counter and a sixth counter, wherein the fifth counter is used to count the number of times a single line of chrominance component data is read, and the sixth counter is used to count the number of lines read; Reading the even-row chrominance component data of the current row in the even-row buffer, and controlling the count value of the fifth counter to increase; When the count value of the fifth counter is 2, the count value of the sixth counter is set to 1; The count value of the fifth counter is set to 0, the odd-row chrominance component data of the current row is read from the odd-row buffer, and the count value of the fifth counter is controlled to increase; When the count value of the fifth counter is 2, the count value of the sixth counter is set to 0; The count value of the fifth counter is set to 0, and the next line of even-line image data is read from the even-line buffer.
10. An image data processing device, characterized in that: The image data processing device comprises an even row buffer, an even row write controller, an even row read controller, an odd row buffer, an odd row write controller, a decompression module and an odd row read controller; The even row write controller is configured as: Reading even-row image data of the image data to be processed from the memory; the even-row image data is pixel data located in even-numbered rows of the image data to be processed; Buffering the even-row image data into the even-row buffer; The odd row write controller is configured as: Reading odd-row image data of the image data to be processed from the memory; the odd-row image data is pixel data located in odd-numbered rows of the image data to be processed; Buffering the odd-row image data into the odd-row buffer; The even row read controller is configured as: reading the even-line image data in the even-line buffer; Sending the even-row image data to a subsequent image processing module; The odd row read controller is configured as: Reading the odd-row image data in the odd-row buffer; Sending the odd-row image data to a subsequent image processing module; The decompression module is configured as: Reading compressed data from a memory, wherein the compressed data is data obtained after compressing the image data to be processed; Performing decompression processing on the compressed data to obtain decompressed data, the decompressed data comprising a plurality of decompressed data units, the decompressed data units comprising pixel points located in even-numbered rows in the image data to be processed and pixel points located in odd-numbered rows in the image data to be processed; The even row write controller is also configured to: Cache the pixels located in the even rows in the decompressed data unit into the even row cache, and switch to the odd row write controller after the cache is completed; The odd row write controller is also configured to: The pixel points located in the odd rows in the decompressed data unit are cached to the odd row buffer, and after the caching is completed, the controller is switched to the even row write controller so that the even row write controller again executes the step of caching the pixel points located in the even rows in the decompressed data unit to the even row buffer until the decompressed data is cached.
11. The image data processing device according to claim 10, characterized in that: The image data processing device further includes a selector, the selector including a first input port, a second input port, a selection port and an output port; the first input port is connected to the even row buffer; the second input port is connected to the odd row buffer; the output port is connected to the post-stage image processing module; the selection port is connected to the even row read controller and the odd row read controller; The even row read controller is configured as: Input a first signal to the selector through the selection port, so that the selector outputs the even-line image data in the even-line buffer to the subsequent image processing module through the output port; The odd row read controller is configured as: A second signal is input to the selector through the selection port, so that the selector outputs the odd-row image data in the odd-row buffer to the subsequent image processing module through the output port.
Citation Information
Patent Citations
Image processing method, device and system and computer readable medium
CN112188280A
