From: Armandas Kvietkus via B4 Relay <devnull+armandas.kvietkus.proton.me@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Griffin Kroah-Hartman <griffin.kroah@fairphone.com>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Armandas Kvietkus <armandas.kvietkus@proton.me>
Subject: [PATCH 0/2] Input: Add Awinic AW8697 haptics driver
Date: Wed, 30 Sep 2026 18:08:02 +0200 [thread overview]
Message-ID: <20260930-mainlining-v1-0-c303cbdb00c8@proton.me> (raw)
This series adds a driver for the Awinic AW8697 LRA haptic driver IC.
It is the vibrator in the Xiaomi POCO F3.
The AW8697 is an older generation than the AW86927. The register map
is different, so it gets its own driver. The binding reuses
awinic,aw86927.yaml.
Tested on the phone: rumble at several strengths, 72 effects in a row,
stop on close, driver rebind and module reload.
Signed-off-by: Armandas Kvietkus <armandas.kvietkus@proton.me>
---
Armandas Kvietkus (2):
dt-bindings: input: awinic,aw86927: Add Awinic AW8697
Input: aw8697 - Add Awinic AW8697 haptics driver
.../devicetree/bindings/input/awinic,aw86927.yaml | 4 +-
MAINTAINERS | 6 +
drivers/input/misc/Kconfig | 14 +
drivers/input/misc/Makefile | 1 +
drivers/input/misc/aw8697.c | 725 +++++++++++++++++++++
5 files changed, 749 insertions(+), 1 deletion(-)
---
base-commit: 165768bb70265b5c38cf0b73fafd75be235f8b14
change-id: 20260930-mainlining-0bd8b7b5ca6c
Best regards,
--
Armandas Kvietkus <armandas.kvietkus@proton.me>
next reply other threads:[~2026-09-30 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 16:08 Armandas Kvietkus via B4 Relay [this message]
2026-09-30 16:08 ` [PATCH 1/2] dt-bindings: input: awinic,aw86927: Add Awinic AW8697 Armandas Kvietkus via B4 Relay
2026-09-30 16:08 ` [PATCH 2/2] Input: aw8697 - Add Awinic AW8697 haptics driver Armandas Kvietkus via B4 Relay
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=20260930-mainlining-v1-0-c303cbdb00c8@proton.me \
--to=devnull+armandas.kvietkus.proton.me@kernel.org \
--cc=armandas.kvietkus@proton.me \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=griffin.kroah@fairphone.com \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®