POS-based TP driver management method and application thereof

Abstract

The invention discloses a POS-based TP driver management method and application thereof, a touch screen driver framework (TP driver management system) of the scheme realizes hierarchical design of a strategy layer, an interface layer and an implementation layer, so that the strategy layer and the interface layer can be kept unchanged in the process of importing a new TP development, and the implementation layer is not changed. Different TP interaction modes only need to be realized in the implementation layer according to framework requirements, so that the difficulty of maintenance and upgrading is reduced; meanwhile, an efficient anti-interference mechanism is further introduced in the scheme, the TP anti-interference function is automatically started in the non-contact or charging scene of the POS, the stability and accuracy of the touch screen in the high-interference environment are remarkably improved, and the user experience is optimized. According to the scheme, a TP pin input switching mechanism is achieved through design, in the PIN input stage, the TP is prevented from interacting with the TP IC according to the PIN input state, and therefore TP driving abnormity in the PIN input process is avoided; according to the scheme, the increasing requirement of the market for the high-performance touch screen technology can be met.

Description

Technical Field

[0001] The present invention relates to the fields of touch screen driving technology and POS machine control technology, and in particular to a POS-based TP driving management method and application thereof. Background Art

[0002] In the field of smart devices, touch screen technology has become an important way for users to interact. Although the existing technology has met the basic needs of the market to a certain extent, there are still some problems that need to be solved. For example, when the existing touch screen is used, its technology aims to achieve effective control and precise response of the touch screen in smart devices. When driving touch, most of the existing electronic devices establish a communication bridge between the hardware abstraction layer and the operating system to ensure that the user's operation can be accurately recognized and converted into executable commands for the device.

[0003] The existing TP drive management system mainly has the following functions:

[0004] a. Hardware driver: provides basic control instructions for touch screen hardware, including initialization, configuration, and data processing.

[0005] b. Compatibility adaptation: Try to be compatible with touch screen hardware of different models and manufacturers through some basic adaptation measures.

[0006] c. Power management: Implement simple management of the touch screen power supply to adapt to different usage scenarios and energy-saving requirements.

[0007] d. Event handling mechanism: Basic event handling logic is designed to respond to and process user touch operations.

[0008] e. Firmware upgrade support: Provides a way to update firmware to correct defects or introduce new features.

[0009] However, most of the existing TP driver management solutions for POS devices can only implement basic operations and functions, such as simple touch recognition and screen wake-up. At the same time, when the touch screen is applied to electronic devices, it still has the following limitations:

[0010] 1. Compatibility issues: Compatibility issues between different hardware platforms and touch screen ICs complicate porting and maintenance.

[0011] 2. Inconsistent code quality: The quality of driver codes provided by suppliers varies, which increases the difficulty of development and maintenance.

[0012] 3. Lack of modular design: Existing technologies usually do not implement modularization, resulting in poor code reusability and difficulty in expansion and maintenance.

[0013] 4. Insufficient performance optimization: In high-interference environments, the touch screen's stability and accuracy are insufficient.

[0014] 5. Insufficient targeting for POS applications: There is no effective response to special POS application scenarios, such as PIN input scenarios. The main control Soc cannot communicate with TP, and the TP operation will result in abnormal driving.

[0015] Therefore, how to optimize the driver of the existing touch screen driver technology to address the problems of insufficient compatibility, high difficulty in code maintenance, insufficient performance optimization, inflexible firmware upgrades, and limited exception handling capabilities is a research topic with very positive and practical significance. Summary of the invention

[0016] In view of this, the purpose of the present invention is to propose a POS-based TP drive management method and application thereof that has good compatibility and adaptability, strong anti-interference performance, and reliable and stable implementation.

[0017] In order to achieve the above technical objectives, the technical solution adopted by the present invention is:

[0018] A POS-based TP drive management system, used for interactive driving of a POS touch screen, comprising a strategy layer, an interface layer and an implementation layer; the strategy layer is respectively connected to the interface layer and the implementation layer for communication, and the interface layer is connected to the implementation layer for bidirectional communication;

