Merge "Add "uinput" command to support uinput device."

clang_format = --commit ${PREUPLOAD_COMMIT} --style file --extensions c,h,cc,cpp

               cmds/hid/

               cmds/input/

               cmds/uinput/

               core/jni/

               libs/input/

               services/core/jni/

// Copyright 2020 The Android Open Source Project

//

java_binary {

    name: "uinput",

    wrapper: "uinput",

    srcs: ["**/*.java",

           ":uinputcommand_aidl"

    ],

    required: ["libuinputcommand_jni"],

}

filegroup {

    name: "uinputcommand_aidl",

    srcs: [

        "src/com/android/commands/uinput/InputAbsInfo.aidl",

    ],

}

 No newline at end of file

   Copyright (c) 2005-2008, The Android Open Source Project

   Licensed under the Apache License, Version 2.0 (the "License");

   you may not use this file except in compliance with the License.

   Unless required by applicable law or agreed to in writing, software

   distributed under the License is distributed on an "AS IS" BASIS,

   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

   See the License for the specific language governing permissions and

   limitations under the License.

                                 Apache License

                           Version 2.0, January 2004

                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,

      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by

      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all

      other entities that control, are controlled by, or are under common

      control with that entity. For the purposes of this definition,

      "control" means (i) the power, direct or indirect, to cause the

      direction or management of such entity, whether by contract or

      otherwise, or (ii) ownership of fifty percent (50%) or more of the

      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity

      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,

      including but not limited to software source code, documentation

      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical

      transformation or translation of a Source form, including but

      not limited to compiled object code, generated documentation,

      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or

      Object form, made available under the License, as indicated by a

      copyright notice that is included in or attached to the work

      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object

      form, that is based on (or derived from) the Work and for which the

      editorial revisions, annotations, elaborations, or other modifications

      represent, as a whole, an original work of authorship. For the purposes

      of this License, Derivative Works shall not include works that remain

      separable from, or merely link (or bind by name) to the interfaces of,

      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including

      the original version of the Work and any modifications or additions

      to that Work or Derivative Works thereof, that is intentionally

      submitted to Licensor for inclusion in the Work by the copyright owner

      or by an individual or Legal Entity authorized to submit on behalf of

      the copyright owner. For the purposes of this definition, "submitted"

      means any form of electronic, verbal, or written communication sent

      to the Licensor or its representatives, including but not limited to

      communication on electronic mailing lists, source code control systems,

      and issue tracking systems that are managed by, or on behalf of, the

      Licensor for the purpose of discussing and improving the Work, but

      excluding communication that is conspicuously marked or otherwise

      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity

      on behalf of whom a Contribution has been received by Licensor and

      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of

      this License, each Contributor hereby grants to You a perpetual,

      worldwide, non-exclusive, no-charge, royalty-free, irrevocable

      copyright license to reproduce, prepare Derivative Works of,

      publicly display, publicly perform, sublicense, and distribute the

      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of

      this License, each Contributor hereby grants to You a perpetual,

      worldwide, non-exclusive, no-charge, royalty-free, irrevocable

      (except as stated in this section) patent license to make, have made,

      use, offer to sell, sell, import, and otherwise transfer the Work,

      where such license applies only to those patent claims licensable

      by such Contributor that are necessarily infringed by their

      Contribution(s) alone or by combination of their Contribution(s)

      with the Work to which such Contribution(s) was submitted. If You

      institute patent litigation against any entity (including a

      cross-claim or counterclaim in a lawsuit) alleging that the Work

      or a Contribution incorporated within the Work constitutes direct

      or contributory patent infringement, then any patent licenses

      granted to You under this License for that Work shall terminate

      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the

      Work or Derivative Works thereof in any medium, with or without

      modifications, and in Source or Object form, provided that You

      meet the following conditions:

      (a) You must give any other recipients of the Work or

          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices

          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works

          that You distribute, all copyright, patent, trademark, and

          attribution notices from the Source form of the Work,

          excluding those notices that do not pertain to any part of

          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its

          distribution, then any Derivative Works that You distribute must

          include a readable copy of the attribution notices contained

          within such NOTICE file, excluding those notices that do not

          pertain to any part of the Derivative Works, in at least one

          of the following places: within a NOTICE text file distributed

          as part of the Derivative Works; within the Source form or

          documentation, if provided along with the Derivative Works; or,

          within a display generated by the Derivative Works, if and

          wherever such third-party notices normally appear. The contents

          of the NOTICE file are for informational purposes only and

          do not modify the License. You may add Your own attribution

          notices within Derivative Works that You distribute, alongside

          or as an addendum to the NOTICE text from the Work, provided

          that such additional attribution notices cannot be construed

          as modifying the License.

      You may add Your own copyright statement to Your modifications and

      may provide additional or different license terms and conditions

      for use, reproduction, or distribution of Your modifications, or

      for any such Derivative Works as a whole, provided Your use,

      reproduction, and distribution of the Work otherwise complies with

      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,

      any Contribution intentionally submitted for inclusion in the Work

      by You to the Licensor shall be under the terms and conditions of

      this License, without any additional terms or conditions.

      Notwithstanding the above, nothing herein shall supersede or modify

      the terms of any separate license agreement you may have executed

      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade

      names, trademarks, service marks, or product names of the Licensor,

      except as required for reasonable and customary use in describing the

      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or

      agreed to in writing, Licensor provides the Work (and each

      Contributor provides its Contributions) on an "AS IS" BASIS,

      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or

      implied, including, without limitation, any warranties or conditions

      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A

      PARTICULAR PURPOSE. You are solely responsible for determining the

      appropriateness of using or redistributing the Work and assume any

      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,

      whether in tort (including negligence), contract, or otherwise,

      unless required by applicable law (such as deliberate and grossly

      negligent acts) or agreed to in writing, shall any Contributor be

      liable to You for damages, including any direct, indirect, special,

      incidental, or consequential damages of any character arising as a

      result of this License or out of the use or inability to use the

      Work (including but not limited to damages for loss of goodwill,

      work stoppage, computer failure or malfunction, or any and all

      other commercial damages or losses), even if such Contributor

      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing

      the Work or Derivative Works thereof, You may choose to offer,

      and charge a fee for, acceptance of support, warranty, indemnity,

      or other liability obligations and/or rights consistent with this

      License. However, in accepting such obligations, You may act only

      on Your own behalf and on Your sole responsibility, not on behalf

      of any other Contributor, and only if You agree to indemnify,

      defend, and hold each Contributor harmless for any liability

      incurred by, or claims asserted against, such Contributor by reason

      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

