WO2019134393A1 - 触控与显示驱动器、驱动方法、主机及触控显示装置 - Google Patents

触控与显示驱动器、驱动方法、主机及触控显示装置 Download PDF

Info

Publication number
WO2019134393A1
WO2019134393A1 PCT/CN2018/105677 CN2018105677W WO2019134393A1 WO 2019134393 A1 WO2019134393 A1 WO 2019134393A1 CN 2018105677 W CN2018105677 W CN 2018105677W WO 2019134393 A1 WO2019134393 A1 WO 2019134393A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
driver
touch
display
data
Prior art date
Application number
PCT/CN2018/105677
Other languages
English (en)
French (fr)
Inventor
范利涛
Original Assignee
京东方科技集团股份有限公司
北京京东方光电科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 京东方科技集团股份有限公司, 北京京东方光电科技有限公司 filed Critical 京东方科技集团股份有限公司
Priority to US16/332,569 priority Critical patent/US10915200B2/en
Publication of WO2019134393A1 publication Critical patent/WO2019134393A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4411—Configuring for operating with peripheral devices; Loading of device drivers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
    • G06F3/041—Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means
    • G06F3/0416—Control or interface arrangements specially adapted for digitisers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
    • G06F3/041—Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means
    • G06F3/0412—Digitisers structurally integrated in a display
    • G—PHYSICS
    • G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
    • G09G—ARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
    • G09G3/00—Control arrangements or circuits, of interest only in connection with visual indicators other than cathode-ray tubes
    • G09G3/20—Control arrangements or circuits, of interest only in connection with visual indicators other than cathode-ray tubes for presentation of an assembly of a number of characters, e.g. a page, by composing the assembly by combination of individual elements arranged in a matrix no fixed position being assigned to or needed to be assigned to the individual characters or partial characters