[0019] The strategy layer communicates and interacts with the Input framework of the system user space of the POS machine and is used to implement the logical process driven by TP;

[0020] The interface layer is used to parse the TP-related device tree and export the board-level configuration interface to componentize the TP driver;

[0021] The implementation layer directly communicates and interacts with the TP to implement the interface of the TP differentiation function.

[0022] As a possible implementation mode, further, the strategy layer in this solution implements the TP-driven logical process including: input event reporting, interrupt event processing, event monitoring and processing, and TP-driven initialization process.

[0023] As a preferred implementation option, preferably, the input event described in this scheme includes one or more of touch input and gesture input; the interrupt event includes a touch interrupt event; and the TP driver initialization process includes one or more of loading TP IC driver, configuring GPIO, and power management.

[0024] As a preferred implementation option, preferably, the board-level configuration interface described in this solution includes one or more of GPIO configuration and power supply configuration.

[0025] As a preferred implementation option, preferably, the implementation layer of this solution directly communicates and interacts with the IC of the TP, reads and writes the registers of the TP, so as to implement the interface of the TP differentiated function; the differentiated function includes one or more of firmware upgrade, initialization, and sleep wakeup.

[0026] As a preferred implementation option, preferably, the functions of the interface for implementing the TP differentiation function of the implementation layer described in this solution include at least one of touch event analysis, firmware upgrade, and sleep wakeup.

[0027] The technical starting points of this solution's TP drive management system can be summarized as follows:

[0028] a. For the universal driver framework: This solution improves the compatibility and portability in different hardware and software environments by designing a modular universal driver framework.

[0029] b. For enhanced compatibility management: This solution introduces advanced hardware abstraction and interface standardization technologies to simplify the cross-platform porting and hardware adaptation process.

[0030] c. Design for modularity and standardization: This solution implements clear stratification of the strategy layer, interface layer, and implementation layer, enhancing the readability and maintainability of the code.

[0031] d. Performance optimization: This solution designs an efficient anti-interference mechanism for high-interference environments, which significantly improves the stability and accuracy of the touch screen.

[0032] e. Aiming at friendly POS application scenarios: This solution is designed for POS application scenarios and implements a PIN input touch switching solution to avoid TP abnormalities after PIN input is completed.

[0033] Through these technical measures, this solution not only improves the performance and reliability of the touch screen driver, but also provides users with a more stable and friendly user experience, meeting the market demand for high-performance touch screen technology.

[0034] Based on the above, the present solution also provides a POS-based TP drive management method, which is applied with the above-mentioned POS-based TP drive management system, and includes:

[0035] S01, the implementation layer provides interfaces for implementing TP differentiation functions;

[0036] S02, converting the initial driver of the TP to the implementation layer, so that it is implemented according to the corresponding interface provided by the driver framework of the implementation layer, so that the TP and the implementation layer can communicate and interact directly;

[0037] S03, the strategy layer monitors TP events through the interface layer;

[0038] S04. TP notifies the policy layer of the user's input operation through an interrupt. The policy layer then converts the input operation into information that can be parsed by the implementation layer. The policy layer then converts the user's input operation into coordinates by calling the implementation layer-driven input event parsing function. The policy layer then obtains the coordinates and reports them to the Input subsystem of the POS machine.

[0039] Based on the above, the present solution also provides a POS machine, which is applied with the above-mentioned POS-based TP drive management system.

[0040] Based on the above, the present solution also provides a touch POS machine working method, which applies the above-mentioned POS-based TP drive management method.