# Usage

##  Two options to use the uinput command:

### 1. Interactive through stdin:

type `uinput -` into the terminal, then type/paste commands to send to the binary.

Use Ctrl+D to signal end of stream to the binary (EOF).

This mode can be also used from an app to send uinput events.

For an example, see the cts test case at: [InputTestCase.java][2]

When using another program to control uinput in interactive mode, registering a

new input device (for example, a bluetooth joystick) should be the first step.

After the device is added, you need to wait for the _onInputDeviceAdded_

(see [InputDeviceListener][1]) notification before issuing commands

to the device.

Failure to do so will cause missed events and inconsistent behavior.

### 2. Using a file as an input:

type `uinput <filename>`, and the file will be used an an input to the binary.

You must add a sufficient delay after a "register" command to ensure device

is ready. The interactive mode is the recommended method of communicating

with the uinput binary.

All of the input commands should be in pseudo-JSON format as documented below.

See examples [here][3].

The file can have multiple commands one after the other (which is not strictly

legal JSON format, as this would imply multiple root elements).

## Command description

1. `register`

Register a new uinput device

| Field         | Type          | Description                |

|:-------------:|:-------------:|:-------------------------- |

| id            | integer       | Device id                  |

| command       | string        | Must be set to "register"  |

| name          | string        | Device name                |

| vid           | 16-bit integer| Vendor id                  |

| pid           | 16-bit integer| Product id                 |

| bus           | string        | Bus that device should use |

| configuration | int array     | uinput device configuration|

| ff_effects_max| integer       | ff_effects_max value       |

| abs_info      | array         | ABS axes information       |

Device ID is used for matching the subsequent commands to a specific device

to avoid ambiguity when multiple devices are registered.

Device bus is used to determine how the uinput device is connected to the host.

The options are "usb" and "bluetooth".

