Home
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running the QNX OS 8.0.
Graphics
Input Events Library Reference
The Input Events library provides the framework necessary for Screen Graphics Subsystem to communicate with your touch driver.
Input Events Library Overview
mtouch_driver.h
Functions that are to be implemented by the mtouch driver and are called by libinputevents to fetch the data required to transform the device data into mtouch events.
Driver test result types
The types of test results

QNX Momentics IDE User's Guide
This User's Guide describes version 8.0 of the Integrated Development Environment (IDE) that's part of the QNX Tool Suite.
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running the QNX OS 8.0.
- Quickstart Guide
- System Architecture
  The System Architecture guide accompanies the QNX OS and is intended for both application developers and end-users.
- OS Components & Operations
- Graphics
  - Gestures Library Reference
    The Gestures library provides gesture recognizers to detect gestures through touch events that occur when you place one or more fingers on a touch screen.
  - Image Library Reference
  - Input Events Library Reference
    The Input Events library provides the framework necessary for Screen Graphics Subsystem to communicate with your touch driver.
    - Writing a Touch Driver
      In order for Screen to be able to detect events from your touch controller, you need to provide a driver for your touch controller.
    - Input Events Library Overview
      - event_types.h
        Enumerations and structures for input events.
      - mtouch_driver.h
        Functions that are to be implemented by the mtouch driver and are called by libinputevents to fetch the data required to transform the device data into mtouch events.
        Definitions in mtouch_driver.h
        Preprocessor macro definitions for the mtouch_driver.h header file in the libinputevents library
        Driver test result types
        The types of test results
        mtouch_driver_attach()
        Attach driver to the Input Events framework
        mtouch_driver_detach()
        Detach driver from the Input Events framework
        mtouch_driver_funcs_t
        Functions to be implemented by the mtouch driver
        mtouch_driver_process_packet()
        Process the data packet from the specified driver
        mtouch_test_bist()
        Test the built-in-self-test (BIST)
        mtouch_test_fini()
        Clean up test driver interface
        mtouch_test_init()
        Initialize test driver interface
        mtouch_test_read_firmware_version()
        Test the ability to read the firmware version of the driver
        mtouch_test_read_product_id()
        Test the ability to read the product ID of the driver
        mtouch_test_read_serial_id()
        Test the ability to read the serial ID of the driver
        mtouch_test_read_supplier_id()
        Test the ability to read the supplier ID
      - mtouch_log.h
        Function and Macros that print mtouch log information.
      - mtouch_params.h
        Enumerations and Structures for mtouch parameters.
      - parseopts.h
        Helper functions to parse the options from the mtouch section of graphics.conf.
      - screen_helpers.h
        Helper functions for Screen input events.
  - OpenWF Configuration Developer's Guide
    If you are integrating a new display, you must configure and provide the parameters of your display based on its specifications via the OpenWF Display Configuration API (Wfdcfg Library).
  - OpenWF Display Server User's Guide
    The OpenWF Display Server (wfd-server) is a resource manager that provides applications the ability to show image buffers directly to the display controller via the OpenWF Display API.
  - Screen Graphics Subsystem Developer's Guide
    QNX Screen Graphics Subsystem is a graphics framework that provides all the functionality necessary to develop interactive user experiences.
  - Video Capture Developer's Guide
    The video capture framework provides applications the ability to capture frames from a video input source. These frames can be passed to a graphics component such as Screen for display.
- Programming
- System Security Guide
  The QNX System Security Guide is intended for both system integrators who are responsible for the security of a QNX OS system and developers who want to create a QNX OS resource manager free from vulnerabilities.
- Utilities & Libraries
- Migrating to QNX OS 8.0
QNX Software in the Cloud
QNX Software in the Cloud enables developers to use the QNX OS in the Amazon cloud environment.
QNX Toolkit for Visual Studio Code
This User's Guide describes the QNX^® Toolkit for Visual Studio Code. The guide introduces you to the QNX Toolkit by explaining the QNX development environment and how to build, run, and debug your QNX^® Operating System (OS) applications and systems.
QNX Hypervisor User's Guide
This User's Guide explains the QNX hypervisor architecture and provides instructions for installing and running a QNX Hypervisor system, changing system components and configuration, and using hypervisor features such as virtual devices (vdevs).
Typographical Conventions, Support, and Licensing
This section describes the typographical conventions used throughout the documentation, explains how to obtain technical support, and provides some information about licensing.

Driver test result types

QNX SDP8.0Input Events Library ReferenceAPIDeveloperProgramming

The types of test results

Synopsis:

#include <input/mtouch_driver.h>

enum {
    MTOUCH_TEST_RESULT_COMPLETED,
    MTOUCH_TEST_RESULT_NOT_SUPPORTED,
    MTOUCH_TEST_RESULT_NOT_NOW,
    MTOUCH_TEST_RESULT_I2C_FAILURE,
    MTOUCH_TEST_RESULT_TIMEOUT
};

Data:

MTOUCH_TEST_RESULT_COMPLETED

Test has completed.

MTOUCH_TEST_RESULT_NOT_SUPPORTED

Test is not supported.

MTOUCH_TEST_RESULT_NOT_NOW

Test cannot be run at this time.

Possible reasons include:

firmware is being updated
single scan
BIST is occurring

MTOUCH_TEST_RESULT_I2C_FAILURE

I2C communication with controller failed.

MTOUCH_TEST_RESULT_TIMEOUT

The controller did not respond in time.

Library:

libinputevents

Description:

This enumeration lists possible test results from using the test interface for an mtouch driver.

Page updated: March 05, 2025