[0041] This solution designs a universal touch screen driver framework, which can adapt to different Soc platforms through modular and standardized design, simplifying the cross-platform transplantation and hardware adaptation process. The touch screen driver framework (TP driver management system) of this solution implements a hierarchical design of the strategy layer, interface layer and implementation layer, so that when introducing a new TP development process, the strategy layer and interface layer can be kept unchanged, and only different TP interaction methods need to be implemented in the implementation layer according to the framework requirements, reducing the difficulty of maintenance and upgrading; at the same time, this solution also introduces an efficient anti-interference mechanism, which automatically starts the TP anti-interference function when the POS is turned on in a contactless or charging scenario, significantly improving the stability and accuracy of the touch screen in a high-interference environment and optimizing the user experience. This solution also implements the TP pin input switching mechanism by design. In the PIN input stage, TP avoids interacting with TP IC according to the PIN input status, thereby avoiding the occurrence of TP driver anomalies during the PIN input process; this application provides an efficient, stable and user-friendly touch screen driver solution that can meet the market's growing demand for high-performance touch screen technology.

[0042] By adopting the above technical solution, the present invention has the following beneficial effects compared with the prior art:

[0043] 1. Improve compatibility: This solution achieves wide compatibility with a variety of touch screen hardware through abstract design, which is particularly prominent in the cross-platform transplantation and adaptation process. Compared with the existing technology, the present invention reduces at least 30% of the adaptation workload and significantly reduces the compatibility issues caused by hardware differences.

[0044] 2. Enhanced code maintainability: Using modular design concepts, the present invention decomposes the touch screen driver into independent, functionally clear modules, which greatly improves the readability and maintainability of the code. Compared with the prior art, modular design reduces maintenance costs and time by more than 50%.

[0045] 3. Shorten the development cycle: The modular design and hardware abstraction layer of the present invention greatly shorten the adaptation and development cycle of the new hardware platform. Compared with the prior art, the present invention can shorten the adaptation time of the new platform by more than 50%.

[0046] 4. Reduce labor intensity: The exception handling framework of the present invention reduces the workload of technicians in problem diagnosis and repair, and reduces labor intensity. Compared with the prior art, the exception handling time is reduced by more than 60%.

[0047] In summary, this solution provides a TP universal driver framework, which can effectively solve the problems faced by existing TP drivers, improve the compatibility, maintainability and portability of TP drivers, shorten the product development cycle, and improve production and shipment efficiency. It has important practical value and application prospects. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0049] Figure 1 This is a schematic diagram of the connection between the newland-tpd driver, the driver management system of this solution, and other hierarchical communication architectures in the POS machine;

[0050] Figure 2 This is a schematic diagram of the software layer structure of the newland-tpd driver, a driver management system in this solution;

[0051] Figure 3 This is a schematic diagram of the logical order of event processing for the policy layer (nl_tpd_core) in this solution;

[0052] Figure 4 This is a schematic diagram of the logical order in which this solution processes the interface layer (nl_tpd_loader);

[0053] Figure 5 This is a schematic diagram of the logical order in which this solution processes the implementation layer (tpd);

[0054] Figure 6 This is a schematic diagram of the working logic of TP driver management in sleep and wake-up of this solution;

[0055] Figure 7 This is a schematic diagram of the working logic of TP driver management in touch event processing.

[0056] Figure 8 This is a schematic diagram of the working logic of TP driver management on Pin input switching;

[0057] Fig. 9 This is one of the partial working logic diagrams of TP driver management on charging / RF status notification;

[0058] Fig.10 This is the second schematic diagram of the local working logic of TP driver management on charging / RF status notification. DETAILED DESCRIPTION

[0059] The present invention will be further described in detail below in conjunction with the accompanying drawings and examples. It is particularly noted that the following examples are only used to illustrate the present invention, but are not intended to limit the scope of the present invention. Similarly, the following examples are only partial embodiments of the present invention rather than all embodiments, and all other embodiments obtained by those of ordinary skill in the art without creative work are within the scope of protection of the present invention.

[0060] Combination Figure 1 As shown, it shows the schematic diagram of the driver management system newland-tpd driver in the POS machine interacting with other hierarchical communication architectures; at the same time, combined with Figure 2 As shown, the scheme of this embodiment is based on the POS TP drive management system newland-tpd driver, which is used for interactive driving of the POS touch screen, and includes a strategy layer (nl_tpd_core), an interface layer (nl_tpd_loader) and an implementation layer (tpd); the strategy layer (nl_tpd_core) is communicated with the interface layer (nl_tpd_loader) and the implementation layer (tpd) respectively, and the interface layer (nl_tpd_loader) is bidirectionally communicated with the implementation layer (tpd);

