zephyr

History

Fabio Baltieri 57e0da4d80 boards: add zephyr,code properties to the various gpio-keys nodes Add gpio-keys codes for all boards. These are mostly INPUT_KEY_0 and so on but I've used some more specific ones where it was obvious that there's something else on the boards. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>		2023-08-07 11:26:26 +02:00
..
src	samples: input_dump: use CONFIG_INPUT_EVENT_DUMP	2023-07-12 10:53:04 +00:00
CMakeLists.txt
prj.conf	samples: input_dump: use CONFIG_INPUT_EVENT_DUMP	2023-07-12 10:53:04 +00:00
README.rst
sample.yaml	tests: samples: cleanup test tags, add integration_platforms	2023-06-02 04:47:06 -04:00

README.rst

.. _input-dump-sample:

Input Dump
##########

Overview
********

The Input Dump sample prints any input event using the :ref:`input` APIs.

Requirements
************

The samples works on any board with an input driver defined in the board devicetree.

Building and Running
********************

Build and flash as follows, changing ``nrf52dk_nrf52832`` for your board:

.. zephyr-app-commands::
   :zephyr-app: samples/subsys/input/input_dump
   :board: nrf52dk_nrf52832
   :goals: build flash
   :compact:

After starting, the sample will print any input event in the console.