The disclosed embodiments of the present invention relate to transmitting and receiving display data over a display interface, and more particularly, to a data processing apparatus for transmitting/receiving compression-related indication information via a display interface and related data processing method.
A display interface is disposed between a first chip and a second chip to transmit display data from the first chip to the second chip for further processing. For example, the first chip may be a host application processor, and the second chip may be a driver integrated circuit (IC). The display data may include image data, video data, graphic data, and/or OSD (on-screen display) data. Besides, the display data may be single view data for two-dimensional (2D) display or multiple view data for three-dimensional (3D) display. When a display panel supports a higher display resolution, 2D/3D display with higher resolution can be realized. Hence, the display data transmitted over the display interface would have a larger data size/data rate, which increases the power consumption of the display interface inevitably. If the host application processor and the driver IC are both located at a portable device (e.g., a smartphone) powered by a battery device, the battery life is shortened due to the increased power consumption of the display interface. Thus, there is a need for an innovative design which can effectively reduce the power consumption of the display interface.
In accordance with exemplary embodiments of the present invention, a data processing apparatus for transmitting/receiving compression-related indication information via a display interface and related data processing method are proposed.
According to a first aspect of the present invention, an exemplary data processing apparatus is disclosed. The exemplary data processing apparatus includes a compressor and an output interface. The compressor is arranged for generating a compressed display data by compressing a display data according to a compression algorithm. The output interface is arranged for appending first indication information in a first output bitstream, appending second indication information in a second output bitstream, and outputting the first output bitstream and the second output bitstream via a display interface, wherein the first output bitstream is derived from the compressed display data, the first indication information is set in response to the compression algorithm employed by the compressor, the first indication information is different from the second indication information, and the display interface is arranged for coupling to a driver circuit.
According to a second aspect of the present invention, an exemplary data processing apparatus is disclosed. The exemplary data processing apparatus includes a compressor and an output interface. The compressor is arranged for generating a compressed display data by compressing a first display data according to a compression algorithm. The output interface is arranged for appending first indication information and first identification (ID) number in a first output bitstream, appending second ID number in a second output bitstream, and outputting the first output bitstream and the second output bitstream via a display interface, wherein the first output bitstream is derived from the compressed display data, the first indication information is set in response to the compression algorithm employed by the compressor, the first ID number is different from the second ID number, and the display interface is arranged for coupling to a driver circuit.
According to a third aspect of the present invention, an exemplary data processing method is disclosed. The exemplary data processing method includes generating a compressed display data by compressing a display data according to a compression algorithm; and appending first indication information in an output bitstream, appending second indication information in a second output bitstream, and outputting the first output bitstream and the second output bitstream via a display interface, wherein the first output bitstream is derived from the compressed display data, the first indication information is set in response to the compression algorithm, the first indication information is different from the second indication information, and the display interface is arranged for coupling to a driver circuit.
These and other objectives of the present invention will no doubt become obvious to those of ordinary skill in the art after reading the following detailed description of the preferred embodiment that is illustrated in the various figures and drawings.
Certain terms are used throughout the description and following claims to refer to particular components. As one skilled in the art will appreciate, manufacturers may refer to a component by different names. This document does not intend to distinguish between components that differ in name but not function. In the following description and in the claims, the terms “include” and “comprise” are used in an open-ended fashion, and thus should be interpreted to mean “include, but not limited to . . . ”. Also, the term “couple” is intended to mean either an indirect or direct electrical connection. Accordingly, if one device is coupled to another device, that connection may be through a direct electrical connection, or through an indirect electrical connection via other devices and connections.
The present invention proposes applying data compression to a display data and then transmitting a compressed display data over a display interface. As the data size/data rate of the compressed display data is smaller than that of the original un-compressed display data, the power consumption of the display interface is reduced correspondingly. Besides, the de-compression algorithm employed by a receiving end which receives and de-compresses a compressed display data is required to be compliant with the compression algorithm employed by a transmitting end which generates and transmits the compressed display data; otherwise, the receiving end fails to correctly de-compress the compressed display data. Therefore, the present invention further proposes transmitting/receiving the compression-related indication information via the display interface, such that the de-compression algorithm of the receiving end is properly configured based on the compression-related indication information. Further details will be described as below.
The application processor 102 is coupled to the display interface 103, and supports un-compressed data transmission and compressed data transmission. When the application processor 102 is used to transmit un-compressed data to the driver IC 104, the application processor 102 generates the un-compressed display data D1 according to an input display data DI provided by an external data source 105, and transmits the un-compressed display data D1 over the display interface 103. When the application processor 102 is used to transmit compressed data to the driver IC 104, the application processor 102 generates a compressed display data D1′ according to the input display data DI provided by the external data source 105, and transmits the compressed display data D1′ over the display interface 103. Byway of example, but not limitation, the data source 105 may be a camera sensor, a memory card or a wireless receiver, and the input display data DI may include image data, video data, graphic data, and/or OSD data. Further, the input display data DI may be single view data for 2D display or multiple view data for 3D display.
As shown in
The output interface 114 is arranged for packing/packetizing the un-compressed display data D1/compressed display data D1′ into an output bitstream according to the transmission protocol of the display interface 103, and transmits the output bitstream to the driver IC 104 via the display interface 103. When the compression mode of the application processor 102 is enabled, the compressor 117 further sets indication information INFO in response to the compression algorithm employed. Besides, the output interface 114 further records the indication information INFO in the output bitstream. In this way, when the output bitstream is transmitted from the application processor 102 to the driver IC 104, the compression-related indication information (e.g., the indication information INFO) is also transmitted via the display interface 103.
Regarding the driver IC 104, it communicates with the application processor 102 via the display interface 103. In this embodiment, the driver IC 104 is coupled to the display interface 103, and supports un-compressed data reception and compressed data reception. When the application processor 102 transmits the un-compressed data D1 to the driver IC 104, the driver IC 104 is operated under a non-decompression mode to receive an un-compressed data D2 from the display interface 103 and drive a display panel 106 according to the un-compressed display data D2. By way of example, the display panel 106 may be implemented using any 2D/3D display device (e.g. a retina display), and the pixel arrangement may be a rectangle layout, a triangle layout or a pentile layout. When the application processor 102 transmits the compressed data D1′ to the driver IC 104, the driver IC 104 is operated under a de-compression mode to receive a compressed display data D2′ from the display interface 103 and drive the display panel 106 according to a de-compressed display data derived from de-compressing the compressed display data D2′. If there is no error introduced during the data transmission, the un-compressed data D1 transmitted under the non-compression mode should be identical to the un-compressed data D2 received under the non-decompression mode, and the compressed data D1′ transmitted under the compression mode should be identical to the compressed data D2′ received under the de-compression mode.
As shown in
The input interface 124 is arranged for receiving the input bitstream from the display interface 103, and un-packing/un-packetizing the input bitstream into un-compressed display data D2/compressed display data D2′ according to the transmission protocol of the display interface 103. When the de-compression mode of the driver IC 104 is enabled, the input interface 124 is further arranged for parsing the indication information INFO included in the input bitstream, and configuring the de-compressor 127 to employ a de-compression algorithm as indicated by the indication information INFO. In addition to the compressed data transmission between the application processor 102 and the driver IC 104, information handshaking is realized through the display interface 103. Therefore, with the help of the indication information INFO supplied from the application processor 102, the de-compressor 127 of the driver IC 104 is properly configured to employ an adequate de-compression algorithm needed for de-compressing the compressed data D2′ correctly.
In one exemplary design, the output interface 114 records the indication information INFO by setting a command set in a payload portion of the output bitstream transmitted over the display interface 103, and the input interface 124 obtains the indication information INFO by parsing a command set in a payload portion of the input bitstream received from the display interface 103. Please refer to
Step 400: Start.
Step 402: Configure the compressor 117 to employ a compression algorithm.
Step 404: Set the indication information INFO in response to the compression algorithm employed by the compressor 117.
Step 406: Record the indication information INFO in an output bitstream. For example, the indication information INFO is recorded by setting a command set in a payload portion of the output bitstream.
Step 408: Transmit the output bitstream over the display interface 103.
Step 410: Receive an input bitstream from the display interface 103.
Step 412: Parse the indication information INFO included in the input bitstream. For example, the indication information INFO is obtained by parsing a command set in a payload portion of the input bitstream.
Step 414: Configure the de-compressor 127 to employ a de-compression algorithm as indicated by the indication information INFO.
Step 416: End.
It should be noted that steps 402-408 are performed by the application processor (AP) 102, and steps 410-414 are performed by the driver IC 104. As a person skilled in the art can readily understand details of each step shown in
In the embodiment shown in
The channel controller 504 is arranged to direct data to individual driver ICs 106, 506, 508, 510 under the control of the channel detector 502, thus eliminating the need for multiple interfaces or complex multiplexing schemes. In this embodiment, the output interface 114 of the application processor 102 is further arranged for recording a channel identification (ID) number IDCH in a header portion of the output bitstream to indicate which one of the driver ICs 106, 506, 508, 510 should be connected for receiving the output bitstream.
The channel detector 502 is implemented for receiving an input bitstream from the display interface 103, and identifying the channel ID number IDCH from the header portion of the input bitstream. Next, the channel controller 504 dispatches the input bitstream, including the header portion and the payload portion shown in
Step 700: Start.
Step 702: Configure the compressor 117 to employ a compression algorithm.
Step 704: Set the indication information INFO in response to the compression algorithm employed by the compressor 117.
Step 706: Set the channel ID number IDCH indicative of which driver IC should be connected for data transmission.
Step 708: Record the channel ID number IDCH and the indication information INFO in an output bitstream. For example, the indication information INFO is recorded by setting a command set in a payload portion of the output bitstream, and the channel ID number IDCH is recorded by setting a header portion of the output bitstream.
Step 710: Transmit the output bitstream over the display interface 103.
Step 712: Get the channel ID number IDCH from an input bitstream. For example, the channel ID number IDCH is obtained by parsing a header portion of the input bitstream.
Step 714: Dispatch the input bitstream to a selected driver IC with the channel ID number IDCH.
Step 716: Receive the input bitstream dispatched from the channel controller 504.
Step 718: Parse the indication information INFO included in the input bitstream. For example, the indication information INFO is obtained by parsing a command set in a payload portion of the input bitstream.
Step 720: Configure the de-compressor 127 to employ a de-compression algorithm as indicated by the indication information INFO.
Step 722: End.
It should be noted that steps 702-710 are performed by the application processor (AP) 102, step 712 is performed by the channel detector 502, step 714 is performed by the channel controller 504, and steps 716-720 are performed by the selected driver IC (i.e., one of the driver ICs 106, 506, 508, 510). As a person skilled in the art can readily understand details of each step shown in
Those skilled in the art will readily observe that numerous modifications and alterations of the device and method may be made while retaining the teachings of the invention. Accordingly, the above disclosure should be construed as limited only by the metes and bounds of the appended claims.
This is a continuation of U.S. application Ser. No. 13/936,231 filed Jul. 8, 2013, which claims the benefit of U.S. provisional application No. 61/711,319 filed Oct. 9, 2012 and U.S. provisional application No. 61/712,949 filed Oct. 12, 2012. The entire contents of all related applications are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4424565 | Larson | Jan 1984 | A |
5553160 | Dawson | Sep 1996 | A |
5760760 | Helms | Jun 1998 | A |
5943508 | Penney | Aug 1999 | A |
6031929 | Maitz | Feb 2000 | A |
6353699 | Schwab | Mar 2002 | B1 |
6704022 | Aleksic | Mar 2004 | B1 |
6914637 | Wolf | Jul 2005 | B1 |
7036032 | Mizuyabu et al. | Apr 2006 | B2 |
7822278 | Hobbs et al. | Oct 2010 | B1 |
7903119 | Hochmuth | Mar 2011 | B2 |
7930436 | Znosko | Apr 2011 | B1 |
8112513 | Margulis | Feb 2012 | B2 |
8145813 | Ho | Mar 2012 | B2 |
8179971 | Gough | May 2012 | B1 |
8363969 | Wang | Jan 2013 | B1 |
8599316 | Deever | Dec 2013 | B2 |
20020030675 | Kawai | Mar 2002 | A1 |
20020057265 | Tamura | May 2002 | A1 |
20020105905 | Boyle | Aug 2002 | A1 |
20030234799 | Lee | Dec 2003 | A1 |
20040103216 | Lane | May 2004 | A1 |
20050135682 | Abrams | Jun 2005 | A1 |
20050276496 | Molgaard | Dec 2005 | A1 |
20060017715 | Kimura | Jan 2006 | A1 |
20060037051 | McDowell | Feb 2006 | A1 |
20060093230 | Hochmuth | May 2006 | A1 |
20060117371 | Margulis | Jun 2006 | A1 |
20060159358 | Yi | Jul 2006 | A1 |
20060215755 | Ju | Sep 2006 | A1 |
20070081587 | Raveendran | Apr 2007 | A1 |
20070255926 | Chuang | Nov 2007 | A1 |
20090129478 | Meroth | May 2009 | A1 |
20090322713 | Furihata | Dec 2009 | A1 |
20100020831 | Okamoto | Jan 2010 | A1 |
20100073574 | Nakajima et al. | Mar 2010 | A1 |
20100158104 | Lin | Jun 2010 | A1 |
20100182402 | Nakajima | Jul 2010 | A1 |
20100309975 | Zhou et al. | Dec 2010 | A1 |
20100328425 | Nagaraj | Dec 2010 | A1 |
20110075729 | Dane | Mar 2011 | A1 |
20110249723 | Wasily | Oct 2011 | A1 |
20120027317 | Choi | Feb 2012 | A1 |
20120068952 | Slaby | Mar 2012 | A1 |
20120072044 | Slaby | Mar 2012 | A1 |
20120072157 | Alameh | Mar 2012 | A1 |
20120134410 | Kawasaki | May 2012 | A1 |
20120163181 | Xue | Jun 2012 | A1 |
20120207155 | Nelogal | Aug 2012 | A1 |
20130088373 | Takano | Apr 2013 | A1 |
20130127980 | Haddick | May 2013 | A1 |
20130179659 | Seo | Jul 2013 | A1 |
20130293121 | Viacheslav | Nov 2013 | A1 |
20130322517 | Zurpal | Dec 2013 | A1 |
Number | Date | Country |
---|---|---|
1359048 | Jul 2002 | CN |
1610408 | Apr 2005 | CN |
1838772 | Sep 2006 | CN |
101035086 | Sep 2007 | CN |
101237301 | Aug 2008 | CN |
101355364 | Jan 2009 | CN |
101378384 | Mar 2009 | CN |
101553795 | Oct 2009 | CN |
101816318 | Dec 2009 | CN |
101669361 | Mar 2010 | CN |
101882745 | Mar 2010 | CN |
101426132 | Jul 2010 | CN |
101803382 | Aug 2010 | CN |
201758429 | Mar 2011 | CN |
101340575 | Apr 2012 | CN |
102939630 | Feb 2013 | CN |
Entry |
---|
“International Search Report” mailed on Dec. 5, 2013 for International application No. PCT/CN2013/083061, International filing date:Sep. 6, 2013. |
“International Search Report” mailed on Dec. 19, 2013 for International application No. PCT/CN2013/083118, International filing date:Sep. 9, 2013. |
“International Search Report” mailed on Dec. 19, 2013 for International application No. PCT/CN2013/083653, International filing date:Sep. 17, 2013. |
“International Search Report” mailed on Dec. 26, 2013 for International application No. PCT/CN2013/083739, International filing date:Sep. 18, 2013. |
“International Search Report” mailed on Jan. 2, 2014 for International application No. PCT/CN2013/084496, International filing date:Sep. 27, 2013. |
“International Search Report” mailed on Jan. 2, 2014 for International application No. PCT/CN2013/084489, International filing date:Sep. 27, 2013. |
Office Action issued Apr. 1, 2017, in Chinese Patent Application No. 201380052502.2. |
Office Action mailed Feb. 22, 2017, in co-pending U.S. Appl. No. 13/937,224. |
Number | Date | Country | |
---|---|---|---|
20160253980 A1 | Sep 2016 | US |
Number | Date | Country | |
---|---|---|---|
61711319 | Oct 2012 | US | |
61712949 | Oct 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13936231 | Jul 2013 | US |
Child | 15152562 | US |