You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Change slightly aligns documentation pages of HID keyboard, system
control and consumer control report providers to improve consistency.
Jira: NCSDK-35470
Signed-off-by: Marek Pieta <[email protected]>
Signed-off-by: Pekka Niskanen <[email protected]>
Copy file name to clipboardExpand all lines: applications/nrf_desktop/doc/hid_provider_consumer_ctrl.rst
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ This option is enabled by default if the device uses HID provider events (:ref:`
34
34
The default implementation of the HID provider uses a predefined format of HID reports, which is aligned with the default HID report map in the common configuration (:ref:`CONFIG_DESKTOP_HID_REPORT_DESC <config_desktop_app_options>`).
35
35
36
36
Alternatively, you can substitute the module with a custom HID consumer control report provider implementation.
37
-
Using the custom provider allows you to modify sources of user input and the HID report format.
37
+
Using the custom provider allows you to modify the sources of user input and the HID report format.
38
38
Enable the :ref:`CONFIG_DESKTOP_HID_REPORT_PROVIDER_CONSUMER_CTRL_ALT <config_desktop_app_options>` Kconfig option to use a custom HID consumer control report provider.
39
39
The option disables the default HID consumer control report provider.
40
40
Make sure to introduce the custom HID consumer control report provider if you enable this option.
@@ -58,7 +58,8 @@ See the following sections for the configuration details of the used application
58
58
HID keymap
59
59
----------
60
60
61
-
The module uses the :ref:`nrf_desktop_hid_keymap` to map an application-specific key ID to a HID report ID and HID usage ID pair.
61
+
Since the keys on the board can be associated with a HID usage ID and thus be part of different HID reports, the first step is to identify if the key belongs to a HID report that is provided by this module.
62
+
This is done by obtaining the key mapping from the :ref:`nrf_desktop_hid_keymap`.
62
63
The module selects the :ref:`CONFIG_DESKTOP_HID_KEYMAP <config_desktop_app_options>` Kconfig option to enable the utility.
Copy file name to clipboardExpand all lines: applications/nrf_desktop/doc/hid_provider_keyboard.rst
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ HID provider keyboard module
7
7
:local:
8
8
:depth: 2
9
9
10
-
The HID provider keyboard module is a HID report provider integrated with :ref:`nrf_desktop_hid_state`.
10
+
The HID provider keyboard module is a HID report provider integrated with the :ref:`nrf_desktop_hid_state`.
11
11
The module is responsible for providing the HID keyboard input report and the HID boot keyboard input report.
12
12
13
13
The module listens to the user input (:c:struct:`button_event`) and communicates with the :ref:`nrf_desktop_hid_state`.
@@ -31,13 +31,14 @@ Configuration
31
31
32
32
You can enable the default implementation of the HID provider using the :ref:`CONFIG_DESKTOP_HID_REPORT_PROVIDER_KEYBOARD <config_desktop_app_options>` Kconfig option.
33
33
This option is enabled by default if the device uses HID provider events (:ref:`CONFIG_DESKTOP_HID_REPORT_PROVIDER_EVENT <config_desktop_app_options>`) and supports HID keyboard reports (:ref:`CONFIG_DESKTOP_HID_REPORT_KEYBOARD_SUPPORT <config_desktop_app_options>`).
34
+
The default implementation of the HID provider uses a predefined format of HID reports, which is aligned with the default HID report map in the common configuration (:ref:`CONFIG_DESKTOP_HID_REPORT_DESC <config_desktop_app_options>`).
34
35
The module also provides HID boot keyboard input report if it is supported (:ref:`CONFIG_DESKTOP_HID_BOOT_INTERFACE_KEYBOARD <config_desktop_app_options>`).
35
36
36
37
Alternatively, you can substitute the module with a custom HID keyboard report provider implementation.
38
+
Using the custom provider allows you to modify the sources of user input and the HID report format.
37
39
Enable the :ref:`CONFIG_DESKTOP_HID_REPORT_PROVIDER_KEYBOARD_ALT <config_desktop_app_options>` Kconfig option to use a custom HID keyboard report provider.
38
40
The option disables the default HID keyboard report provider.
39
41
Make sure to introduce the custom HID keyboard report provider if you enable this option.
40
-
See the :ref:`nrf_desktop_hid_state_providing_hid_input_reports` documentation section of the HID state module for details.
41
42
42
43
Default implementation
43
44
======================
@@ -58,7 +59,7 @@ See the following sections for the configuration details of the used application
58
59
HID keymap
59
60
----------
60
61
61
-
Since keys on the board can be associated with a HID usage ID and thus be part of different HID reports, the first step is to identify if the key belongs to a HID report that is provided by this module.
62
+
Since the keys on the board can be associated with a HID usage ID and thus be part of different HID reports, the first step is to identify if the key belongs to a HID report that is provided by this module.
62
63
This is done by obtaining the key mapping from the :ref:`nrf_desktop_hid_keymap`.
63
64
The module selects the :ref:`CONFIG_DESKTOP_HID_KEYMAP <config_desktop_app_options>` Kconfig option to enable the utility.
64
65
Make sure to configure the HID keymap utility.
@@ -111,7 +112,7 @@ The subsequent requests lead to providing subsequent keypresses as HID report ev
111
112
All key state changes still go through the HID event queue until the queue is empty.
112
113
113
114
Once the queue is empty, a key state change results in an instant update of the tracked state of pressed keys.
114
-
If the state of pressed keys changes, the module calls the ``trigger_report_send`` callback from the :c:struct:`hid_state_api` to notify the :ref:`nrf_desktop_hid_state` about the new data.
115
+
If the state of pressed keys changes, the module calls the :c:member:`hid_state_api.trigger_report_send` callback to notify the :ref:`nrf_desktop_hid_state` about the new data.
115
116
The module also remembers that the HID subscriber needs to be updated.
Copy file name to clipboardExpand all lines: applications/nrf_desktop/doc/hid_provider_system_ctrl.rst
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ This option is enabled by default if the device uses HID provider events (:ref:`
34
34
The default implementation of the HID provider uses a predefined format of HID reports, which is aligned with the default HID report map in the common configuration (:ref:`CONFIG_DESKTOP_HID_REPORT_DESC <config_desktop_app_options>`).
35
35
36
36
Alternatively, you can substitute the module with a custom HID system control report provider implementation.
37
-
Using the custom provider allows you to modify sources of user input and the HID report format.
37
+
Using the custom provider allows you to modify the sources of user input and the HID report format.
38
38
Enable the :ref:`CONFIG_DESKTOP_HID_REPORT_PROVIDER_SYSTEM_CTRL_ALT <config_desktop_app_options>` Kconfig option to use a custom HID system control report provider.
39
39
The option disables the default HID system control report provider.
40
40
Make sure to introduce the custom HID system control report provider if you enable this option.
@@ -58,7 +58,8 @@ See the following sections for the configuration details of the used application
58
58
HID keymap
59
59
----------
60
60
61
-
The module uses the :ref:`nrf_desktop_hid_keymap` to map an application-specific key ID to a HID report ID and HID usage ID pair.
61
+
Since the keys on the board can be associated with a HID usage ID and thus be part of different HID reports, the first step is to identify if the key belongs to a HID report that is provided by this module.
62
+
This is done by obtaining the key mapping from the :ref:`nrf_desktop_hid_keymap`.
62
63
The module selects the :ref:`CONFIG_DESKTOP_HID_KEYMAP <config_desktop_app_options>` Kconfig option to enable the utility.
0 commit comments