Definitions

  • the present disclosure relates to the field of electronic technologies, and in particular, to a touch and display driver, a driving method, a host, and a touch display device.
  • touch and display driver integration has the advantages of reducing display noise, saving cost, and making the appearance of the electronic device thinner, thus causing various LCD screens, module manufacturers, etc. Competing for research and development.
  • the related art generally adds a flash memory (Flash Memory, Flash for short) to the drive data of the firmware and the configuration data, and drives the TDDI on the flexible printed circuit board (FPC) of the display module of the electronic device.
  • flash memory Flash Memory, Flash for short
  • FPC flexible printed circuit board
  • drive data can be obtained from the flash memory to drive the touch component and/or the display component.
  • This kind of TDDI driving method needs to be printed on the FPC, and needs to burn TDDI firmware and other processes, which makes the FPC manufacturing process complicated and difficult, and uses the Flash storage drive data, which is not only costly but also takes up FPC.
  • the space is not conducive to the thinning of electronic devices.
  • a touch and display driver including:
  • a communication interface configured to communicate with the host to obtain a driver file
  • the controller is configured to drive the touch component and/or the display component using the acquired driver file.
  • the touch and display driver further includes a touch component and/or a display component.
  • the driver file includes N data identifiers and N types of drive data respectively corresponding to the N data identifiers, where N is a positive integer greater than or equal to 1;
  • the controller is further configured to determine N target driving devices according to the N data identifiers; and drive the N target driving devices by using the N kinds of driving data respectively.
  • the controller is further configured to send a driver file acquisition request to the host via the communication interface, wherein the driver file acquisition request includes an identification of target drive data.
  • the driver file includes a file header, wherein the file header includes a size of the driver file and a first check code;
  • the controller is further configured to: after obtaining the driver file, determining, according to the size of the driver file in the file header, whether the receiving process of the driver file ends; and calculating the first verification data according to the obtained driver file;
  • a host including:
  • a memory configured to store a driver file for driving the touch and display driver
  • a communication interface configured to communicate with the touch and display driver
  • the processor is configured to, when determining that the touch and display driver is powered on, read a drive file stored on the memory and send the touch file to the touch and display driver through the communication interface.
  • the communication interface is further configured to: acquire a driver file acquisition request sent by the touch control and the display driver, wherein the driver file acquisition request includes an identifier of the target driver data.
  • the processor is further configured to perform the packet processing on the driver file according to a protocol corresponding to the communication interface;
  • the processor is further configured to determine a file header corresponding to the driver file according to an attribute of the driver file, where the file header includes a size bit and a check code bit for identifying the size of the driver file.
  • a touch display device comprising the touch and display driver according to the first aspect.
  • An electronic device comprising: the touch and display driver of the first aspect, and the host of the second aspect.
  • a touch and display driver driving method including:
  • the touch component and/or the display component are driven by the drive file.
  • the drive file includes N data identifiers and N types of drive data respectively corresponding to the N data identifiers, where N is a positive integer greater than or equal to 1;
  • the driving process of the touch component and/or the display component includes:
  • the N target driving devices are driven by the N kinds of driving data, respectively.
  • the method before the obtaining the driver file from the host, the method further includes:
  • the driver file includes a file header, wherein the file header includes a size of the driver file and a first check code;
  • the method further includes:
  • a touch and display driver driving method including:
  • the determining that the touch and display drivers are powered up comprises:
  • the method before the sending the driving file to the touch and display driver, the method further includes:
  • the method further includes:
  • FIG. 1 is a schematic structural diagram of an example of a touch and display driver according to an embodiment of the present disclosure
  • FIG. 2 is a schematic flow chart of an example of a touch and display driver driving method according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart diagram of another touch and display driver driving method according to an embodiment of the present disclosure
  • 4A-4B are schematic structural diagrams showing an example of a driver file provided by an embodiment of the present disclosure.
  • FIG. 5 is a schematic structural diagram of an example of a host according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic flowchart diagram of another touch and display driver driving method according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic flowchart diagram of another touch and display driver driving method according to an embodiment of the present disclosure.
  • FIG. 8 is an exemplary signaling interaction diagram of a touch and display driver driving method according to an embodiment of the present disclosure
  • FIG. 9 is a schematic structural diagram of an example of a touch display device according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
  • the related art generally adds a Flash to the peripheral FPC of the display module of the electronic device to store driving data such as firmware data and configuration data, so that when driving the touch component and/or the display component in the TDDI, the Flash component can be obtained from the Flash.
  • driving data such as firmware data and configuration data
  • this TDDI driver method needs to be printed on the FPC, and needs to burn TDDI firmware and other processes, which makes the FPC manufacturing process complex and difficult, and the use of Flash storage drive data, not only high cost, but also Taking up the space of the FPC is not conducive to the thinning of electronic devices.
  • embodiments of the present disclosure provide a touch and display driver and a host.
  • the touch control and display driver and the host provided by the embodiments of the present disclosure can communicate through the communication interface, store the drive file on the host, and then obtain the drive file from the host as needed to drive the touch in the touch and display driver.
  • the control component and/or the display component reduce the manufacturing process difficulty of the FPC, reduce the manufacturing cost, save the space of the FPC, and provide conditions for the thinning of the electronic device.
  • FIG. 1 is a schematic structural diagram of an example of a touch and display driver according to an embodiment of the present disclosure.
  • 2 is a schematic flow chart of an example of a touch and display driver driving method according to an embodiment of the present disclosure.
  • FIG. 3 is a schematic flow chart of another touch and display driver driving method according to an embodiment of the present disclosure.
  • the touch and display driver 10 includes a communication interface 11 and a controller 12.
  • the touch and display driver 10 may additionally include a touch component 13 and/or a display component 14 .
  • the touch and display driver 10 may not include any or both of the touch component 13 and/or the display component 14.
  • the touch and display driver 10 without the touch component 13 can be used. In this case, the touch and display driver 10 can also be called To display the drive 10.
  • a touch and display driver 10 without the display component 14 can be used, and the touch and display driver 10 can also be used. It is called touch driver 10.
  • touch driver 10 In the case where the touch component 13 and/or the display component 14 are externally coupled to and coupled to the touch and display driver 10, the touch and display driver 10 itself may not have the touch component 13 and/or display. Component 14. In other words, the present disclosure is not limited to the specific embodiment shown in FIG. 1.
  • the communication interface 11 is configured to perform a communication connection with the host to obtain a driver file.
  • the controller 12 is configured to drive the touch component 13 and/or the display component 14 using the acquired drive file.
  • the driver file may include any one or more of the following: firmware data, configuration data of the touch component 13 and/or the display component 14, power drive data of the display component, time drive data, and the like.
  • the communication interface 11 of the touch and display driver 10 can be connected to the host through a bus, or can be connected to the host by other means, which is not limited herein.
  • the drive files required to drive the touch component 13 and/or the display component 14 can be stored in the host. Therefore, when the touch component 13 and/or the display component 14 need to be driven after the touch and display driver 10 is powered on, the driver file can be obtained from the host through the communication interface 11, and the touch component can be driven by the controller 12 by using the driver file. 13 and/or display component 14. Since the driver file is stored on the host, there is no need to add Flash to the FPC to store the driver file, so there is no need to process and burn the TDDI firmware on the FPC, which reduces the manufacturing process difficulty of the FPC, reduces the manufacturing cost, and saves.
  • the space of the FPC provides conditions for the thinning of electronic equipment.
  • the touch and display driver driving method provided by the embodiment of the present disclosure may include:
  • step 201 a driver file is obtained from the host.
  • Step 202 Drive the touch component and/or the display component by using the driver file.
  • the touch and display driver driving method shown in FIG. 2 can be performed by, for example, the touch and display driver 10 shown in FIG. 1.
  • the manufacturing process of the FPC is reduced, the manufacturing cost is reduced, and the FPC is saved. Space provides conditions for the thinning of electronic devices.
  • the touch and display driver 10 can respectively obtain driving data such as firmware data, the touch component 13 and/or configuration data of the display component 14; or, the firmware data, the touch component 13 and/or can be acquired at one time. Or a plurality of types of driving data such as configuration data of the component 14 are displayed, thereby increasing the speed of obtaining the driving file, thereby improving the driving speed and efficiency of the touch and display driver 10.
  • the driver file may include N data identifiers and N types of driving data respectively corresponding to the N data identifiers, where N is a positive integer greater than or equal to 1;
  • the controller 12 is specifically configured to determine N target driving devices according to the N data identifiers; and drive the N target driving devices by using N kinds of driving data respectively.
  • the driving data may include firmware data, configuration data of the touch component 13 , configuration data of the display component 14 , power drive data of the display component 14 , time drive data, and the like.
  • the data identifier is used to uniquely identify the driver data, which can be arbitrarily set as needed. For example, it can be a custom field such as Data1, Data2, etc.
  • the target driving device may be the touch component 13 or the display component 14.
  • the target driving device corresponding to the driving data can be determined.
  • the controller 12 can determine the N data identifiers according to the N data identifiers in the driving file.
  • the N target drivers are respectively driven to drive the N target driving devices by using N kinds of driving data respectively corresponding to the N data identifiers.
  • the data identifier corresponding to the configuration data of the touch component 13 is set to Data1
  • the data identifier corresponding to the configuration data of the display component 14 is Data2. If the touch and display driver 10 obtains the drive file from the host, including the data identifiers Data1 and Data2, according to the data identifiers Data1 and Data2, the target driving device can be determined as the touch component 13 and the display component 14, so that the data1 can be utilized separately.
  • the configuration data of the corresponding touch component 13 and the configuration data of the display component 14 corresponding to Data2 are respectively driven to the touch component 13 and the display component 14.
  • step 202 may include:
  • N target drive devices are driven by N kinds of drive data, respectively.
  • various driving data may be transmitted in a preset order.
  • the firmware data may be transmitted first, and then the configuration data may be transmitted.
  • the disclosure is not limited thereto.
  • the driving speed and efficiency of the touch and display driver 10 are improved by acquiring a plurality of driving data at one time. And by determining the target driving device according to the data identification, the touch and display driver 10 is determined to determine the speed of the target driving device.
  • the driver file may be automatically obtained from the host; or the touch and display driver 10 may first send a driver file acquisition request to the host, and the host receives the driver file. After the driver file gets the request, the driver file is obtained from the host. That is, in the touch and display driver 10 provided by the embodiment of the present disclosure, the controller 12 can also be configured to:
  • a driver file acquisition request is sent to the host through the communication interface 11, wherein the acquisition request includes an identifier of the target driver data.
  • the identifier of the target driving data is used to uniquely identify the target driving data, which can be arbitrarily set as needed. For example, it can be a custom field such as Data1, Data2, etc.
  • an identifier of N types of target drive data may be included in the acquisition request, where N is a positive integer greater than or equal to 1.
  • the touch and display driver 10 can send a driver file acquisition request to the host, where the obtaining request includes respectively driving the N devices.
  • the identification of the N types of target drive data After the N touch drive data is acquired by the touch and display driver 10, the N target drive devices can be determined according to the N flags, and the N target drive devices are respectively driven by the N types of drive data.
  • the touch and display driver 10 first sends a driver file acquisition request to the host, and then acquires the driver file, thereby improving the flexibility of the control of the touch and display driver 10.
  • the touch and display driver driving method provided by the embodiment of the present disclosure may further include:
  • a file header may be included in the driver file, and the size of the driver file may be included in the file header, so that when the touch and display driver 10 receives the driver file, it may be determined according to the size of the driver file. Whether the process of receiving and receiving the file by the touch and display drive 10 ends.
  • the first check code may be included in the file header, so that the received driver file may be determined to be accurate according to the first check code.
  • the driver file includes a file header, wherein the file header includes a size of the driver file and a first check code;
  • the controller 12 is further configured to: after obtaining the driver file, determining whether the receiving process of the driver file ends according to the size of the driver file in the file header; and calculating the first verification data according to the obtained driver file;
  • the driver file may further include a data block.
  • the first check code may be determined by the host according to the attributes of the file header and the data block in the driver file, and is used by the touch and display driver 10 to determine.
  • the obtained driver file is accurate, and may be a redundancy check code or other check code, which is not limited herein.
  • the first verification data may be a verification code or the like calculated by the controller 12 based on the acquired drive file.
  • the touch and display driver 10 obtains the driver file from the host through the communication interface 11, if the size of the driver file is the same as the size of the driver file included in the file header, it can be determined that the receiving process of the driver file is completed.
  • the first verification code can be compared with the first verification data, and if the first calibration is calculated, If the verification data is consistent with the first verification code included in the file header, it may be determined that the obtained driver file is accurate. If the first verification data is inconsistent with the first verification code included in the file header, the obtained driver file may be determined. Inaccurate.
  • the driver file may be a Hex file, and the structure of the driver file may be as shown in FIG. 4A.
  • the file header includes a state DI of the transmitted data, a size D-Size of the driver file, and a first check code CRC. Among them, the state can be used to characterize the category of the data.
  • the specific data status can be represented by Data0, Data1, and the like. In some embodiments, Data0 may indicate that the corresponding data is firmware data, Data1 may indicate that the corresponding data is configuration data of the touch component, Data2 may indicate that the corresponding data is configuration data of the display component, and the like. However, the present disclosure is not limited thereto.
  • the status DI and D-Size of the transmitted data can be set and transmitted by using the data identification register and the data packet register, respectively.
  • the data identification register can set different values to represent data of different states, such as firmware data, touch component configuration data, and touch component configuration data.
  • the data packet register can set and transmit data size information for the specific data state of the data identification register.
  • the data block may be sequentially transmitted according to the actual data of the specific status information identified in the file header until the driving file reaches the D-Size size data, and the touch and display driver 10 determines the size of the received driver file. If the D-Size is the same size, it can be determined that the receiving process of the driver file ends. At the same time, the touch and display driver 10 can calculate the first verification data according to the driving file, and if the first verification data calculated according to the driving file is the first calibration data. If the verification code CRC is consistent, it can be determined that the obtained driver file is accurate.
  • the host may also respectively determine the first check code and the second check code according to the attributes of the file header and the data block in the driver file, that is, the drive file acquired by the touch and display driver 10 as shown in FIG. 4B.
  • the first check code CRC1 may be included in the file header
  • the second check code CRC2 may be included in the data block.
  • the first check code CRC1 is used by the touch and display driver 10 to determine whether the file header in the obtained drive file is accurate.
  • the second check code CRC2 is used by the touch and display driver 10 to determine whether the data block in the obtained drive file is accurate.
  • the first check data and the second check data may be respectively calculated according to the file header and the data block, and the first check data calculated according to the file header and the file are determined.
  • the first check code CRC1 included in the header is consistent, and whether the second check data calculated according to the data block is consistent with the second check code CRC2 included in the data block, and if they are all consistent, the obtained drive file can be determined to be accurate. .
  • the touch and display driver driving method provided by the embodiment of the present disclosure may further include: after step 201:
  • the touch and display driver driving method provided by the embodiment of the present disclosure may include:
  • step 301 a driver file is obtained from the host.
  • the driver file includes a file header, and the file header includes a size of the driver file and a first check code.
  • Step 302 Determine, according to the size of the driver file in the file header, whether the receiving process of the driver file ends.
  • Step 303 if yes, calculating the first verification data according to the obtained driver file.
  • Step 304 Determine whether the acquired driver file is accurate according to whether the first check code is consistent with the first check data.
  • Step 305 if yes, driving the touch component and/or the display component by using the driver file.
  • the touch control and display driver provided by the embodiment of the present disclosure can communicate with the host through a communication interface, and the drive file is stored on the host, and the drive file is obtained from the host as needed to drive the touch in the touch and display driver.
  • the components and/or display components reduce the manufacturing process difficulty of the FPC, reduce the manufacturing cost, save the space of the FPC, and provide conditions for the thinning of the electronic device.
  • FIG. 5 is a schematic structural diagram of an example of a host provided by an embodiment of the present disclosure.
  • FIG. 6 is a schematic flow chart of another touch and display driver driving method according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic flow chart of another touch and display driver driving method according to an embodiment of the present disclosure.
  • the host 20 includes a communication interface 21, a memory 22, and a processor 23.
  • the drive file for driving the touch and display driver 10 is stored on the memory 22.
  • the communication interface 21 is configured to be in communication connection with the touch and display driver 10;
  • the processor 23 is configured to read the drive file stored on the memory 22 when it is determined that the touch and display drivers are powered up, and to transmit to the touch and display driver 10 via the communication interface 21.
  • the host 20 may be a device such as a central processing unit included in an electronic device such as a smart phone or a computer.
  • the driver files may include firmware data, touch data component 13 and/or configuration data of display component 14, power drive data of display component 14, time drive data, and the like.
  • the communication interface 21 of the host 20 can be connected to the touch and display driver 10 through a bus, or can be connected to the touch and display driver 10 by other means, which is not limited herein.
  • the driving files required to drive the touch component 13 and/or the display component 14 can be stored in the host 20, so that after the touch and display driver 10 is powered on, the touch component 13 and/or the display component need to be driven.
  • the processor 23 of the host 20 can read the drive file stored in the memory 22 and send it to the touch and display driver 10 through the communication interface 21, so that the touch and display driver 10 can drive the touch using the drive file.
  • Component 13 and/or display assembly 14 Since the driver file is stored on the host 20, there is no need to add Flash to the FPC to store the driver file, so there is no need to process and burn the TDDI firmware on the FPC, which reduces the manufacturing process difficulty of the FPC and reduces the manufacturing cost. It saves space for FPC and provides conditions for thinning and thinning electronic devices.
  • the touch and display driver driving method provided by the embodiment of the present disclosure may include:
  • Step 501 Acquire a driving file of the touch and display driver when determining that the touch control and the display driver are powered on;
  • Step 502 Send the driver file to the touch and display driver.
  • the touch and display driver driving method shown in FIG. 6 can be performed by, for example, the host 20 shown in FIG. 5.
  • the FPC manufacturing process is reduced by storing the driver file on the host and sending the driver file to the touch and display driver when the touch and display drivers are powered up to drive the touch component and/or the display component.
  • the difficulty, the manufacturing cost is reduced, the space of the FPC is saved, and the conditions for the thinning of the electronic device are provided.
  • the host 20 can separately send the driving data of the firmware data, the touch component 13 and/or the configuration data of the display component 14 to the touch and display driver 10; or the host 20 can also directly execute the firmware data, Various driving data such as the touch component 13 and/or the configuration data of the display component 14 are transmitted to the touch and display driver 10, thereby increasing the transmission speed of the drive file, thereby improving the driving speed and efficiency of the touch and display driver 10.
  • the host 20 can determine whether the touch and display driver 10 is powered on in various manners.
  • the touch and display driver 10 it is possible to monitor whether the power source connected to the power supply end of the touch and display driver 10 outputs an electrical signal. If the power source outputs an electrical signal, it can be determined that the touch and display driver 10 is powered on.
  • the driver file acquisition request can be sent to the host 20, so that the host 20 obtains the touch and display driver 10 to send. After the driver file acquisition request, it is determined that the touch and display driver 10 is powered on.
  • determining that the touch and display driver 10 is powered on may include:
  • the driver file obtaining request includes an identifier of the target driving data.
  • the identification of the target drive data is used to uniquely identify the target drive data required to drive the target drive device, which can be arbitrarily set as needed. For example, it can be a custom field such as Data1, Data2, etc.
  • an identifier of N types of target drive data may be included in the acquisition request, where N is a positive integer greater than or equal to 1.
  • the host 20 can automatically send the driver file to the touch and display driver 10 after detecting that the touch and display driver 10 is powered on; or the host 20 can receive the driver sent by the touch and display driver 10 After the file acquisition request, the drive file is sent to the touch and display drive 10. That is, the communication interface 21 is further configured to acquire a drive file acquisition request sent by the touch control and display driver 10, wherein the acquisition request includes an identifier of the target drive data.
  • the touch and display driver 10 can send a driver file acquisition request to the host 20, wherein the obtaining request includes respectively driving the N devices.
  • the N types of target drive data are identified by the device, so that after acquiring the drive file acquisition request, the host 20 can read the corresponding N kinds of target drive data stored in the memory 22 according to the identifiers of the N types of target drive data, and send
  • the touch and display driver 10 is configured to enable the touch and display driver 10 to acquire N kinds of target drive data
  • the N target drive devices can be driven.
  • the driver file sent by the host 20 may be a file that is packaged according to a protocol corresponding to the communication interface, that is, the processor 23 is further configured to package the driver file according to a protocol corresponding to the communication interface. deal with.
  • the method may further include: Step 601: Perform a packet processing on the driver file according to a communication interface protocol that is in communication with the touch control and display driver 10.
  • the protocol corresponding to the communication interface can be set as needed.
  • the driver file may include a file header
  • the file header may include a size bit and a verification code bit for identifying the size of the driver file, so that after the host 20 sends the driver file to the touch and display driver 10, the touch is performed.
  • the display driver 10 can determine whether the process of receiving the file by the touch control and display driver 10 is finished according to the size information of the size bit, and determine whether the received drive file is accurate by using the check code of the check code bit.
  • the processor 23 is further configured to determine a file header corresponding to the driver file according to an attribute of the driver file, wherein the file header includes a size bit and a check code bit for identifying the size of the driver file.
  • the method may further include:
  • Step 602 Determine, according to an attribute of the driver file, a file header corresponding to the driver file, where the file header includes a size bit and a check code bit for identifying a size of the driver file.
  • the attribute of the driver file may include any information related to the driver file, such as the size of the driver file, the category of the driver data, and the like.
  • the integrity and reliability of the drive file transmission is ensured by setting the size bits including the size of the identification drive file and the check code bits in the driver file.
  • the host provided by the embodiment of the present disclosure can communicate with the touch control and display driver through the communication interface, and store the drive file on the host, and then send the drive file to the touch and display driver as needed to drive the touch and display.
  • the touch component and/or the display component in the driver reduce the manufacturing process difficulty of the FPC, reduce the manufacturing cost, save the space of the FPC, and provide conditions for the thinning and thinning of the electronic device.
  • the touch and display driver driving method provided by the embodiment of the present disclosure is further described below with reference to FIG. 8 .
  • FIG. 8 is an exemplary signaling interaction diagram of a touch and display driver driving method according to an embodiment of the present disclosure.
  • the touch and display driver driving method is performed by a touch and display driver and a host, and the specific interaction process is as follows:
  • Step 701 The touch and display driver sends a driver file acquisition request to the host.
  • the identifier of the target drive data is included in the acquisition request.
  • Step 702 The host acquires a driving file of the touch and display driver according to the identifier of the target driving data.
  • Step 703 The host determines, according to an attribute of the driver file, a file header corresponding to the driver file.
  • the file header includes a size bit and a check code bit for identifying the size of the drive file.
  • Step 704 The host performs a packet processing process according to a communication interface protocol that is in communication with the touch control and the display driver.
  • step 705 the host sends the driver file to the touch and display driver.
  • Step 706 The touch and display driver determines that the receiving process of the driver file ends according to the size of the driver file in the file header.
  • Step 707 The touch and display driver calculates the first verification data according to the acquired driving file.
  • Step 708 The touch and display driver determines that the first check code is consistent with the first check data.
  • step 709 the touch and display driver uses the driver file to drive the touch component and/or the display component.
  • the touch and display driver and the host can send the drive file stored thereon to the touch and display by the host when the touch component and/or the display component in the touch and display driver are to be driven.
  • the driver realizes driving processing of the touch component and/or the display component in the touch and display driver, thereby reducing the manufacturing process difficulty of the FPC, reducing the manufacturing cost, saving the space of the FPC, and being an electronic device
  • the thinness of the conditions provides the conditions.
  • the embodiment of the present disclosure further provides a touch display device.
  • FIG. 9 is a schematic structural diagram of an example of a touch display device according to an embodiment of the present disclosure.
  • the touch display device 30 includes a touch and display driver 10 .
  • the touch display device provided by the embodiment of the present disclosure reduces the FPC by storing the driver file on the host and then acquiring the driver file from the host as needed to drive the touch component and/or the display component in the touch and display driver.
  • the manufacturing process is difficult, the manufacturing cost is reduced, the space of the FPC is saved, and the conditions for the thinning of the electronic device are provided.
  • An embodiment of the present disclosure also provides an electronic device.
  • FIG. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
  • the electronic device 40 includes a touch and display driver 10 and a host 20.
  • the flexible device board can also be included in the electronic device 40, and the touch and display driver 10 and the host 20 can be disposed on the flexible circuit board as needed. Since the drive file is stored on the host 20, the flash circuit board does not need to add Flash to store the drive file, thereby reducing the manufacturing process difficulty of the FPC, reducing the manufacturing cost, saving the space of the FPC, and providing the thin and light electronic device. The conditions.
  • the electronic device provided by the embodiment of the present disclosure can communicate with the touch control and the display driver and the host through a communication interface, and store the drive file on the host, so that the driver file can be obtained from the host as needed to drive the touch and The touch component and/or the display component in the display driver, thereby reducing the manufacturing process difficulty of the FPC, reducing the manufacturing cost, saving the space of the FPC, and providing conditions for the thinning of the electronic device.
  • first and second are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated.
  • features defining “first” or “second” may include at least one of the features, either explicitly or implicitly.
  • the meaning of "a plurality” is at least two, such as two, three, etc., unless specifically defined otherwise.
  • Any process or method description in the flowcharts or otherwise described herein may be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing the steps of a custom logic function or process.
  • the scope of the preferred embodiments of the present disclosure includes additional implementations, in which the functions may be performed in a substantially simultaneous manner or in an inverse order depending on the functions involved, in the order shown or discussed. It will be understood by those skilled in the art to which the embodiments of the present disclosure pertain.
  • a "computer readable medium” can be any apparatus that can contain, store, communicate, propagate, or transport a program for use in an instruction execution system, apparatus, or device, or in conjunction with such an instruction execution system, apparatus, or device.
  • computer readable media include the following: electrical connections (electronic devices) having one or more wires, portable computer disk cartridges (magnetic devices), random access memory (RAM), Read only memory (ROM), erasable editable read only memory (EPROM or flash memory), fiber optic devices, and portable compact disk read only memory (CDROM).
  • the computer readable medium may even be a paper or other suitable medium on which the program can be printed, as it may be optically scanned, for example by paper or other medium, followed by editing, interpretation or, if appropriate, other suitable The method is processed to obtain the program electronically and then stored in computer memory.
  • portions of the present disclosure can be implemented in hardware, software, firmware, or a combination thereof.
  • multiple steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system.
  • a suitable instruction execution system For example, if implemented in hardware and in another embodiment, it can be implemented by any one or combination of the following techniques well known in the art: discrete with logic gates for implementing logic functions on data signals Logic circuits, application specific integrated circuits with suitable combinational logic gates, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), and the like.
  • each functional unit in various embodiments of the present disclosure may be integrated into one processing module, or each unit may exist physically separately, or two or more units may be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the integrated modules, if implemented in the form of software functional modules and sold or used as stand-alone products, may also be stored in a computer readable storage medium.
  • the above mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like. While the embodiments of the present disclosure have been shown and described above, it is understood that the foregoing embodiments are illustrative and are not to be construed as limiting the scope of the disclosure The embodiments are subject to variations, modifications, substitutions and variations.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Control Of Indicators Other Than Cathode Ray Tubes (AREA)
  • User Interface Of Digital Computer (AREA)
  • Liquid Crystal Display Device Control (AREA)