[0061] Among them, the strategy layer communicates and interacts with the Input framework of the system user space of the POS machine, and is used to implement the logical process of TP driver; the interface layer is used to parse the TP-related device tree and export the board-level configuration interface to componentize the TP driver; the implementation layer communicates and interacts directly with TP to implement the interface of TP differentiated functions.

[0062] This solution proposes an innovative modular design method, which decomposes the touch screen driver into three independent functional module drivers: strategy layer, interface layer and implementation layer. This layered architecture allows each module driver to be independently developed, tested and upgraded, greatly improving the maintainability and scalability of the system.

[0063] As for hardware abstraction technology: This solution can define a unified hardware interface through the interface layer, which achieves wide compatibility with different touch screen hardware and reduces the complexity of cross-platform migration. The hardware abstraction strategy layer can intelligently identify and adapt to various hardware platforms, providing a universal hardware interaction method.

[0064] In this solution, the strategy layer (nl_tpd_core) is responsible for interacting with the upper-layer input framework and implementing the logical process of TP driver, which includes: input event reporting, interrupt event processing, event monitoring and processing, and TP driver initialization process. This layer does not interact directly with the hardware to ensure decoupling from the hardware.

[0065] In this solution, the input events in the strategy layer (nl_tpd_core) include at least one of touch input and gesture input; the interrupt events include touch interrupt events; and the TP driver initialization process includes at least one of loading TP IC driver, configuring GPIO, and power management.

[0066] In this solution, the interface layer (nl_tpd_loader) is responsible for parsing the TP-related board-level device tree (dts) and exporting the board-level configuration interface to realize the componentization of the TP driver. This layer is closely related to the specific board-level hardware and is responsible for the abstraction and configuration of the hardware to ensure that the TP driver is compatible with different hardware platforms.

[0067] Among them, as a better implementation option, preferably, the board-level configuration interface described in this solution includes one or more of GPIO configuration and power supply configuration.

[0068] In this solution, the implementation layer (tpd) is responsible for interacting directly with TP and implementing interfaces for TP's differentiated functions, such as touch event analysis, firmware upgrade, sleep wakeup, etc. This layer maintains a certain degree of independence. In addition to implementing the basic functions of TP, which must comply with the framework regulations, other functions can be implemented according to the original TP driver's provision method to ensure compatibility with the general framework and maintain a certain degree of flexibility.

[0069] As a preferred implementation option, preferably, the implementation layer of this solution directly communicates and interacts with the IC of the TP, reads and writes the registers of the TP, so as to implement the interface of the TP differentiated function; the differentiated function includes one or more of firmware upgrade, initialization, and sleep wakeup.

[0070] As a preferred implementation option, preferably, the functions of the interface for implementing the TP differentiation function of the implementation layer described in this solution include at least one of touch event analysis, firmware upgrade, and sleep wakeup.

[0071] Based on the above, the aspects of the drive management system of this solution that are different from the prior art include the following:

[0072] (1) Modular and hierarchical design: Compared with the existing TP driver, the present invention adopts modular and hierarchical design, dividing the TP driver into a strategy layer driver, an interface layer driver, and an implementation layer driver, each of which performs its own function without interfering with each other;

[0073] (2) Interface standardization: This solution can ensure that the TP driver is compatible with different hardware platforms and facilitates interaction with other modules by defining a unified interface specification.

[0074] (3) Decoupling of the strategy layer from the hardware: The strategy layer of this solution does not interact directly with the hardware, but implements its functions by calling the interface of the interface layer, thereby ensuring the uniformity of the interface.

[0075] (4) The implementation layer maintains independence: The implementation layer of this solution maintains a certain degree of independence. In addition to implementing the basic functions of TP, which must comply with the framework regulations, other functions can be implemented according to the original TP driver's provision method to ensure compatibility with the general framework and maintain a certain degree of flexibility.

