Touch screen failure processing method and device and computer readable storage medium
By detecting abnormal messages and link status of touch chips in the in-vehicle infotainment system, automatic processing of touch screen failure is achieved, the problem of touch screen failure is solved, and user experience and system stability are improved.
Patent Information
- Application Number
- CN202411997402.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-31
- Publication Date
- 2025-05-02
AI Technical Summary
In the in-vehicle infotainment system, due to environmental interference and other factors, the problem of touch screen failure is more prominent, resulting in users being unable to operate the system, causing serious problems.
A method for handling touch screen failure is proposed. By receiving abnormal messages from the touch chip, the link state between the serialized driver and the deserialized driver is detected. If the link state is normal, the touch chip is reset. Otherwise, the deserialized driver is reloaded and the touch driver is reloaded.
It effectively prevents touch screen failure, improves the experience of touch screen operation and real-time interaction, and realizes an efficient, low-cost and adaptive touch screen failure treatment solution.
Smart Images

Figure CN119916965A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of display screen technology, and in particular to a method and device for processing touch screen failure, and a computer-readable storage medium. Background Art
[0002] like Figure 1 As shown, the existing in-vehicle infotainment system (IVI for short), especially the IVI-based SOC (System on Chip, main control chip) and the screen end adopt the industry's mainstream LVDS (Low-Voltage Differential Signaling, low voltage differential signal) transmission medium, such as GMSL (Gigabit Multimedia Serial Links, Gigabit Multimedia Serial Link) or FPD-LINK (Flat Panel Display Link, a high-speed digital video interface standard), which can achieve high-speed long distance, ultra-high definition, differential signal anti-interference, multi-channel, and low-latency technical effects. On the one hand, it provides users with a high-definition digital and intelligent sense of technological interaction, but on the other hand, the vehicle environment cannot completely avoid electrical interference, such as electrostatic discharge, strong electromagnetic interference or voltage fluctuations, environmental factors such as extreme temperature changes and humidity changes, hardware failures, etc., which may cause a certain probability of occasional touch screen failure, resulting in serious problems that users cannot operate IVI.
[0003] Therefore, how to effectively prevent the touch screen from failing has become a technical problem that needs to be solved urgently. Summary of the invention
[0004] In order to overcome the deficiencies in the prior art, the purpose of the present invention is to provide a method for solving the problem of touch screen failure caused by environmental interference when the current IVI-based SOC and the screen end are linked using LVDS.
[0005] The present invention proposes a method for processing touch screen failure, which is applied to a serialization chip, wherein the serialization chip is connected to a deserialization chip, the serialization chip is also used to connect to a main control chip, and the deserialization chip is also used to connect to a touch control chip, wherein the serialization chip runs a serialization drive, the deserialization chip runs a deserialization drive, and the touch control chip runs a touch control drive. The method includes:
[0006] Receiving an abnormal message related to the touch chip sent by the touch driver;
[0007] Detecting whether the link status between the deserialization driver and the serialization driver is normal;
[0008] If the link status is normal, reset the touch chip first, otherwise reload the deserialization driver first;
[0009] Reload the touch driver.
[0010] Optionally, the serialization driver is also used to maintain a preset first kernel thread;
[0011] The first kernel thread is used to monitor the exception message.
[0012] Optionally, the touch driver is further used to maintain a preset second kernel thread;
[0013] The second kernel thread is used to generate the exception message.
[0014] Optionally, the second kernel thread is further used for:
[0015] When the touch chip supports a heartbeat detection interface, the heartbeat data of the touch chip is read in real time through the heartbeat detection interface;
[0016] or,
[0017] When the touch information does not support the heartbeat detection interface, the hardware data of the touch chip is read periodically through the integrated circuit bus.
[0018] Optionally, when the second kernel thread is used to read the heartbeat data of the touch control chip in real time through the heartbeat detection interface:
[0019] If the second kernel thread fails to read the heartbeat data within a preset period, the exception message is generated.
[0020] Optionally, when the second kernel thread is used to periodically read the hardware data of the touch control chip through the integrated circuit bus:
[0021] If the hardware data reading status of the second kernel thread meets a preset condition, the exception message is generated.
[0022] Optionally, the deserialization driver is further used for:
[0023] The heartbeat data or the hardware data is deserialized so that the touch control chip receives a reset signal and the touch control driver is reloaded.
[0024] Optionally, the otherwise reloading the deserialization driver further comprises:
[0025] If the link status is abnormal, the deserialization driver is reloaded first, and then the touch chip is reset.
[0026] The present invention also proposes a touch screen failure processing device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, the steps of the touch screen failure processing method as described in any one of the above items are implemented.
[0027] The present invention also proposes a computer-readable storage medium, on which a touch screen failure processing program is stored. When the touch screen failure processing program is executed by a processor, the steps of the touch screen failure processing method as described in any one of the above items are implemented.
[0028] The method, device and computer-readable storage medium for handling touch screen failure of the present invention are implemented by receiving an abnormal message related to the touch chip sent by the touch driver; detecting whether the link status between the deserialization driver and the serialization driver is normal; if the link status is normal, resetting the touch chip first, otherwise reloading the deserialization driver first; reloading the touch driver. The present invention realizes an efficient, low-cost and adaptive touch screen failure handling solution, effectively preventing touch screen failure, improving the experience of touch screen operation, and enhancing the real-time nature of touch screen interaction. BRIEF DESCRIPTION OF THE DRAWINGS
[0029] The present invention will be further described below with reference to the accompanying drawings and embodiments, in which:
[0030] Figure 1 This is a schematic diagram of the existing touch screen hardware connection;
[0031] Figure 2 is a flow chart of a method for handling touch screen failure of the present invention;
[0032] Figure 3 It is a schematic diagram of driver software control of the touch screen failure processing method of the present invention. DETAILED DESCRIPTION
[0033] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.
[0034] In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present invention, and have no specific meanings. Therefore, "module", "component" or "unit" can be used in a mixed manner.
[0035] Figure 2This is the first flow chart of the method for handling touch screen failure of the present invention. This embodiment proposes a method for handling touch screen failure, which is applied to a serialization chip, wherein the serialization chip is connected to a deserialization chip, the serialization chip is also used to connect to a main control chip, and the deserialization chip is also used to connect to a touch control chip, wherein the serialization chip runs a serialization drive, the deserialization chip runs a deserialization drive, and the touch control chip runs a touch control drive, and the method includes:
[0036] S1. receiving an abnormal message related to the touch chip sent by the touch driver;
[0037] S2, detecting whether the link status between the deserialization driver and the serialization driver is normal;
[0038] S3. If the link status is normal, reset the touch chip first, otherwise reload the deserialization driver first;
[0039] S4. Reload the touch driver.
[0040] In this embodiment, IVI adopts a machine and screen separation mode, that is, the SOC and the screen end are connected using an LVDS (GMSL or FPD-LINK) signal line. The signal of this link is a differential signal, which is used to support data transmission of video, audio, and control signals. The SOC is not directly connected to the TOUCH IC (i.e., touch chip), but directly connected to the SER (i.e., serial chip); based on this, the IVI host-side data of this embodiment is first sent to the SER serialization chip, then packaged by the SER serialization chip, and finally sent to the touch screen end through LVDS.
[0041] In this embodiment, the touch screen end integrates an LCD display and a TOUCH touch screen, wherein the TOUCH IC of the touch screen end is connected to the DES (i.e., the deserialization chip); based on this, in this embodiment, first, the touch screen end receives the LVDS differential signal through the DES, and sends the current touch screen data to the DES, and then the DES sends it to the IVI host end.
[0042] In this embodiment, the SER driver (i.e., the serialization driver) is used for data packaging and parsing, and interacts with the DES (deserialization chip), and the DES is used to directly connect to the LCD and the TOUCH IC. The corresponding DES driver (i.e., the deserialization driver) is used to deserialize the video data and send it to the LCD, and bridge the TOUCH IC. Based on this, in this embodiment, the DES receives the I2C bus or IO interface data of the TOUCH IC and sends it to the SER. The TOUCH driver (i.e., the touch driver) initializes the touch screen and returns data, and the SER driver is used to keep the DES and the TOUCH IC alive.
[0043] Specifically, in this embodiment, first, the serialization driver of the serialization chip receives the abnormal message related to the touch chip sent by the touch driver; then, the serialization driver detects whether the link status between the deserialization driver and the serialization driver is normal. If the link status is normal, the touch chip is reset first, and then the touch driver is reloaded; if the link status is abnormal, the deserialization driver is reloaded first, and then the touch driver is reloaded.
[0044] It can be seen that in this embodiment, on the one hand, by timely performing link detection and recovery when the touch screen fails, the stability of the touch screen system is improved, and the application experience of touch screen products in various extremely harsh environments is enhanced. In addition, even if the touch screen fails due to environmental or other factors, the user does not need to worry, because the touch screen can be adaptively restored through the above solution, so that the touch screen can maintain normal working state for a long time.
[0045] The beneficial effect of this embodiment is that by receiving the abnormal message related to the touch chip sent by the touch driver, detecting whether the link status between the deserialization driver and the serialization driver is normal, if the link status is normal, first resetting the touch chip, then reloading the touch driver; if the link status is abnormal, first reloading the deserialization driver, then reloading the touch driver. This effectively prevents touch screen failure, improves the experience of touch screen operation, and enhances the real-time nature of touch screen interaction.
[0046] Please refer to Figure 3In this embodiment, the serialization driver is also used to maintain a preset first kernel thread; the first kernel thread is used to monitor the abnormal message. Further, in this embodiment, the touch driver is also used to maintain a preset second kernel thread; the second kernel thread is used to generate the abnormal message. That is, in addition to the traditional driver function (i.e., packaging and transmitting video data, audio data, I2C and IO data), the SER driver also needs to maintain a kernel thread kthread for monitoring abnormal event messages from the TOUCH driver. Based on this, step 1, when the kernel thread kthread receives the abnormal message from the TOUCH IC, recheck whether the DES link is normal; step 2, if the link is normal, the kernel thread kthread controls the TOUCH IC to reset, that is, reset the TOUCH IC, and re-initialize the TOUCH driver; step 3, if the link is abnormal, the kernel thread kthread controls the DESdriver to reload, and then the kernel thread kthread controls the TOUCH IC to reset. Therefore, this embodiment enables the abnormal message to reach the deserialization driver in a timely and effective manner, thereby avoiding the situation where the current touch screen abnormality problem cannot be known when the link is disconnected.
[0047] In this embodiment, the second kernel thread is also used to: when the touch chip supports the heartbeat detection interface, read the heartbeat data of the touch chip in real time through the heartbeat detection interface; or, when the touch information does not support the heartbeat detection interface, read the hardware data of the touch chip regularly through the integrated circuit bus. Further, in this embodiment, when the second kernel thread is used to read the heartbeat data of the touch chip in real time through the heartbeat detection interface: if the second kernel thread does not read the heartbeat data within a preset period, the abnormal message is generated. In this embodiment, when the second kernel thread is used to read the hardware data of the touch chip regularly through the integrated circuit bus: if the second kernel thread meets the preset conditions for the hardware data reading state, the abnormal message is generated. That is, TOUCH IC adds heartbeat IO to facilitate signal detection, and if TOUCH IC does not support IO, I2C (Inter-Integrated Circuit, integrated circuit bus) is used for reading. Moreover, the DES driver of this embodiment is used for video data analysis on the one hand, and for deserialization of I2C signals and IO signals on the other hand, so that it can normally probe the TOUCH IC, determine its status, and assist the DES driver to load normally. Similarly, on the TOUCH driver side, a Heartbeat Kthread thread is added to read the heartbeat data of the TOUCH IC in real time, wherein, if the TOUCH IC does not have this IO, the I2C is used to read the device ID regularly, for example, if the above heartbeat signal is not read within 4s, an abnormal message is sent to the SER. Thus, this embodiment enables the touch screen side to flexibly adjust the collection and transmission channels of the keep-alive data currently relied on according to its own interface or bus configuration.
[0048] In this embodiment, the deserialization driver is also used to: deserialize the heartbeat data or the hardware data so that the touch chip receives a reset signal and the touch driver can be reloaded. Further, in this embodiment, if the link status is abnormal, the deserialization driver is reloaded first, and then the touch driver is reloaded, further including: if the link status is abnormal, the deserialization driver is reloaded first, then the touch chip is reset, and finally the touch driver is reloaded. Therefore, by increasing the communication between the SER serializer and the TOUCH IC, when the TOUCH driver is abnormal, the TOUCH driver can promptly and effectively notify the SER driver, and the SER driver checks the status of the current LVDS link. If it is abnormal, a soft reset is performed to relink.
[0049] It can be seen that in this embodiment, when applying the above touch screen failure processing solution, there is no need to increase additional hardware costs, and the software can be implemented using existing interfaces, which greatly improves the stability of the product.
[0050] Based on the above embodiments, the present invention also proposes a touch screen failure processing device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the computer program is executed by the processor, the steps of the touch screen failure processing method as described in any one of the above items are implemented.
[0051] It should be noted that the above-mentioned device embodiment and method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, and the technical features in the method embodiment are correspondingly applicable in the device embodiment, which will not be repeated here.
[0052] Based on the above embodiments, the present invention further proposes a computer-readable storage medium, on which a touch screen failure processing program is stored. When the touch screen failure processing program is executed by a processor, the steps of the touch screen failure processing method as described in any of the above items are implemented.
[0053] It should be noted that the above-mentioned medium embodiment and method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, and the technical features in the method embodiment are correspondingly applicable in the medium embodiment, which will not be repeated here.
[0054] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present invention.
[0055] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.
[0056] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the enlightenment of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the purpose of the present invention and the claims, which all fall within the protection of the present invention.
Claims
1. A method for handling touch screen failure, applied to a serialization chip, wherein the serialization chip is connected to a deserialization chip, the serialization chip is also used to connect to a main control chip, and the deserialization chip is also used to connect to a touch control chip, wherein: The serialization chip runs a serialization drive, the deserialization chip runs a deserialization drive, and the touch control chip runs a touch control drive. The method includes: Receiving an abnormal message related to the touch chip sent by the touch driver; Detect whether the link status between the deserialization driver and the serialization driver is normal; if the link status is normal, reset the touch chip first, otherwise reload the deserialization driver first; Reload the touch driver.
2. The method for handling touch screen failure according to claim 1, characterized in that: The serialization driver is also used to maintain a preset first kernel thread; The first kernel thread is used to monitor the exception message.
3. The method for handling touch screen failure according to claim 1, characterized in that: The touch driver is also used to maintain a preset second kernel thread; The second kernel thread is used to generate the exception message.
4. The method for handling touch screen failure according to claim 3, characterized in that: The second kernel thread is further used for: When the touch chip supports a heartbeat detection interface, the heartbeat data of the touch chip is read in real time through the heartbeat detection interface; or, When the touch information does not support the heartbeat detection interface, the hardware data of the touch chip is read periodically through the integrated circuit bus.
5. The method for handling touch screen failure according to claim 4, characterized in that: When the second kernel thread is used to read the heartbeat data of the touch control chip in real time through the heartbeat detection interface: If the second kernel thread fails to read the heartbeat data within a preset period, the exception message is generated.
6. The method for handling touch screen failure according to claim 4, characterized in that: When the second kernel thread is used to periodically read the hardware data of the touch control chip through the integrated circuit bus: If the hardware data reading status of the second kernel thread meets a preset condition, the exception message is generated.
7. The method for handling touch screen failure according to claim 4, characterized in that: The deserialization driver is also used for: The heartbeat data or the hardware data is deserialized so that the touch control chip receives a reset signal and the touch control driver is reloaded.
8. The method for handling touch screen failure according to claim 1, characterized in that: The first reloading of the deserialization driver further comprises: First reload the deserialization driver, and then reset the touch chip.
9. A touch screen failure processing device, characterized in that: The device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, the steps of the method for processing touch screen failure as described in any one of claims 1 to 8 are implemented.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a touch screen failure processing program, and when the touch screen failure processing program is executed by a processor, the steps of the touch screen failure processing method according to any one of claims 1 to 8 are implemented.