From: Samuel Holland <samuel@sholland.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Ondrej Jirman <x@xff.cz>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org, Samuel Holland <samuel@sholland.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Chen-Yu Tsai <wens@csie.org>,
Colin Ian King <colin.king@intel.com>,
David Gow <davidgow@google.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Marco Felsch <m.felsch@pengutronix.de>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Stephen Boyd <swboyd@chromium.org>,
Yassine Oudjana <y.oudjana@protonmail.com>,
"fengping.yu" <fengping.yu@mediatek.com>,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev
Subject: [PATCH v4 0/4] Pine64 PinePhone keyboard support
Date: Sat, 18 Jun 2022 11:57:43 -0500 [thread overview]
Message-ID: <20220618165747.55709-1-samuel@sholland.org> (raw)
This series adds support for the official keyboard case for the Pine64
PinePhone and PinePhone Pro. This accessory contains a keyboard MCU and
an IP5209 power bank IC. The keyboard MCU firmware[0] is free software.
It exposes the keyboard scan matrix over I2C, and also provides commands
for SMBus access to the IP5209. In order to keep the IP5209 driver
(CONFIG_IP5XXX_POWER) generic, this is modeled as a child I2C bus.
[0]: https://megous.com/git/pinephone-keyboard/about/
Changes in v4:
- Rebase to resolve MAINTAINERS merge conflict
- Add missing newlines in error messages
Changes in v3:
- Replace unevaluatedProperties with additionalProperties
- Rename i2c-bus to i2c
- Rename i2c-bus to i2c
Changes in v2:
- Drop keymap DT properties
- Add vbat-supply property
- Fix missing key release events when FN state changes
- Add VBAT consumer to ensure enough power is available for the MCU
- Use a single fixed-size, fixed-contents keymap for both layers
Samuel Holland (4):
dt-bindings: input: Add the PinePhone keyboard binding
Input: pinephone-keyboard - Add PinePhone keyboard driver
Input: pinephone-keyboard - Support the proxied I2C bus
[DO NOT MERGE] arm64: dts: allwinner: pinephone: Add keyboard
.../input/pine64,pinephone-keyboard.yaml | 66 +++
MAINTAINERS | 6 +
.../dts/allwinner/sun50i-a64-pinephone.dtsi | 18 +
drivers/input/keyboard/Kconfig | 10 +
drivers/input/keyboard/Makefile | 1 +
drivers/input/keyboard/pinephone-keyboard.c | 438 ++++++++++++++++++
6 files changed, 539 insertions(+)
create mode 100644 Documentation/devicetree/bindings/input/pine64,pinephone-keyboard.yaml
create mode 100644 drivers/input/keyboard/pinephone-keyboard.c
--
2.35.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-06-18 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 16:57 Samuel Holland [this message]
2022-06-18 16:57 ` [PATCH v4 1/4] dt-bindings: input: Add the PinePhone keyboard binding Samuel Holland
2022-06-18 16:57 ` [PATCH v4 2/4] Input: pinephone-keyboard - Add PinePhone keyboard driver Samuel Holland
2022-06-19 11:43 ` Andy Shevchenko
2022-06-21 4:12 ` Samuel Holland
2022-10-01 6:28 ` Dmitry Torokhov
2022-06-18 16:57 ` [PATCH v4 3/4] Input: pinephone-keyboard - Support the proxied I2C bus Samuel Holland
2022-06-19 11:34 ` Andy Shevchenko
2022-06-18 16:57 ` [PATCH v4 4/4] [DO NOT MERGE] arm64: dts: allwinner: pinephone: Add keyboard Samuel Holland
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=20220618165747.55709-1-samuel@sholland.org \
--to=samuel@sholland.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=colin.king@intel.com \
--cc=davidgow@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=fengping.yu@mediatek.com \
--cc=jernej.skrabec@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=m.felsch@pengutronix.de \
--cc=mkorpershoek@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.org \
--cc=wens@csie.org \
--cc=x@xff.cz \
--cc=y.oudjana@protonmail.com \
/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;
as well as URLs for NNTP newsgroup(s).