Device configuration is used to configure uinput device.  "type" field provides the UI_SET_*

control code, and data is a vector of control values to be sent to uinput device, depends on

the control code.

| Field         | Type          | Description                |

|:-------------:|:-------------:|:-------------------------- |

| type          | integer       | UI_SET_ control type       |

| data          | int array     | control values             |

Device ff_effects_max must be provided if FFBIT is set.

Device abs_info fields are provided to set the device axes information. It is an array of below

objects:

| Field         | Type          | Description                |

|:-------------:|:-------------:|:-------------------------- |

| code          | integer       | Axis code                  |

| info          | object        | ABS information object     |

ABS information object is defined as below:

| Field         | Type          | Description                |

|:-------------:|:-------------:|:-------------------------- |

| value         | integer       | Latest reported value      |

| minimum       | integer       | Minimum value for the axis |

| maximum       | integer       | Maximum value for the axis |

| fuzz          | integer       | fuzz value for noise filter|

| flat          | integer       | values to be discarded     |

| resolution    | integer       | resolution of axis         |

See [struct input_absinfo][4]) definitions.

Example:

```json

{

  "id": 1,

  "command": "register",

  "name": "Keyboard (Test)",

  "vid": 0x18d2,

  "pid": 0x2c42,

  "bus": "usb",

  "configuration":[

        {"type":100, "data":[1, 21]},  // UI_SET_EVBIT : EV_KEY and EV_FF

        {"type":101, "data":[11, 2, 3, 4]},   // UI_SET_KEYBIT : KEY_0 KEY_1 KEY_2 KEY_3

        {"type":107, "data":[80]}    //  UI_SET_FFBIT : FF_RUMBLE

  ],

  "ff_effects_max" : 1,

  "abs_info": [

        {"code":1, "info": {"value":20, "minimum":-255,

                            "maximum":255, "fuzz":0, "flat":0, "resolution":1}

        },

        {"code":8, "info": {"value":-50, "minimum":-255,

                            "maximum":255, "fuzz":0, "flat":0, "resolution":1}

        }

  ]

}

```

2. `delay`

Add a delay to command processing

| Field         | Type          | Description                |

|:-------------:|:-------------:|:-------------------------- |

| id            | integer       | Device id                  |

| command       | string        | Must be set to "delay"     |

| duration      | integer       | Delay in milliseconds      |

Example:

```json

{

  "id": 1,

  "command": "delay",

  "duration": 10

}

```

3. `inject`

Send an array of uinput event packets [type, code, value] to the uinput device

| Field         | Type          | Description                |

|:-------------:|:-------------:|:-------------------------- |

| id            | integer       | Device id                  |

| command       | string        | Must be set to "inject"    |

| events        | integer array | events to inject           |

The "events" parameter is an array of integers, encapsulates evdev input_event type, code and value,

see the example below.

Example:

```json

{

  "id": 1,

  "command": "inject",

  "events": [0x01, 0xb,  0x1,   // EV_KEY, KEY_0, DOWN

             0x00, 0x00, 0x00,  // EV_SYN, SYN_REPORT, 0

             0x01, 0x0b, 0x00,  // EV_KEY, KEY_0, UP

             0x00, 0x00, 0x00,  // EV_SYN, SYN_REPORT, 0

             0x01, 0x2,  0x1,   // EV_KEY, KEY_1, DOWN

             0x00, 0x00, 0x01,  // EV_SYN, SYN_REPORT, 0

             0x01, 0x02, 0x00,  // EV_KEY, KEY_1, UP

             0x00, 0x00, 0x01   // EV_SYN, SYN_REPORT, 0

            ]

}

```

### Notes

1. As soon as EOF is reached (either in interactive mode, or in file mode),

the device that was created will be unregistered. There is no

explicit command for unregistering a device.

2. The `getevent` utility can used to print out the key events

for debugging purposes.

[1]: https://developer.android.com/reference/android/hardware/input/InputManager.InputDeviceListener.html

[2]: ../../../../cts/tests/tests/hardware/src/android/hardware/input/cts/tests/InputTestCase.java

[3]: ../../../../cts/tests/tests/hardware/res/raw/

[4]: ../../../../bionic/libc/kernel/uapi/linux/input.h