Abstract

一种触控与显示驱动器（10）、驱动方法、主机（20）及触控显示装置（30），其中，触控与显示驱动器（10）包括：通信接口（11），被配置为与主机（20）进行通信连接，以获取驱动文件；控制器（12），被配置为利用获取的驱动文件，驱动触控组件（13）和/或显示组件（14）。

Description

触控与显示驱动器、驱动方法、主机及触控显示装置
相关申请的交叉引用
本申请要求于2018年1月2日递交的题为“触控与显示驱动器、驱动方法、主机及触控显示装置”的中国专利申请(申请号201810002101.0)的优先权，在此以全文引用的方式将该中国专利申请并入本文中。
技术领域
本公开涉及电子技术领域，尤其涉及一种触控与显示驱动器、驱动方法、主机及触控显示装置。
背景技术
目前，由于触控与显示驱动器(Touch and Display Driver Integration，简称TDDI)具有减少显示噪声、节约成本、使所在电子设备的外形更薄等优点，因此引起了各家液晶屏、模组厂家等的争相研发。
相关技术通常是在电子设备中显示模组的外围柔性电路板(Flexible Printed Circuit Board，简称FPC)上增加一个闪存(Flash Memory，简称Flash)来存储固件数据及配置数据等驱动数据，在驱动TDDI中的触控组件和/或显示组件时，可以从闪存中获取驱动数据，以驱动触控组件和/或显示组件。这种TDDI驱动方式，需要在FPC上打件，并且需要烧录TDDI固件等流程，这就造成了FPC的制造工艺复杂、难度大，且利用Flash存储驱动数据，不但成本高，而且占用了FPC的空间，不利于电子设备的轻薄化。
发明内容
根据本公开第一方面的实施例提出了一种触控与显示驱动器，包括：
通信接口，被配置为与主机进行通信连接，以获取驱动文件；
控制器，被配置为利用获取的驱动文件，驱动触控组件和/或显示组件。
在一些实施例中，所述触控与显示驱动器还包括触控组件和/或显示组件。
在一些实施例中，所述驱动文件中包括N个数据标识及与所述N个数据 标识分别对应的N种驱动数据，其中，N为大于或等于1的正整数；
所述控制器还被配置为根据所述N个数据标识，确定N个目标驱动器件；并分别利用所述N种驱动数据，对所述N个目标驱动器件进行驱动。
在一些实施例中，所述控制器还被配置为通过所述通信接口向所述主机发送驱动文件获取请求，其中所述驱动文件获取请求中包括目标驱动数据的标识。
在一些实施例中，所述驱动文件包括文件头，其中所述文件头中包括所述驱动文件的大小及第一校验码；
所述控制器还被配置为在获取到驱动文件后，根据文件头中的驱动文件的大小，确定所述驱动文件的接收过程是否结束；并根据获取的驱动文件计算第一校验数据；
根据第一校验码与第一校验数据是否一致，判断获取的驱动文件是否准确。
根据本公开第二方面的实施例提出了一种主机，包括：
存储器，被配置为存储用于驱动触控与显示驱动器的驱动文件；
通信接口，被配置为与触控与显示驱动器进行通信连接；以及
处理器，被配置为在确定所述触控与显示驱动器上电时，读取存储在所述存储器上的驱动文件，并通过所述通信接口，发送给所述触控与显示驱动器。
在一些实施例中，所述通信接口还被配置为：获取所述触控与显示驱动器发送的驱动文件获取请求，其中所述驱动文件获取请求中包括目标驱动数据的标识。
在一些实施例中，所述处理器还被配置为根据所述通信接口对应的协议将所述驱动文件进行打包处理；
所述处理器还被配置为根据所述驱动文件的属性，确定所述驱动文件对应的文件头，其中，文件头中包括用于标识所述驱动文件大小的尺寸位及校验码位。
根据本公开第三方面的实施例提出了一种触控显示装置，包括如第一方面所述的触控与显示驱动器。
根据本公开第四方面的实施例提出了一种电子设备，包括：如第一方面所述的触控与显示驱动器及如第二方面所述的主机。
根据本公开第五方面的实施例提出了一种触控与显示驱动器驱动方法，包 括：
从主机获取驱动文件；
利用所述驱动文件，对触控组件和/或显示组件进行驱动处理。
在一些实施例中，所述驱动文件中包括N个数据标识及与所述N个数据标识分别对应的N种驱动数据，其中，N为大于或等于1的正整数；
所述对触控组件和/或显示组件进行驱动处理包括：
根据所述N个数据标识，确定N个目标驱动器件；
分别利用所述N种驱动数据，对所述N个目标驱动器件进行驱动。
在一些实施例中，所述从主机获取驱动文件之前，该方法还包括：
向所述主机发送驱动文件获取请求，其中所述驱动文件获取请求中包括目标驱动数据的标识。
在一些实施例中，所述驱动文件包括文件头，其中所述文件头中包括所述驱动文件的大小及第一校验码；
所述主机获取驱动文件之后，还包括：
根据文件头中的驱动文件的大小，确定所述驱动文件的接收过程是否结束；
根据获取的驱动文件计算第一校验数据；
根据第一校验码与第一校验数据是否一致，判断获取的驱动文件是否准确。
根据本公开第六方面的实施例提出了一种触控与显示驱动器驱动方法，包括：
在确定触控与显示驱动器上电时，获取所述触控与显示驱动器的驱动文件；
将所述驱动文件发送给所述触控与显示驱动器。
在一些实施例中，所述确定触控与显示驱动器上电包括：
确定与所述触控与显示驱动器的供电端连接的电源输出电信号；
或者，
获取到所述触控与显示驱动器发送的驱动文件获取请求。
在一些实施例中，所述将所述驱动文件发送给所述触控与显示驱动器之前，该方法还包括：
根据与所述触控与显示驱动器进行通信连接的通信接口协议，将所述驱动文件进行打包处理；
所述将所述驱动文件进行打包处理之前，该方法还包括：
根据所述驱动文件的属性，确定所述驱动文件对应的文件头，其中，文件头中包括用于标识所述驱动文件大小的尺寸位及校验码位。
本公开附加的方面和优点将在下面的描述中部分给出，部分将从下面的描述中变得明显，或通过本公开的实践了解到。
附图说明
本公开上述的和/或附加的方面和优点从下面结合附图对实施例的描述中将变得明显和容易理解，其中：
图1为本公开一个实施例所提供的触控与显示驱动器的示例结构示意图；
图2为本公开实施例所提供的一种触控与显示驱动器驱动方法的示例流程示意图；
图3为本公开实施例所提供的另一种触控与显示驱动器驱动方法的示例流程示意图；
图4A-4B分别为本公开一个实施例所提供的驱动文件的示例结构示意图；
图5为本公开一个实施例所提供的主机的示例结构示意图；
图6为本公开实施例所提供的另一种触控与显示驱动器驱动方法的示例流程示意图；
图7为本公开实施例所提供的另一种触控与显示驱动器驱动方法的示例流程示意图；
图8为本公开一个实施例提供的触控与显示驱动器驱动方法的示例信令交互图；
图9为本公开一个实施例提供的触控显示装置的示例结构示意图；
图10为本公开一个实施例提供的电子设备的示例结构示意图。
具体实施方式
下面详细描述本公开的实施例，所述实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的元件或具有相同或类似功能的元件。下面通过参考附图描述的实施例是示例性的，旨在用于解释本公开，而不 能理解为对本公开的限制。
相关技术通常是在电子设备中显示模组的外围FPC上增加一个Flash来存储固件数据及配置数据等驱动数据，从而在驱动TDDI中的触控组件和/或显示组件时，可以从Flash中获取驱动数据，这种TDDI驱动方式，需要在FPC上打件，并且需要烧录TDDI固件等流程，这就造成了FPC的制造工艺复杂、难度大，且利用Flash存储驱动数据，不但成本高，而且占用了FPC的空间，不利于电子设备的轻薄化。针对这些问题，本公开各实施例提出一种触控与显示驱动器和一种主机。
本公开实施例提供的触控与显示驱动器和主机，可以通过通信接口进行通信连接，通过将驱动文件存储在主机上，再根据需要从主机获取驱动文件，以驱动触控与显示驱动器中的触控组件和/或显示组件，降低了FPC的制造工艺难度，减小了制造成本，节省了FPC的空间，为电子设备的轻薄化提供了条件。
下面参考附图描述本公开实施例的触控与显示驱动器、驱动方法、主机及触控显示装置。
首先结合附图1、附图2及附图3，对本公开实施例提供的触控与显示驱动器及触控与显示驱动器侧执行的触控与显示驱动器驱动方法进行说明。
图1为本公开实施例所提供的触控与显示驱动器的示例结构示意图。图2为本公开实施例所提供的一种触控与显示驱动器驱动方法的示例流程示意图。图3为本公开实施例所提供的另一种触控与显示驱动器驱动方法的示例流程示意图。
如图1所示，该触控与显示驱动器10包括：通信接口11和控制器12。此外，如图1所示，触控与显示驱动器10还可以附加地包括触控组件13和/或显示组件14。然而需要注意的是，在另一些实施例中，触控与显示驱动器10也可以不包括触控组件13和/或显示组件14中的任一个或全部两个。例如，在不支持触控操作的显示设备(例如，监视器、电视等)中，可以采用不具有触控组件13的触控与显示驱动器10，此时触控与显示驱动器10也可被称为显示驱动器10。又例如，在不支持显示的纯触控设备(例如，触摸板、手写板等)中，可以采用不具有显示组件14的触控与显示驱动器10，此时触控与 显示驱动器10也可被称为触控驱动器10。再例如，在触控组件13和/或显示组件14在触控与显示驱动器10外部并与之通信耦接的情况下，触控与显示驱动器10本身可以不具有触控组件13和/或显示组件14。换言之，本公开不限于图1所示的具体实施例。
具体的，通信接口11被配置为与主机进行通信连接，以获取驱动文件；
控制器12被配置为利用获取的驱动文件，驱动触控组件13和/或显示组件14。
其中，驱动文件可以包括以下任意一项或多项：固件数据、触控组件13和/或显示组件14的配置数据、显示组件的电源驱动数据、时间驱动数据等驱动数据。
触控与显示驱动器10的通信接口11可以通过总线与主机连接，也可以通过其它方式与主机连接，此处不作限制。
具体的，驱动触控组件13和/或显示组件14所需的驱动文件可以被存储在主机中。从而在触控与显示驱动器10上电后需要驱动触控组件13和/或显示组件14时，可以通过通信接口11，从主机获取驱动文件，并通过控制器12，利用驱动文件驱动触控组件13和/或显示组件14。由于将驱动文件存储在主机上，无需在FPC上增加Flash来存储驱动文件，因此无需在FPC上打件及烧录TDDI固件等流程，降低了FPC的制造工艺难度，减小了制造成本，节省了FPC的空间，为电子设备的轻薄化提供了条件。
相应的，如图2所示，本公开实施例提供的触控与显示驱动器驱动方法，可以包括：
步骤201，从主机获取驱动文件。
步骤202，利用驱动文件，对触控组件和/或显示组件进行驱动处理。
具体的，图2所示的触控与显示驱动器驱动方法，可以由例如图1所示的触控与显示驱动器10执行。
通过将驱动文件存储在主机上，再根据需要从主机获取驱动文件，以对触控组件和/或显示组件进行驱动处理，降低了FPC的制造工艺难度，减小了制造成本，节省了FPC的空间，为电子设备的轻薄化提供了条件。
需要说明的是，触控与显示驱动器10可以分别获取固件数据、触控组件 13和/或显示组件14的配置数据等驱动数据；或者，也可以一次性获取固件数据、触控组件13和/或显示组件14的配置数据等多种驱动数据，从而提高驱动文件的获取速度，进而提高触控与显示驱动器10的驱动速度和效率。
相应的，驱动文件中可以包括N个数据标识，及与N个数据标识分别对应的N种驱动数据，其中，N为大于或等于1的正整数；
控制器12具体被配置为根据N个数据标识，确定N个目标驱动器件；并分别利用N种驱动数据，对N个目标驱动器件进行驱动。
其中，驱动数据可以包括固件数据、触控组件13的配置数据、显示组件14的配置数据、显示组件14的电源驱动数据、时间驱动数据等数据。
数据标识用来唯一标识驱动数据，其可以根据需要任意设置。比如，可以是如Data1、Data2等自定义的字段。
目标驱动器件可以是触控组件13或显示组件14。
需要说明的是，由于驱动数据与要驱动的器件存在对应关系，而数据标识用来唯一标识驱动数据，因此根据数据标识，可以确定与驱动数据对应的目标驱动器件。
具体的，触控与显示驱动器10通过通信接口11一次性从主机获取包括多种驱动数据的驱动文件后，可以通过控制器12，根据驱动文件中的N个数据标识，确定与N个数据标识分别对应的N个目标驱动器，从而分别利用与N个数据标识分别对应的N种驱动数据，对N个目标驱动器件分别进行驱动。
举例来说，假设预先设置触控组件13的配置数据对应的数据标识为Data1、显示组件14的配置数据对应的数据标识为Data2。若触控与显示驱动器10从主机获取的驱动文件中，包括数据标识Data1和Data2，则根据数据标识Data1和Data2，可以确定目标驱动器件为触控组件13和显示组件14，从而可以分别利用Data1对应的触控组件13的配置数据和Data2对应的显示组件14的配置数据，对触控组件13和显示组件14分别进行驱动。
相应的，图2所示的触控与显示驱动器驱动方法中，步骤202可以包括：
根据N个数据标识，确定N个目标驱动器件；
分别利用N种驱动数据，对N个目标驱动器件进行驱动。
需要说明的是，触控与显示驱动器10从主机获取驱动数据时，多种驱动 数据可以按预设的顺序传输，比如，可以先传输固件数据，再传输配置数据，然而本公开不限于此。
通过一次性获取多种驱动数据，提高了触控与显示驱动器10的驱动速度和效率。且通过根据数据标识，确定目标驱动器件，提高了触控与显示驱动器10确定目标驱动器件的速度。
另外，在本公开实施例中，触控与显示驱动器10上电后，可以自动从主机获取驱动文件；或者，触控与显示驱动器10也可以先向主机发送驱动文件获取请求，在主机接收到驱动文件获取请求后，再从主机获取驱动文件。即，本公开实施例提供的触控与显示驱动器10中，控制器12还可以被配置为：
通过通信接口11向主机发送驱动文件获取请求，其中，获取请求中包括目标驱动数据的标识。
其中，目标驱动数据的标识用来唯一标识目标驱动数据，其可以根据需要任意设置。比如，可以是如Data1、Data2等自定义的字段。在本公开实施例中，获取请求中可以包括N种目标驱动数据的标识，其中N为大于或等于1的正整数。
具体的，在触控与显示驱动器10上电后，需要驱动某N个器件时，触控与显示驱动器10即可向主机发送驱动文件获取请求，其中，获取请求中包含分别驱动该N个器件的N种目标驱动数据的标识。在触控与显示驱动器10获取到N种目标驱动数据后，即可根据N个标识，确定该N个目标驱动器件，从而分别利用N种驱动数据，对N个目标驱动器件分别进行驱动。通过触控与显示驱动器10先向主机发送驱动文件获取请求，再获取驱动文件，提高了触控与显示驱动器10的控制的灵活性。
相应的，本公开实施例提供的触控与显示驱动器驱动方法，在步骤201之前，还可以包括：
向主机发送驱动文件获取请求，其中获取请求中包括目标驱动数据的标识。
在本公开一种可能的实现形式中，驱动文件中可以包括文件头，文件头中可以包括驱动文件的大小，从而在触控与显示驱动器10接收驱动文件时，可以根据驱动文件的大小，确定触控与显示驱动器10接收文件的过程是否结束。另外，文件头中可以包括第一校验码，从而可以根据第一校验码，判断接收到 的驱动文件是否准确。
即，驱动文件包括文件头，其中文件头中包括驱动文件的大小及第一校验码；
控制器12还被配置为在获取到驱动文件后，根据文件头中的驱动文件的大小，确定驱动文件的接收过程是否结束；并根据获取的驱动文件计算第一校验数据；
根据第一校验码与第一校验数据是否一致，判断获取的驱动文件是否准确。
可以理解的是，驱动文件中除了文件头，还可以包括数据块，第一校验码可以是主机根据驱动文件中的文件头和数据块的属性确定的，用于触控与显示驱动器10判断获取的驱动文件是否准确，其可以是冗余校验码，也可以是其它校验码，此处不作限制。
第一校验数据可以是控制器12根据获取的驱动文件计算出的校验码等。
具体的，触控与显示驱动器10通过通信接口11从主机获取到驱动文件后，若驱动文件的大小与文件头中包括的驱动文件的大小相同，则可以确定驱动文件的接收过程完成。
另外，触控与显示驱动器10获取到驱动文件，并根据驱动文件计算出第一校验数据后，即可将第一校验码与第一校验数据进行对比，若计算得到的第一校验数据与文件头中包括的第一校验码一致，则可以确定获取的驱动文件准确，若第一校验数据与文件头中包括的第一校验码不一致，则可以确定获取的驱动文件不准确。
具体实现时，驱动文件可以为Hex文件，驱动文件的结构可以如图4A所示，文件头包括传输数据的状态DI、驱动文件的大小D-Size及第一校验码CRC。其中，状态可以用来表征数据的类别。具体的数据状态可以用Data0、Data1等表示。其中，在一些实施例中，Data0可以表示对应的数据为固件数据，Data1可以表示对应的数据为触控组件的配置数据，Data2可以表示对应的数据为显示组件的配置数据，等等。然而本公开不限于此。
其中，传输数据的状态DI及D-Size，可以分别采用数据识别寄存器和数据包寄存器进行设置并传输。其中，数据识别寄存器可以设置不同的数值表示传输不同状态的数据，如固件数据、触控组件配置数据、触控组件配置数据。 数据包寄存器可以对数据识别寄存器的具体数据状态进行数据大小的信息设置及传输。
具体的，数据块可以根据文件头中识别的具体状态信息的实际数据进行顺序传输，直至驱动文件达到D-Size大小的数据为止，若触控与显示驱动器10确定接收到的驱动文件的大小与D-Size大小相同，则可以确定驱动文件的接收过程结束，同时，触控与显示驱动器10可以根据驱动文件计算第一校验数据，若根据驱动文件计算的第一校验数据与第一校验码CRC一致，则可以确定获取的驱动文件准确。
进一步的，主机也可以分别根据驱动文件中的文件头和数据块的属性分别确定第一校验码和第二校验码，即如图4B所示，触控与显示驱动器10获取的驱动文件中，文件头中可以包括第一校验码CRC1，数据块中可以包括第二校验码CRC2，第一校验码CRC1用于触控与显示驱动器10判断获取的驱动文件中文件头是否准确，第二校验码CRC2用于触控与显示驱动器10判断获取的驱动文件中数据块是否准确。从而触控与显示驱动器10获取到驱动文件后，可以分别根据文件头和数据块计算出第一校验数据和第二校验数据，并判断根据文件头计算的第一校验数据是否和文件头中包括的第一校验码CRC1一致，及根据数据块计算的第二校验数据是否和数据块中包括的第二校验码CRC2一致，若均一致，则可以确定获取的驱动文件准确。
相应的，本公开实施例提供的触控与显示驱动器驱动方法，在步骤201之后，还可以包括：
根据文件头中的驱动文件的大小，确定驱动文件的接收过程是否结束；
根据获取的驱动文件计算第一校验数据；
根据第一校验码与第一校验数据是否一致，判断获取的驱动文件是否准确。
即，如图3所示，本公开实施例提供的触控与显示驱动器驱动方法，可以包括：
步骤301，从主机获取驱动文件。
其中，驱动文件包括文件头，文件头中包括驱动文件的大小及第一校验码。
步骤302，根据文件头中的驱动文件的大小，确定驱动文件的接收过程是否结束。
步骤303，若是，则根据获取的驱动文件计算第一校验数据。
步骤304，根据第一校验码与第一校验数据是否一致，判断获取的驱动文件是否准确。
步骤305，若是，则利用驱动文件，对触控组件和/或显示组件进行驱动处理。
通过在驱动文件中设置包括驱动文件的大小及第一校验码的文件头，保证了驱动文件接收的完整性和可靠性。
本公开实施例提供的触控与显示驱动器可以通过通信接口与主机进行通信连接，通过将驱动文件存储在主机上，再根据需要从主机获取驱动文件，以驱动触控与显示驱动器中的触控组件和/或显示组件，降低了FPC的制造工艺难度，减小了制造成本，节省了FPC的空间，为电子设备的轻薄化提供了条件。
下面结合附图5、附图6和附图7，对本公开实施例提供的主机及主机侧执行的触控与显示驱动器驱动方法进行说明。
图5为本公开实施例所提供的主机的示例结构示意图。图6为本公开实施例所提供的另一种触控与显示驱动器驱动方法的示例流程示意图。图7为本公开实施例所提供的另一种触控与显示驱动器驱动方法的示例流程示意图。
如图5所示，主机20包括通信接口21、存储器22和处理器23。
具体的，存储器22上存储用于驱动触控与显示驱动器10的驱动文件。
具体的，通信接口21被配置为与触控与显示驱动器10进行通信连接；
处理器23被配置为在确定触控与显示驱动器上电时，读取存储在存储器22上的驱动文件，并通过通信接口21，发送给触控与显示驱动器10。
其中，主机20可以是智能手机、电脑等电子设备中包括的中央处理器等器件。驱动文件可以包括固件数据、触控组件13和/或显示组件14的配置数据、显示组件14的电源驱动数据、时间驱动数据等驱动数据。
主机20的通信接口21可以通过总线与触控与显示驱动器10连接，也可以通过其它方式与触控与显示驱动器10连接，此处不作限制。
具体的，驱动触控组件13和/或显示组件14所需的驱动文件可以被存储在主机20中，从而在触控与显示驱动器10上电后，需要驱动触控组件13和/ 或显示组件14时，主机20的处理器23可以读取存储在存储器22上的驱动文件，并通过通信接口21发送给触控与显示驱动器10，以使触控与显示驱动器10可以利用驱动文件驱动触控组件13和/或显示组件14。由于将驱动文件存储在主机20上，无需在FPC上增加Flash来存储驱动文件，因此无需在FPC上打件及烧录TDDI固件等流程，降低了FPC的制造工艺难度，减小了制造成本，节省了FPC的空间，为电子设备的轻薄化提供了条件。
相应的，如图6所示，本公开实施例提供的触控与显示驱动器驱动方法可以包括：
步骤501，在确定触控与显示驱动器上电时，获取触控与显示驱动器的驱动文件；
步骤502，将驱动文件发送给触控与显示驱动器。
具体的，图6所示的触控与显示驱动器驱动方法可以由例如图5所示的主机20执行。
通过将驱动文件存储在主机上，并在触控与显示驱动器上电时将驱动文件发送给触控与显示驱动器，以对触控组件和/或显示组件进行驱动处理，降低了FPC的制造工艺难度，减小了制造成本，节省了FPC的空间，为电子设备的轻薄化提供了条件。
需要说明的是，主机20可以分别将固件数据、触控组件13和/或显示组件14的配置数据等驱动数据发送给触控与显示驱动器10；或者，主机20也可以一次性将固件数据、触控组件13和/或显示组件14的配置数据等多种驱动数据发送给触控与显示驱动器10，从而提高驱动文件的传输速度，进而提高触控与显示驱动器10的驱动速度和效率。
具体实现时，主机20可以通过多种方式确定触控与显示驱动器10是否上电。
比如，可以监测与触控与显示驱动器10的供电端连接的电源是否输出电信号，若该电源输出电信号，则可以确定触控与显示驱动器10上电。
或者，由于触控与显示驱动器10上电后，需要驱动触控组件13和/或显示组件14时，可以向主机20发送驱动文件获取请求，从而主机20在获取到触控与显示驱动器10发送的驱动文件获取请求后，即可确定触控与显示驱动 器10上电。
即，步骤501中，确定触控与显示驱动器10上电，可以包括：
确定与触控与显示驱动器的供电端连接的电源输出电信号；
或者，
获取到触控与显示驱动器发送的驱动文件获取请求。
其中，驱动文件获取请求中包括目标驱动数据的标识。
目标驱动数据的标识用来唯一标识驱动目标驱动器件时所需的目标驱动数据，其可以根据需要任意设置。比如，可以是如Data1、Data2等自定义的字段。在本公开实施例中，获取请求中可以包括N种目标驱动数据的标识，其中N为大于或等于1的正整数。
相应的，主机20可以在监测到触控与显示驱动器10上电后，自动将驱动文件发送给触控与显示驱动器10；或者，主机20也可以在接收到触控与显示驱动器10发送的驱动文件获取请求后，再向触控与显示驱动器10发送驱动文件。即，通信接口21还被配置为：获取触控与显示驱动器10发送的驱动文件获取请求，其中获取请求中包括目标驱动数据的标识。
具体的，在触控与显示驱动器10上电后，需要驱动某N个器件时，触控与显示驱动器10即可向主机20发送驱动文件获取请求，其中，获取请求中包含分别驱动该N个器件的N种目标驱动数据的标识，从而主机20在获取到驱动文件获取请求后，可以根据N种目标驱动数据的标识，读取存储在存储器22上的对应的N种目标驱动数据，并发送给触控与显示驱动器10，以使触控与显示驱动器10获取到N种目标驱动数据后，可以对N个目标驱动器件进行驱动。通过根据触控与显示驱动器10发送的驱动文件获取请求，向触控与显示驱动器10发送驱动文件，提高了驱动文件发送的灵活性。
在本公开一种可能的实现形式中，主机20发送的驱动文件可以是根据通信接口对应的协议经过打包处理的文件，即处理器23还被配置为根据通信接口对应的协议将驱动文件进行打包处理。相应的，如图7所示，在步骤502之前，还可以包括：步骤601，根据与触控与显示驱动器10进行通信连接的通信接口协议，将驱动文件进行打包处理。
其中，通信接口对应的协议可以根据需要设置。
具体的，驱动文件中可以包括文件头，文件头中可以包括用于标识驱动文件大小的尺寸位及校验码位，从而在主机20将驱动文件发送给触控与显示驱动器10后，触控与显示驱动器10可以根据尺寸位的尺寸信息，确定触控与显示驱动器10接收文件的过程是否结束，并利用校验码位的校验码，判断接收到的驱动文件是否准确。
即，处理器23还被配置为根据驱动文件的属性，确定与驱动文件对应的文件头，其中，文件头中包括用于标识驱动文件大小的尺寸位及校验码位。
相应的，如图7所示，在步骤601之前，还可以包括：
步骤602，根据驱动文件的属性，确定驱动文件对应的文件头，其中，文件头中包括用于标识驱动文件大小的尺寸位及校验码位。
其中，驱动文件的属性可以包括驱动文件的大小、驱动数据的类别等与驱动文件相关的任意信息。
通过在驱动文件中设置包括标识驱动文件大小的尺寸位及校验码位，保证了驱动文件传输的完整性和可靠性。
本公开实施例提供的主机可以通过通信接口与触控与显示驱动器进行通信连接，通过将驱动文件存储在主机上，再根据需要将驱动文件发送给触控与显示驱动器，以驱动触控与显示驱动器中的触控组件和/或显示组件，降低了FPC的制造工艺难度，减小了制造成本，节省了FPC的空间，为电子设备的轻薄化提供了条件。
下面结合附图8，对本公开实施例提供的触控与显示驱动器驱动方法进行进一步说明。
图8为本公开一个实施例提供的触控与显示驱动器驱动方法的示例信令交互图。
如图8所示，该触控与显示驱动器驱动方法由触控与显示驱动器和主机执行，具体的交互过程如下：
步骤701，触控与显示驱动器向主机发送驱动文件获取请求。
其中获取请求中包括目标驱动数据的标识。
步骤702，主机根据目标驱动数据的标识，获取触控与显示驱动器的驱动文件。
步骤703，主机根据驱动文件的属性，确定驱动文件对应的文件头。
其中，文件头中包括用于标识驱动文件大小的尺寸位及校验码位。
步骤704，主机根据与触控与显示驱动器进行通信连接的通信接口协议，将驱动文件进行打包处理。
步骤705，主机将驱动文件发送给触控与显示驱动器。
步骤706，触控与显示驱动器根据文件头中的驱动文件的大小，确定驱动文件的接收过程结束。
步骤707，触控与显示驱动器根据获取的驱动文件计算第一校验数据。
步骤708，触控与显示驱动器确定第一校验码与第一校验数据一致。
步骤709，触控与显示驱动器利用驱动文件，对触控组件和/或显示组件进行驱动处理。
触控与显示驱动器和主机通过上述交互过程，即可在要驱动触控与显示驱动器中的触控组件和/或显示组件时，由主机将存储在其上的驱动文件发送给触控与显示驱动器，从而实现对触控与显示驱动器中的触控组件和/或显示组件的驱动处理，由此，降低了FPC的制造工艺难度，减小了制造成本，节省了FPC的空间，为电子设备的轻薄化提供了条件。
本公开实施例还提供一种触控显示装置。
图9为本公开一个实施例提供的触控显示装置的示例结构示意图。
如图9所示，该触控显示装置30包括触控与显示驱动器10。
本公开实施例提供的触控显示装置通过将驱动文件存储在主机上，再根据需要从主机获取驱动文件，以驱动触控与显示驱动器中的触控组件和/或显示组件，降低了FPC的制造工艺难度，减小了制造成本，节省了FPC的空间，为电子设备的轻薄化提供了条件。
本公开实施例还提供一种电子设备。
图10为本公开一个实施例提供的电子设备的示例结构示意图。
如图10所示，该电子设备40包括触控与显示驱动器10及主机20。
可以理解的是，电子设备40中还可以包括柔性电路板，触控与显示驱动器10及主机20可以根据需要设置在柔性电路板上。由于将驱动文件存储在主机20上，柔性电路板上无需增加Flash来存储驱动文件，因此降低了FPC的 制造工艺难度，减小了制造成本，节省了FPC的空间，为电子设备的轻薄化提供了条件。
需要说明的是，上述对触控与显示驱动器10及主机20实施例的具体说明，也适用于本公开实施例的电子设备40，此处不再赘述。
本公开实施例提供的电子设备，可以将触控与显示驱动器与主机通过通信接口进行通信连接，并将驱动文件存储在主机上，从而可以根据需要从主机上获取驱动文件，以驱动触控与显示驱动器中的触控组件和/或显示组件，由此，降低了FPC的制造工艺难度，减小了制造成本，节省了FPC的空间，为电子设备的轻薄化提供了条件。
在本说明书的描述中，参考术语“一个实施例”、“一些实施例”、“示例”、“具体示例”、或“一些示例”等的描述意指结合该实施例或示例描述的具体特征、结构、材料或者特点包含于本公开的至少一个实施例或示例中。在本说明书中，对上述术语的示意性表述不必须针对的是相同的实施例或示例。而且，描述的具体特征、结构、材料或者特点可以在任一个或多个实施例或示例中以合适的方式结合。此外，在不相互矛盾的情况下，本领域的技术人员可以将本说明书中描述的不同实施例或示例以及不同实施例或示例的特征进行结合和组合。
此外，术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括至少一个该特征。在本公开的描述中，“多个”的含义是至少两个，例如两个，三个等，除非另有明确具体的限定。
流程图中或在此以其他方式描述的任何过程或方法描述可以被理解为，表示包括一个或更多个用于实现定制逻辑功能或过程的步骤的可执行指令的代码的模块、片段或部分，并且本公开的优选实施方式的范围包括另外的实现，其中可以不按所示出或讨论的顺序，包括根据所涉及的功能按基本同时的方式或按相反的顺序，来执行功能，这应被本公开的实施例所属技术领域的技术人员所理解。
在流程图中表示或在此以其他方式描述的逻辑和/或步骤，例如，可以被认为是用于实现逻辑功能的可执行指令的定序列表，可以具体实现在任何计算 机可读介质中，以供指令执行系统、装置或设备(如基于计算机的系统、包括处理器的系统或其他可以从指令执行系统、装置或设备取指令并执行指令的系统)使用，或结合这些指令执行系统、装置或设备而使用。就本说明书而言，″计算机可读介质″可以是任何可以包含、存储、通信、传播或传输程序以供指令执行系统、装置或设备或结合这些指令执行系统、装置或设备而使用的装置。计算机可读介质的更具体的示例(非穷尽性列表)包括以下：具有一个或多个布线的电连接部(电子装置)，便携式计算机盘盒(磁装置)，随机存取存储器(RAM)，只读存储器(ROM)，可擦除可编辑只读存储器(EPROM或闪速存储器)，光纤装置，以及便携式光盘只读存储器(CDROM)。另外，计算机可读介质甚至可以是可在其上打印所述程序的纸或其他合适的介质，因为可以例如通过对纸或其他介质进行光学扫描，接着进行编辑、解译或必要时以其他合适方式进行处理来以电子方式获得所述程序，然后将其存储在计算机存储器中。
应当理解，本公开的各部分可以用硬件、软件、固件或它们的组合来实现。在上述实施方式中，多个步骤或方法可以用存储在存储器中且由合适的指令执行系统执行的软件或固件来实现。如，如果用硬件来实现和在另一实施方式中一样，可用本领域公知的下列技术中的任一项或他们的组合来实现：具有用于对数据信号实现逻辑功能的逻辑门电路的离散逻辑电路，具有合适的组合逻辑门电路的专用集成电路，可编程门阵列(PGA)，现场可编程门阵列(FPGA)等。
本技术领域的普通技术人员可以理解实现上述实施例方法携带的全部或部分步骤是可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，该程序在执行时，包括方法实施例的步骤之一或其组合。
此外，在本公开各个实施例中的各功能单元可以集成在一个处理模块中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。所述集成的模块如果以软件功能模块的形式实现并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。
上述提到的存储介质可以是只读存储器，磁盘或光盘等。尽管上面已经示出和描述了本公开的实施例，可以理解的是，上述实施例是示例性的，不能理解为对本公开的限制，本领域的普通技术人员在本公开的范围内可以对上述实施例进行变化、修改、替换和变型。