[0076] Based on the above, the present solution also provides a POS-based TP drive management method, which is applied with the above-mentioned POS-based TP drive management system, and includes:

[0077] S01, the implementation layer provides interfaces for implementing TP differentiation functions;

[0078] S02, converting the initial driver of the TP to the implementation layer, so that it is implemented according to the corresponding interface provided by the driver framework of the implementation layer, so that the TP and the implementation layer can communicate and interact directly;

[0079] S03, the strategy layer monitors TP events through the interface layer;

[0080] S04. TP notifies the policy layer of the user's input operation through an interrupt. The policy layer then converts the input operation into information that can be parsed by the implementation layer. The policy layer then converts the user's input operation into coordinates by calling the implementation layer-driven input event parsing function. The policy layer then obtains the coordinates and reports them to the Input subsystem of the POS machine.

[0081] The strategy layer, interface layer, and implementation layer of the TP driver management system of this solution can be used to achieve the following functional effects.

[0082] Combination Figure 3 As shown, the policy layer nl_tpd_core driver can achieve the following functional effects:

[0083] (1) Implement an input event reporting mechanism to report TP input events (such as touch, gesture, etc.) to the system.

[0084] (2) Implement an interrupt event handling mechanism. When the TP IC generates an interrupt (such as detecting a touch event), handle these interrupts and execute corresponding logic.

[0085] (3) Implement event monitoring and processing mechanisms to monitor device sleep and wake-up, gesture wake-up switches, RF / Charger status changes, Pin input events, etc., and perform corresponding operations based on the events.

[0086] (4) Implement the TP driver initialization process, including loading the TP IC driver, configuring GPIO, power management, etc.

[0087] Combination Figure 4 As shown, the interface layer nl_tpd_loader driver can achieve the following functional effects:

[0088] (1) Parse the TP-related board-level device tree (dts) and export the board-level configuration interface, such as GPIO configuration, power configuration, etc.

[0089] (2) Maintain TP IC components to facilitate the management of TP IC component matching and compatibility.

[0090] Combination Figure 5 As shown, the implementation layer tpd driver can achieve the following functional effects:

[0091] (1) Interact with the TP IC to read and write TP registers to implement various functions of the touch screen.

[0092] (2) Realize the differentiated functions of TP, such as firmware upgrade, initialization, sleep and wake-up, etc.

[0093] (3) Provide a firmware upgrade interface that can update the TP firmware to fix errors or introduce new features.

[0094] (4) Provide an initialization interface and be responsible for the TP initialization process, including configuring TP registers, setting working modes, etc.

[0095] (5) Provide a sleep and wake-up interface to implement the sleep and wake-up functions of TP.

[0096] As for the touch screen TP adaptation, as an example, this solution can use the framework to implement TP driving through the following methods:

[0097] a. TP driver manufacturer: The TP driver manufacturer develops TP driver programs that comply with the interface specifications provided by the present invention.

[0098] b. POS manufacturers: Convert the drivers provided by TP manufacturers according to the implementation layer of the TP general driver framework, and provide the implementation of the corresponding interface according to the tpd driver framework. The strategy layer and interface layer do not need to be changed.

[0099] c. Actual operation: When the user touches the screen, TP will notify nl_tpd_core (policy layer) through an interrupt, and then the nl_tpd_core driver will convert it into coordinates by calling the tpd driver input event parsing function, and then report it to the upper Android system through the Linux input subsystem.

[0100] Combination Figure 6 As shown in the figure, in order to ensure the independence of the tpd driver, that is, to decouple it from the LCD status acquisition mechanism of a specific platform, the implementation layer tpd driver of this solution is not directly associated with the LCD status. Instead, this task is completed by the policy layer nl_tpd_core. The policy layer nl_tpd_core notifies the tpd driver when to enter or exit the sleep state through event calls. This design enables the implementation layer tpd driver to work without knowing the underlying LCD status acquisition mechanism, thereby improving the versatility and portability of the driver.

