public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dzmitry Sankouski <dsankouski@gmail.com>
To: u-boot@lists.denx.de
Cc: Dzmitry Sankouski <dsankouski@gmail.com>
Subject: [PATCH v3 0/5] dm: input: driver for buttons with linux, code declaration
Date: Sun, 22 Jan 2023 18:21:20 +0300	[thread overview]
Message-ID: <20230122152125.858085-1-dsankouski@gmail.com> (raw)

Bootmenu requires an input device with arrows and enter key.
A common smartphone luckily has power, volume up/down buttons,
which may be used for controlling bootmenu.

Button keyboard driver relies on button driver - iterates over
all button with linux,code, checks state and sends events.
Add support for linux,code in button driver.
Fix qcom pwr-key gpio driver to work with button driver.

Dzmitry Sankouski (5):
  gpio: qcom: add direction functions for pwrkey
  dts: add missing linux,code in gpio-keys
  test: create dedicated fdt node for ofnode_for_each_prop test
  dm: button: add support for linux_code in button-gpio.c driver
  dm: input: add button_kbd driver

 arch/arm/dts/am3517-evm-ui.dtsi               |   2 +-
 .../dts/imx6ul-phytec-segin-peb-eval-01.dtsi  |   2 +-
 arch/arm/dts/rk3288-popmetal.dtsi             |   2 +
 arch/arm/dts/rk3288-tinker.dtsi               |   2 +
 arch/sandbox/dts/sandbox.dtsi                 |   4 +
 arch/sandbox/dts/test.dts                     |  16 +++
 drivers/button/button-gpio.c                  |  17 ++-
 drivers/button/button-uclass.c                |  10 ++
 drivers/gpio/qcom_pmic_gpio.c                 |  16 +++
 drivers/input/Kconfig                         |   9 ++
 drivers/input/Makefile                        |   1 +
 drivers/input/button_kbd.c                    | 126 ++++++++++++++++++
 include/button.h                              |  16 +++
 test/dm/button.c                              |  13 ++
 test/dm/ofnode.c                              |   2 +-
 15 files changed, 234 insertions(+), 4 deletions(-)
 create mode 100644 drivers/input/button_kbd.c

-- 
2.30.2


             reply	other threads:[~2023-01-22 15:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 15:21 Dzmitry Sankouski [this message]
2023-01-22 15:21 ` [PATCH v3 1/5] gpio: qcom: add direction functions for pwrkey Dzmitry Sankouski
2023-02-10 18:43   ` Tom Rini
2023-01-22 15:21 ` [PATCH v3 2/5] dts: add missing linux,code in gpio-keys Dzmitry Sankouski
2023-02-10 18:43   ` Tom Rini
2023-01-22 15:21 ` [PATCH v3 3/5] test: create dedicated fdt node for ofnode_for_each_prop test Dzmitry Sankouski
2023-01-23 18:42   ` Simon Glass
2023-02-10 18:43   ` Tom Rini
2023-01-22 15:21 ` [PATCH v3 4/5] dm: button: add support for linux_code in button-gpio.c driver Dzmitry Sankouski
2023-01-23 18:42   ` Simon Glass
2023-02-10 18:43   ` Tom Rini
2023-01-22 15:21 ` [PATCH v3 5/5] dm: input: add button_kbd driver Dzmitry Sankouski
2023-01-23 18:42   ` Simon Glass
2023-02-10 18:43   ` Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230122152125.858085-1-dsankouski@gmail.com \
    --to=dsankouski@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox