Pos-based tp drive management method and application thereof

Abstract

The application discloses a POS-based TP driving management method and application thereof, a touch screen driving framework (TP driving management system) of the scheme realizes layered design of a strategy layer, an interface layer and an implementation layer, so that in the process of importing a new TP development, the strategy layer and the interface layer can be kept unchanged, and only different TP interaction modes need to be realized in the implementation layer according to the requirement of the framework, and the scheme reduces the difficulty of maintenance and upgrading; meanwhile, the scheme also introduces an efficient anti-interference mechanism, under the condition that a POS opens a non-interface or charging scene, the TP anti-interference function is automatically started, the stability and accuracy of the touch screen in a high-interference environment are significantly improved, and the user experience is optimized. The scheme also realizes a TP pin input switching mechanism through design, in a PIN input stage, the TP avoids interaction with a TP IC according to a PIN input state, so that the occurrence of TP driving abnormity in the PIN input process is avoided; the scheme can meet the increasing demand of the market for high-performance touch screen technology.

Description

Technical Field

[0001] This 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 its application. Background Technology

[0002] In the field of smart devices, touchscreen technology has become an important means of user interaction. While existing technologies meet basic market demands to a certain extent, some problems still need to be addressed. For example, the purpose of current touchscreen technology is to achieve effective control and precise response of the touchscreen in smart devices. When driving touch, most existing electronic devices establish a communication bridge between the hardware abstraction layer and the operating system to ensure that user operations can be accurately recognized and translated into executable commands.

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

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

[0005] b. Compatibility and Adaptation: Attempt to achieve compatibility with touchscreen hardware from different models and manufacturers through some basic adaptation measures.

[0006] c. Power Management: Enables simple management of the touchscreen's power to adapt to different usage scenarios and energy-saving needs.

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

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

[0009] However, most existing POS device TP driver management solutions can only achieve basic operations and functions, such as simple touch recognition and screen wake-up. Furthermore, touchscreens have the following limitations when applied to electronic devices:

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

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

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

[0013] 4. Insufficient performance optimization: The stability and accuracy of the touch screen are insufficient in high interference environments.

[0014] 5. Insufficient targeting for POS applications: There is no effective way to deal with special application scenarios of POS, such as PIN input scenarios. The main control SoC cannot communicate with the TP, and in this case, the operation of the TP will result in driver abnormalities.

[0015] Therefore, optimizing existing touchscreen driver technologies to address issues such as insufficient compatibility, high code maintenance difficulty, inadequate performance optimization, inflexible firmware upgrades, and limited exception handling capabilities is a research topic with significant practical implications. Summary of the Invention

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

[0017] To achieve the above-mentioned technical objectives, the technical solution adopted by this invention is as follows:

[0018] A POS-based TP driver management system for interactive driving of POS machine touch screen includes a strategy layer, an interface layer, and an implementation layer; the strategy layer is communicatively connected to the interface layer and the implementation layer respectively, and the interface layer is bidirectionally communicatively connected to the implementation layer.

[0019] The strategy layer communicates and interacts with the Input framework of the POS machine's system user space and is used to implement the TP-driven logic flow.

[0020] The interface layer is used to parse the TP-related device tree and export the board-level configuration interface to enable the TP driver to be componentized.

[0021] The implementation layer communicates and interacts directly with the TP to implement the interface for the TP's differentiated functions.

[0022] As one possible implementation, the logic flow of the strategy layer implementing TP driving in this solution further includes one or more of the following: input event reporting, interrupt event handling, event listening and handling, and TP driver initialization process.

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

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

[0025] As a preferred implementation option, the implementation layer of this solution directly communicates and interacts with the TP's IC, reading and writing the TP's registers to implement the interface for the TP's differentiated functions; the differentiated functions include one or more of firmware upgrade, initialization, and sleep / wake-up.

[0026] As a preferred implementation option, the interface for implementing the TP differentiated functions in the implementation layer of this solution preferably includes one or more of the following: touch event parsing, firmware upgrade, and sleep / wake-up.

[0027] The technical starting point of this TP driver management system can be summarized as follows:

[0028] a. Regarding the general driver framework: This solution improves compatibility and portability under different hardware and software environments by designing a modular general driver framework.

[0029] b. Enhanced compatibility management: This solution introduces advanced hardware abstraction and interface standardization technologies, simplifying cross-platform porting and hardware adaptation processes.

[0030] c. For modular and standardized design: This solution achieves a clear layering of strategy layer, interface layer and implementation layer, which enhances code readability and maintainability.

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

[0032] e. For POS application scenarios: This solution is designed and implemented for POS application scenarios to avoid TP abnormality issues after PIN input.

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

[0034] Based on the above, this solution also provides a POS-based TP driver management method, which applies the aforementioned POS-based TP driver management system, and includes:

[0035] S01. The implementation layer provides interfaces for implementing TP differentiation functions;

[0036] S02. Convert the initial driver of TP to the implementation layer and make it implement according to the corresponding interface provided by the driver framework of the implementation layer, so that TP and the implementation layer can communicate and interact directly.

[0037] S03. The strategy layer listens for events from the TP through the interface layer.

[0038] S04. TP notifies the policy layer of the user's input operation via an interrupt. The policy layer then converts the input operation into information that the implementation layer can parse. It then calls the implementation layer's input event parsing function to convert the user's input operation into coordinates. The policy layer then obtains the coordinates and reports them to the POS machine's Input subsystem.

[0039] Based on the above, this solution also provides a POS machine that uses the POS-based TP driver management system described above.

[0040] Based on the above, this solution also provides a method for operating a touch POS machine, which applies the POS-based TP driver management method described above.

[0041] This solution designs a universal touchscreen driver framework. Through modular and standardized design, it can adapt to different SoC platforms, simplifying cross-platform porting and hardware adaptation. The touchscreen driver framework (TP driver management system) implements a layered design of strategy, interface, and implementation layers. This allows the strategy and interface layers to remain unchanged during the development of new TPs; only the implementation layer needs to implement different TP interaction methods according to the framework requirements, reducing maintenance and upgrade difficulty. Simultaneously, this solution introduces an efficient anti-interference mechanism. In POS contactless or charging scenarios, the TP anti-interference function is automatically activated, significantly improving the stability and accuracy of the touchscreen in high-interference environments and optimizing the user experience. This solution also designs and implements a TP pin input switching mechanism. During the PIN input phase, the TP avoids interaction with the TP IC based on the PIN input state, thereby preventing TP driver anomalies during the PIN input process. This application provides an efficient, stable, and user-friendly touchscreen driver solution that meets the growing market demand for high-performance touchscreen technology.

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

[0043] 1. Improved Compatibility: This solution achieves broad compatibility with various touchscreen hardware through abstract design, which is particularly prominent in cross-platform porting and adaptation. Compared with existing technologies, this invention reduces the adaptation workload by at least 30% and significantly reduces compatibility issues caused by hardware differences.

[0044] 2. Enhanced Code Maintainability: Employing a modular design concept, this invention decomposes the touchscreen driver into independent, functionally defined modules, greatly improving code readability and maintainability. Compared to existing technologies, the modular design reduces maintenance costs and time by more than 50%.

[0045] 3. Shortened Development Cycle: The modular design and hardware abstraction layer of this invention significantly shorten the adaptation and development cycle for new hardware platforms. Compared with existing technologies, this invention can reduce the adaptation time for new platforms by more than 50%.

[0046] 4. Reduced workload: The anomaly handling framework of this invention reduces the workload of technicians in problem diagnosis and repair, thus reducing workload. Compared with existing technologies, anomaly handling time is reduced by more than 60%.

[0047] In summary, this solution provides a general-purpose driver framework for TP (Telematics Driver), 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 delivery efficiency. It has significant practical value and application prospects. Attached Figure Description

[0048] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0049] Figure 1 This is a schematic diagram illustrating how the newland-tpd driver, the driver management system of this solution, interacts with other layers of communication architecture in the POS machine.

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

[0051] Figure 3 This is a schematic diagram illustrating the logical sequence of event handling in the strategy layer (nl_tpd_core) in this solution;

[0052] Figure 4 This is a schematic diagram illustrating the logical sequence of the interface layer (nl_tpd_loader) processing in this scheme;

[0053] Figure 5 This is a schematic diagram illustrating the logical sequence of work processing in the implementation layer (tpd) of this scheme;

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

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

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

[0057] Figure 9 This is one of the schematic diagrams of the partial working logic of TP driver management in charging / RF status notification;

[0058] Figure 10 This is the second illustration of the partial working logic of TP driver management in charging / RF status notification. Detailed Implementation

[0059] The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be particularly noted that the following embodiments are for illustrative purposes only and do not limit the scope of the invention. Similarly, the following embodiments are only some, not all, embodiments of the present invention, and all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0060] Combination Figure 1 As shown, this illustrates the interaction between the newland-tpd driver, the driver management system of this solution, and other layers of communication architecture in the POS machine; simultaneously, combined with Figure 2 As shown, this embodiment is based on the POS TP driver management system newland-tpd driver, which is used for the interactive driving of the POS machine touch screen. It 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 communicatively connected to the interface layer (nl_tpd_loader) and the implementation layer (tpd) respectively, and the interface layer (nl_tpd_loader) and the implementation layer (tpd) are bidirectionally communicatively connected.

[0061] The strategy layer communicates and interacts with the Input framework of the POS machine's system user space and is used to implement the logic flow driven by the TP; the interface layer is used to parse the TP-related device tree and export the board-level configuration interface to enable the TP driver to be componentized; the implementation layer communicates and interacts directly with the TP to implement the interface for the TP's differentiated functions.

[0062] This solution proposes an innovative modular design approach, decomposing the touchscreen driver into three independent functional modules: a strategy layer, an interface layer, and an implementation layer. This layered architecture allows each module driver to be developed, tested, and upgraded independently, greatly improving the system's maintainability and scalability.

[0063] Regarding hardware abstraction technology: This solution defines a unified hardware interface through the interface layer, achieving broad compatibility with different touchscreen hardware and reducing the complexity of cross-platform porting. The hardware abstraction strategy layer can intelligently identify and adapt to various hardware platforms, providing a universal hardware interaction method.

[0064] In this scheme, the strategy layer (nl_tpd_core) is responsible for interacting with the upper-layer input framework and implementing the logic flow of TP driver, which includes one or more of the following: input event reporting, interrupt event handling, event listening and handling, and TP driver initialization process. This layer does not interact directly with the hardware, ensuring decoupling from the hardware.

[0065] In this scheme, the input events in the policy 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 the TP IC driver, configuring GPIO, and power management.

[0066] In this solution, the interface layer (nl_tpd_loader) is responsible for parsing the board-level device tree (DTS) related to TP 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, responsible for hardware abstraction and configuration, ensuring that the TP driver is compatible with different hardware platforms.

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

[0068] In this solution, the implementation layer (tpd) is responsible for directly interacting with the TP and implementing the interfaces for the TP's differentiated functions, such as touch event parsing, firmware upgrades, and sleep / wake-up. This layer maintains a certain degree of independence; apart from implementing the basic functions of the TP, which must comply with the framework specifications, other functions can be implemented according to the original TP driver's provision method, ensuring compatibility with the general framework while maintaining a certain degree of flexibility.

[0069] As a preferred implementation option, the implementation layer of this solution directly communicates and interacts with the TP's IC, reading and writing the TP's registers to implement the interface for the TP's differentiated functions; the differentiated functions include one or more of firmware upgrade, initialization, and sleep / wake-up.

[0070] As a preferred implementation option, the interface for implementing the TP differentiated functions in the implementation layer of this solution preferably includes one or more of the following: touch event parsing, firmware upgrade, and sleep / wake-up.

[0071] Based on the above, the aspects in which this solution drives the management system to differ from existing technologies include the following:

[0072] (1) Modular and layered design: Compared with the existing TP driver, the present invention adopts a modular and layered design, dividing the TP driver into a strategy layer driver, an interface layer driver and an implementation layer driver. Each driver performs its own function and does not interfere 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 strategy layer from hardware: The strategy layer of this solution does not interact directly with the hardware, but implements functions by calling the interface layer, thereby ensuring the uniformity of the interface.

[0075] (4) Maintaining independence of the implementation layer: The implementation layer of this solution maintains a certain degree of independence. Except for the basic functions of TP, which need to follow the framework specifications, 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, this solution also provides a POS-based TP driver management method, which applies the aforementioned POS-based TP driver management system, and includes:

[0077] S01. The implementation layer provides interfaces for implementing TP differentiation functions;

[0078] S02. Convert the initial driver of TP to the implementation layer and make it implement according to the corresponding interface provided by the driver framework of the implementation layer, so that TP and the implementation layer can communicate and interact directly.

[0079] S03. The strategy layer listens for events from the TP through the interface layer.

[0080] S04. TP notifies the policy layer of the user's input operation via an interrupt. The policy layer then converts the input operation into information that the implementation layer can parse. It then calls the implementation layer's input event parsing function to convert the user's input operation into coordinates. The policy layer then obtains the coordinates and reports them to the POS machine's Input subsystem.

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

[0082] Combination Figure 3 As shown, the strategy layer nl_tpd_core driver can achieve the following functionalities:

[0083] (1) Implement an input event reporting mechanism to report the input events (such as touch, gestures, etc.) of the TP 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 the corresponding logic.

[0085] (3) Implement an event listening and processing mechanism to listen for device sleep wake-up, gesture wake-up switch, RF / Charger state changes, Pin input events, etc., and perform corresponding operations according to 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 functionalities:

[0088] (1) Parse the board-level device tree (dts) related to TP 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 the TP's registers to realize various functions of the touch screen.

[0092] (2) Implement differentiated functions for TP, such as firmware upgrade, initialization, sleep wake-up, etc.

[0093] (3) Provides a firmware upgrade interface, which can update TP's firmware to fix errors or introduce new features.

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

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

[0096] Regarding touchscreen (TP) adaptation, as an example, this solution can use the framework to implement TP drivers using the following method:

[0097] a. TP driver vendors: TP driver vendors develop TP drivers that conform to the interface specifications provided by this invention.

[0098] b. POS vendors: Convert the driver provided by the TP vendor according to the implementation layer of the TP general driver framework, and provide the corresponding interface implementation according to the tpd driver framework. The policy 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. Then, the nl_tpd_core driver will convert the input event 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, to ensure the independence of the tpd driver during sleep and wake-up—that is, to decouple it from the LCD state acquisition mechanism of a specific platform—this solution does not directly associate the tpd driver implementation layer with the LCD state. Instead, this task is handled by the policy layer nl_tpd_core. The policy layer nl_tpd_core notifies the tpd driver when to enter or exit sleep mode through event calls. This design allows the tpd driver implementation layer to work without being aware of the underlying LCD state acquisition mechanism, thereby improving the driver's versatility and portability.

[0101] In this scheme, the strategy layer `nl_tpd_core` acts as an intermediate layer, responsible for listening to notifications from the touchscreen and translating them into event calls that the implementation layer `tpd` driver can understand, thereby implementing the sleep and wake-up logic. This design allows the implementation layer `tpd` driver to work seamlessly on different platforms without requiring specific modifications for each platform.

[0102] Combination Figure 7 As shown, in terms of touch event handling, the strategy layer nl_tpd_core driver of this solution is responsible for registering interrupt handling functions so that it can handle the interrupt signals reported by the touch screen TP.

[0103] In the strategic layer, the work process includes:

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

[0105] The strategy layer nl_tpd_core driver calls the touch event handling function provided by the tpd driver in the interrupt handling 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 devices 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 TP, which contains the raw data of the touch event.

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

[0111] This coordinate information is then passed to the policy layer driver nl_tpd_core for further reporting.

[0112] Combination Figure 8 As shown, for Pin input switching, this solution's driver management system includes 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 driver response:

[0116] ■TP driver listens for state changes in sysfs nodes or calls back kernel notifiers.

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