Claims (17)

  1. 一种触控与显示驱动器，包括：
    通信接口，被配置为与主机进行通信连接，以获取驱动文件；以及
    控制器，被配置为利用获取的驱动文件，驱动触控组件和/或显示组件。
  2. 如权利要求1所述的触控与显示驱动器，还包括所述触控组件和/或所述显示组件。
  3. 如权利要求1所述的触控与显示驱动器，其中，所述驱动文件中包括N个数据标识及与所述N个数据标识分别对应的N种驱动数据，其中，N为大于或等于1的正整数；
    所述控制器还被配置为根据所述N个数据标识，确定N个目标驱动器件；并分别利用所述N种驱动数据，对所述N个目标驱动器件进行驱动。
  4. 如权利要求1所述的触控与显示驱动器，其中，所述控制器还被配置为通过所述通信接口向所述主机发送驱动文件获取请求，其中所述驱动文件获取请求中包括目标驱动数据的标识。
  5. 如权利要求1-4任一所述的触控与显示驱动器，其中，所述驱动文件包括文件头，其中所述文件头中包括所述驱动文件的大小及第一校验码；
    所述控制器还被配置为在获取到驱动文件后，根据文件头中的驱动文件的大小，确定所述驱动文件的接收过程是否结束；并根据获取的驱动文件计算第一校验数据；根据第一校验码与第一校验数据是否一致，判断获取的驱动文件是否准确。
  6. 一种主机，包括：
    存储器，被配置为存储用于驱动触控与显示驱动器的驱动文件；
    通信接口，被配置为与触控与显示驱动器进行通信连接；以及
    处理器，被配置为在确定所述触控与显示驱动器上电时，读取存储在所述存储器上的驱动文件，并通过所述通信接口，发送给所述触控与显示驱动器。
  7. 如权利要求6所述的主机，其中，所述通信接口还被配置为：获取所述触控与显示驱动器发送的驱动文件获取请求，其中所述驱动文件获取请求中包括目标驱动数据的标识。
  8. 如权利要求6或7所述的主机，其中，所述处理器还被配置为根据所述通信接口对应的协议将所述驱动文件进行打包处理；
    所述处理器还被配置为根据所述驱动文件的属性，确定所述驱动文件对应的文件头，其中，文件头中包括用于标识所述驱动文件大小的尺寸位及校验码位。
  9. 一种触控显示装置，包括：如权利要求1-5任一所述的触控与显示驱动器。
  10. 一种电子设备，包括：如权利要求1-5任一所述的触控与显示驱动器及如权利要求5-7任一所述的主机。
  11. 一种触控与显示驱动器驱动方法，包括：
    从主机获取驱动文件；
    利用所述驱动文件，对触控组件和/或显示组件进行驱动处理。
  12. 如权利要求11所述的方法，其中，所述驱动文件中包括N个数据标识及与所述N个数据标识分别对应的N种驱动数据，其中，N为大于或等于1的正整数；
    所述对触控组件和/或显示组件进行驱动处理包括：
    根据所述N个数据标识，确定N个目标驱动器件；
    分别利用所述N种驱动数据，对所述N个目标驱动器件进行驱动。
  13. 如权利要求11所述的方法，其中，所述从主机获取驱动文件之前，所述方法还包括：
    向所述主机发送驱动文件获取请求，其中所述驱动文件获取请求中包括目标驱动数据的标识。
  14. 如权利要求11-13任一所述的方法，其中，所述驱动文件包括文件头，其中所述文件头中包括所述驱动文件的大小及第一校验码；
    所述主机获取驱动文件之后，所述方法还包括：
    根据文件头中的驱动文件的大小，确定所述驱动文件的接收过程是否结束；
    根据获取的驱动文件计算第一校验数据；
    根据第一校验码与第一校验数据是否一致，判断获取的驱动文件是否准确。
  15. 一种触控与显示驱动器驱动方法，包括：
    在确定触控与显示驱动器上电时，获取所述触控与显示驱动器的驱动文件；以及
    将所述驱动文件发送给所述触控与显示驱动器。
  16. 如权利要求15所述的方法，其中，所述确定触控与显示驱动器上电包括：
    确定与所述触控与显示驱动器的供电端连接的电源输出电信号；
    或者，
    获取到所述触控与显示驱动器发送的驱动文件获取请求。
  17. 如权利要求15或16所述的方法，其中，所述将所述驱动文件发送给所述触控与显示驱动器之前，所述方法还包括：
    根据与所述触控与显示驱动器进行通信连接的通信接口协议，将所述驱动文件进行打包处理；
    所述将所述驱动文件进行打包处理之前，所述方法还包括：
    根据所述驱动文件的属性，确定所述驱动文件对应的文件头，其中，文件头中包括用于标识所述驱动文件大小的尺寸位及校验码位。