[0101] In this solution, the strategy layer nl_tpd_core acts as an intermediate layer, which is responsible for monitoring the notifications of the input touch screen and converting them into event calls that the implementation layer tpd driver can understand, thereby implementing the logic of sleep and wake-up. This design allows the implementation layer tpd driver to work seamlessly on different platforms without the need for special modifications for each platform.

[0102] Combination Figure 7 As shown, in the touch event processing, the strategy layer nl_tpd_core driver of this solution is responsible for registering the interrupt processing function so as to be able to process the interrupt signal reported by the touch screen TP.

[0103] The work process at the strategy layer includes:

[0104] When TP detects a touch event, it notifies the strategy layer nl_tpd_core driver through an interrupt signal.

[0105] The strategy layer nl_tpd_core driver calls the touch event processing function provided by the tpd driver in the interrupt processing function.

[0106] In this way, the strategy layer nl_tpd_core obtains the specific coordinate information of the touch event.

[0107] Finally, the policy layer nl_tpd_core reports the coordinate information to the upper layer (e.g., the Linux kernel's input subsystem) through the input device it initializes and registers.

[0108] In the implementation layer tpd, it includes:

[0109] The implementation layer tpd driver is responsible for reading the coordinate register corresponding to the TP, which contains the original data of the touch event.

[0110] The implementation layer tpd parses the data returned from TP and converts the data into specific coordinate information.

[0111] These coordinate information are then passed to the policy layer nl_tpd_core driver for subsequent reporting processing.

[0112] Combination Figure 8 As shown, for Pin input switching, this solution drives the management system including the following mechanisms:

[0113] a. Status notification mechanism:

[0114] ■When the pin input state changes (e.g., switching from touchscreen control to security module control), the payment service notifies the TP driver by updating the sysfs node or the kernel notifer mechanism;

[0115] b.TP drive response:

[0116] ■TP driver monitors the status changes of sysfs nodes or callback kernel notifer.

[0117] ■According to the state change, the TP driver will adjust its internal logic to adapt to the current state of the touch screen pin.

[0118] ■For example, if the node status indicates that the touch screen pin is under the control of the security module, the TP driver will suspend or adjust the sleep wake-up and ESD check processes.

[0119] c. Strategies to avoid abnormal problems:

[0120] ■The TP driver will decide whether to continue the sleep wake-up and ESD check process based on the status of the sysfs node or kernel notifer.

[0121] ■When the touch screen pins are under the control of the security module, the TP driver may need to postpone or skip these processes until the state of the touch screen pins returns to normal control.

[0122] d.Recovery and reset:

[0123] ■When the status of the touch screen pin returns to normal control, the payment service will update the status through the sysfs node or kernelnotifer.

[0124] ■The TP driver will restart or continue the sleep wake-up and ESD check process according to the new status to ensure the normal operation of the touch screen.

[0125] For PIN input switching, this solution implements the status notification of PIN input switching through sysfs node and kernel notifier mechanism, avoiding abnormal problems of TP driver during PIN input switching.

[0126] In terms of compatibility design, in this solution, the TP IC driver is added to the linked list as a component driver during initialization: this mechanism ensures that each TP IC driver has the opportunity to be loaded and configured in the correct order when the system starts.

[0127] Furthermore, the Linux DRM framework can be combined to bind the TP IC driver and panel information. This mechanism optimizes the initialization sequence, speeds up the matching speed, and improves the system startup efficiency.

[0128] This solution can be modularized through TP driver and asynchronously loaded in the init stage. This mechanism reduces the impact of compatibility matching on system boot time and optimizes the startup speed.

[0129] In the core logic of the strategy layer, the strategy layer of this solution can define the overall behavior and logic flow of the touch screen driver, including key functions such as event recognition and gesture analysis. The present invention implements a set of advanced logic processing algorithms at the strategy layer to optimize the response speed and accuracy of touch operations.

[0130] In terms of the standardized design of the interface layer, as a key part of hardware abstraction, the interface layer of this solution provides a set of standardized interfaces for the strategy layer to call. The interface layer design of this solution takes into account the characteristics of different hardware platforms and can flexibly adapt to various touch screen hardware.

[0131] The interface specification includes data structure definition, function interface design, parameter passing method, return value definition, etc. The specification describes each aspect of the interface in detail to ensure the consistency and operability of the interface.

[0132] In terms of the differentiated functional implementation of the implementation layer, the implementation layer of this solution implements the collection, processing and reporting of touch events according to the specific touch screen hardware characteristics. The present invention adopts a differentiated design method in the implementation layer to ensure accurate control of various hardware platforms.

[0133] Based on the above, the present solution also provides a POS machine, which is applied with the above-mentioned POS-based TP drive management system.

[0134] At the same time, the solution also provides a touch POS machine working method, which applies the above-mentioned POS-based TP drive management method.

[0135] Combination Fig. 9 or Fig.10 As shown, on the POS machine, for charging / RF status notification, this solution includes the following:

[0136] For charging and RF status, a status notification mechanism can be designed through the Linux notify mechanism. The power adapter status notification is implemented by the Linux power_supply native framework, while the RF status is implemented through the payment service driver through a custom notify mechanism.

[0137] In terms of charging / RF status notification, this solution implements charging and RF status notification through the Linux notify mechanism, which can be optimized for high-interference scenarios and improve the stability of the TP driver in scenarios such as contactless opening / adapter insertion.

[0138] The above descriptions are only some embodiments of the present invention, and are not intended to limit the protection scope of the present invention. Any equivalent device or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A POS-based TP drive management system for interactive driving of a POS touch screen, characterized in that: It includes a strategy layer, an interface layer and an implementation layer; the strategy layer is connected to the interface layer and the implementation layer for communication respectively, and the interface layer is connected to the implementation layer for bidirectional communication; The strategy layer communicates and interacts with the Input framework of the system user space of the POS machine and is used to implement the logical process driven by TP; The interface layer is used to parse the TP-related device tree and export the board-level configuration interface to componentize the TP driver; The implementation layer directly communicates and interacts with the TP to implement the interface of the TP differentiation function.

2. The POS-based TP drive management system according to claim 1, characterized in that: The strategy layer implements the TP-driven logical process including: input event reporting, interrupt event processing, event monitoring and processing, and TP-driven initialization process.

3. The POS-based TP drive management system according to claim 2, characterized in that: The input event includes one or more of touch input and gesture input; The interruption event includes a touch interruption event; The TP driver initialization process includes loading TPIC driver, configuring GPIO, and power management.

4. The POS-based TP drive management system according to claim 1, characterized in that: The board-level configuration interface includes at least one of GPIO configuration and power supply configuration.

5. The POS-based TP drive management system according to claim 1, characterized in that: The implementation layer directly communicates and interacts with the IC of the TP, reads and writes the registers of the TP, so as to implement the interface of the TP differentiation function; The differentiated functions include one or more of firmware upgrade, initialization, and sleep and wake-up.

6. The POS-based TP drive management system according to claim 1, characterized in that: The functions of the interface of the implementation layer to implement the TP differentiation function include at least one of touch event analysis, firmware upgrade, and sleep wakeup.

7. A POS-based TP drive management method, which uses the POS-based TP drive management system according to any one of claims 1 to 6, characterized in that: It includes: The implementation layer provides interfaces to implement TP differentiation functions; Convert the initial driver of TP to the implementation layer, and make it implement the corresponding interface provided by the driver framework of the implementation layer, so that TP can communicate and interact directly with the implementation layer; The strategy layer monitors TP events through the interface layer; TP notifies the policy layer of the user's input operation through interruption, and then the policy layer converts the input operation into information that can be parsed by the implementation layer. The user's input operation is then converted into coordinates by calling the implementation layer-driven input event parsing function. The policy layer then obtains the coordinates and reports them to the Input subsystem of the POS machine.

8. A POS machine, characterized in that: The invention is applied with the POS-based TP drive management system as claimed in any one of claims 1 to 6.

9. A touch POS machine working method, characterized in that: The application thereof includes the POS-based TP drive management method described in claim 7.

Images