[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 pause or adjust the sleep / wake-up and ESD check process.

[0119] c. Strategies to avoid abnormal problems:

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

[0121] ■ When the touch screen pins are under the control of the safety 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. Restore and reset:

[0123] ■ When the touchscreen pins return to normal control, the payment service will update the status via 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 uses sysfs nodes and kernel notifier mechanisms to implement PIN input switching status notifications, thus avoiding abnormal issues in the TP driver during PIN input switching.

[0126] In terms of compatibility design, this solution adds the TP IC driver 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, by combining with the Linux DRM framework, the TP IC driver and panel information can be bound together. This mechanism optimizes the initialization order, speeds up the matching process, and improves system startup efficiency.

[0128] This solution uses TP driver modularization, which is asynchronously loaded during the init phase. This mechanism reduces the impact of compatibility matching on system boot time and optimizes startup speed.

[0129] At the core logic of the strategy layer, this solution defines the overall behavior and logical flow of the touchscreen driver, including key functions such as event recognition and gesture analysis. This invention implements an advanced logic processing algorithm at the strategy layer, optimizing the response speed and accuracy of touch operations.

[0130] Regarding the standardized design of the interface layer, this solution's interface layer, as a key part of hardware abstraction, 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 touchscreen hardware.

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

[0132] Regarding the implementation of differentiated functions at the implementation layer, this solution implements operations such as touch event acquisition, processing, and reporting based on the specific hardware characteristics of the touchscreen. This invention employs a differentiated design approach at the implementation layer to ensure precise control over various hardware platforms.

[0133] Based on the above, this solution also provides a POS machine that uses the POS-based TP driver management system described above.

[0134] This solution also provides a method for operating a touch POS machine, which applies the TP-driven management method based on POS described above.

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

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

[0137] Regarding charging / RF status notification, this solution uses the Linux notify mechanism to notify users of charging and RF status. It can be optimized for high-interference scenarios and improve the stability of the TP driver in scenarios such as contactless power-on / adapter insertion.

[0138] The above description is only a part of the embodiments of the present invention and does not limit the scope of protection of the present invention. Any equivalent device or equivalent process transformation made based on the content of the present invention specification and drawings, or direct or indirect application in other related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A POS-based TP drive management system for interactive drive of a POS machine touch screen, characterized in that, It comprises a policy layer, an interface layer and an implementation layer; the policy layer is in communication connection with the interface layer and the implementation layer respectively, and the interface layer is in bidirectional communication connection with the implementation layer; The policy layer communicates with an Input framework of a system user space of the POS machine, and is used for implementing a logic flow of TP driving, and the policy layer implementing the logic flow of TP driving comprises one or more of input event reporting, interrupt event processing, event listening and processing and TP driving initialization flow; The interface layer is used for parsing a device tree related to TP, and exporting a board-level configuration interface to allow TP driving to be componentized; The implementation layer directly communicates with TP to implement an interface of TP differentiation function; The policy layer listens to events of TP through the interface layer; TP notifies a user's input operation to the policy layer in a manner of interrupt, then the policy layer converts the input operation into information that can be parsed by the implementation layer, then the user's input operation is converted into coordinates by calling an input event parsing function of the implementation layer, then the policy layer acquires the coordinates and reports them to an Input subsystem of the POS machine.

2. The POS-based TP drive management system according to claim 1, wherein The input event comprises one or more of touch input and gesture input; The interrupt event comprises a touch interrupt event. The TP driving initialization flow comprises one or more of loading a TP IC driver, configuring GPIO and power management.

3. The POS-based TP drive management system of claim 1, wherein, The board-level configuration interface comprises one or more of GPIO configuration and power configuration.

4. The POS-based TP drive management system according to claim 1, wherein The implementation layer directly communicates with IC of TP to read and write registers of TP to implement the interface of TP differentiation function; The differentiation function comprises one or more of firmware upgrade, initialization and hibernation wake-up.

5. The POS-based TP drive management system according to claim 1, wherein The function of the implementation layer implementing the interface of TP differentiation function comprises one or more of touch event parsing, firmware upgrade and hibernation wake-up.

6. A POS-based TP drive management method applied to the POS-based TP drive management system according to any one of claims 1 to 5, characterized by, It comprises: The implementation layer provides the interface of TP differentiation function; The initial driver of TP is converted to the implementation layer to make the TP directly communicate with the implementation layer according to a corresponding interface provided by a driving framework of the implementation layer; The policy layer listens to events of TP through the interface layer; TP notifies a user's input operation to the policy layer in a manner of interrupt, then the policy layer converts the input operation into information that can be parsed by the implementation layer, then the user's input operation is converted into coordinates by calling an input event parsing function of the implementation layer, then the policy layer acquires the coordinates and reports them to an Input subsystem of the POS machine.

7. A POS machine, characterized by comprising: The application has the POS-based TP driving management system of any one of claims 1 to 5.

8. A touch POS machine operation method, characterized by, The application has the POS-based TP driving management method of claim 6.

Images