PCT/CN2018/105677 2018-01-02 2018-09-14 触控与显示驱动器、驱动方法、主机及触控显示装置 WO2019134393A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/332,569 US10915200B2 (en) 2018-01-02 2018-09-14 Touch and display driver, driving method, host and touch display apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810002101.0A CN108089758B (zh) 2018-01-02 2018-01-02 触控与显示驱动器、驱动方法、主机及触控显示装置
CN201810002101.0 2018-01-02

Publications (1)

Publication Number Publication Date
WO2019134393A1 true WO2019134393A1 (zh) 2019-07-11

Family

ID=62179879

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/105677 WO2019134393A1 (zh) 2018-01-02 2018-09-14 触控与显示驱动器、驱动方法、主机及触控显示装置

Country Status (3)

Country Link
US (1) US10915200B2 (zh)
CN (1) CN108089758B (zh)
WO (1) WO2019134393A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108089758B (zh) * 2018-01-02 2020-05-15 京东方科技集团股份有限公司 触控与显示驱动器、驱动方法、主机及触控显示装置
CN112860125B (zh) * 2021-03-19 2024-04-16 京东方科技集团股份有限公司 触控显示驱动装置、方法及触控显示装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1450520A (zh) * 2003-04-29 2003-10-22 威盛电子股份有限公司 显示装置、显示系统及其驱动方法
CN1897099A (zh) * 2005-07-13 2007-01-17 三星电子株式会社 显示装置及信息处理系统
US20140253536A1 (en) * 2013-03-05 2014-09-11 Renesas Sp Drivers Inc. Driver ic and display-input device
CN105389144A (zh) * 2014-08-25 2016-03-09 三星电子株式会社 主机和包括主机的多显示器系统
CN108089758A (zh) * 2018-01-02 2018-05-29 京东方科技集团股份有限公司 触控与显示驱动器、驱动方法、主机及触控显示装置

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7495690B2 (en) * 2000-12-01 2009-02-24 Nikon Corporation Image data processing device
US7934660B2 (en) * 2006-01-05 2011-05-03 Hand Held Products, Inc. Data collection system having reconfigurable data collection terminal
US7683856B2 (en) * 2006-03-31 2010-03-23 Sony Corporation E-ink touchscreen visualizer for home AV system
CN101547360B (zh) * 2009-05-08 2010-11-10 南京师范大学 可定位视频文件格式及该格式文件数据的采集方法
JP5431111B2 (ja) * 2009-10-22 2014-03-05 株式会社日立製作所 情報処理装置及びシステム設定方法
JP6202345B2 (ja) * 2012-11-02 2017-09-27 ソニー株式会社 表示制御装置、表示制御方法、およびプログラム
CN102929465B (zh) * 2012-11-12 2016-02-24 汕头超声显示器（二厂）有限公司 一种电容触控显示组件及其制造方法
CN102999216B (zh) * 2012-11-21 2015-10-28 汕头超声显示器（二厂）有限公司 一种低功耗触控显示模块、具有该模块的触控电子装置及其软件系统
TW201423710A (zh) * 2012-12-12 2014-06-16 Rich Ip Technology Inc 以顯示結構提供觸控功能的驅動電路及觸控顯示器
US10110649B2 (en) * 2013-08-01 2018-10-23 Spotify Ab System and method for transitioning from decompressing one compressed media stream to decompressing another media stream
US9639261B2 (en) * 2013-12-04 2017-05-02 Sony Corporation Apparatus and method for controlling a suspended state
KR101623776B1 (ko) * 2013-12-09 2016-06-07 엘지디스플레이 주식회사 터치 디스플레이 드라이버 집적회로 및 터치 표시장치
CN104375711A (zh) * 2014-12-05 2015-02-25 合肥鑫晟光电科技有限公司 一种触控显示面板及触控显示装置
CN105808289B (zh) * 2016-02-29 2019-09-24 联想(北京)有限公司 信息处理方法及电子设备
CN106293233A (zh) 2016-08-12 2017-01-04 武汉华星光电技术有限公司 触控显示器的驱动方法及驱动系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1450520A (zh) * 2003-04-29 2003-10-22 威盛电子股份有限公司 显示装置、显示系统及其驱动方法
CN1897099A (zh) * 2005-07-13 2007-01-17 三星电子株式会社 显示装置及信息处理系统
US20140253536A1 (en) * 2013-03-05 2014-09-11 Renesas Sp Drivers Inc. Driver ic and display-input device
CN105389144A (zh) * 2014-08-25 2016-03-09 三星电子株式会社 主机和包括主机的多显示器系统
CN108089758A (zh) * 2018-01-02 2018-05-29 京东方科技集团股份有限公司 触控与显示驱动器、驱动方法、主机及触控显示装置

Also Published As

Publication number Publication date
US20200174614A1 (en) 2020-06-04
US10915200B2 (en) 2021-02-09
CN108089758A (zh) 2018-05-29
CN108089758B (zh) 2020-05-15

Similar Documents

Publication Publication Date Title
WO2015154636A1 (zh) 对车辆的车身控制模块进行更新的方法、装置、系统及计算机可读存储介质
US20180151003A1 (en) System and method for transferring diagnostic commands to a vehicle
US9454505B2 (en) Chip select (‘CS’) multiplication in a serial peripheral interface (‘SPI’) system
WO2019127781A1 (zh) 基于时序控制器的电压校准方法及校准系统
JP2008539497A (ja) 集積回路間におけるスレーブ装置の装置識別コーディング
US10423566B2 (en) Electronic device and method for controlling external electronic device connected to USB type-C connector
WO2019042323A1 (zh) 多驱动兼容的控制装置和实现方法
CN108803577B (zh) 一种诊断方法、上位机及下位机
JP7383578B2 (ja) タイプ２ｈａｒｑコードブック提供方法及び基地局
WO2019192244A1 (zh) 参数配置方法、装置及显示装置
WO2019134393A1 (zh) 触控与显示驱动器、驱动方法、主机及触控显示装置
US8832538B2 (en) Detecting data transmission errors in an inter-integrated circuit (‘I2C’) system
WO2015176388A1 (zh) 硬盘健康状况处理方法及装置
WO2020046909A1 (en) Aggregated in-band interrupt
US8954634B2 (en) Operating a demultiplexer on an inter-integrated circuit (‘I2C’) bus
CN110554929B (zh) 数据校验方法、装置、计算机设备及存储介质
US20130346763A1 (en) Increasing Data Transmission Rate In An Inter-Integrated Circuit ('I2C') System
US20050024392A1 (en) Apparatus and method providing automatic display control in a multimedia system
BR112019015131A2 (pt) Método de exibição e combinação de registro de mensagem e dispositivo terminal
US20140049572A1 (en) Display Systems With Handshaking for Rapid Backlight Activation
WO2018045835A1 (zh) 一种终端声音修复方法、装置及电子设备
US20210173808A1 (en) Early parity error detection on an i3c bus
US11983134B2 (en) Method for recognizing another electronic device by using plurality of interfaces, and electronic device therefor
US20180113833A1 (en) Board management controller peripheral card, host system with the same, and method for managing host peripheral member by the same
US8832341B2 (en) Dynamically determining a primary or slave assignment based on receiving a power signal from the cable at the port of a device

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18898345

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18898345

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 23.11.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18898345

Country of ref document: EP

Kind code of ref document: A1