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 v2 1/2] dt-bindings: input: awinic,aw86927: Add Awinic AW8697
Date: Wed, 30 Sep 2026 19:18:50 +0200 [thread overview]
Message-ID: <20260930-mainlining-v2-1-40bb1b3943db@proton.me> (raw)
In-Reply-To: <20260930-mainlining-v2-0-40bb1b3943db@proton.me>
From: Armandas Kvietkus <armandas.kvietkus@proton.me>
The AW8697 uses the same bus, interrupt and reset lines as the AW86927.
The register map is different, so there is no fallback compatible.
Signed-off-by: Armandas Kvietkus <armandas.kvietkus@proton.me>
---
Documentation/devicetree/bindings/input/awinic,aw86927.yaml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/input/awinic,aw86927.yaml b/Documentation/devicetree/bindings/input/awinic,aw86927.yaml
index bd74b81488f6..f0e26664e3e4 100644
--- a/Documentation/devicetree/bindings/input/awinic,aw86927.yaml
+++ b/Documentation/devicetree/bindings/input/awinic,aw86927.yaml
@@ -12,7 +12,9 @@ maintainers:
properties:
compatible:
oneOf:
- - const: awinic,aw86927
+ - enum:
+ - awinic,aw8697
+ - awinic,aw86927
- items:
- enum:
- awinic,aw86938
--
2.55.0
next prev parent reply other threads:[~2026-09-30 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 17:18 [PATCH v2 0/2] Input: Add Awinic AW8697 haptics driver Armandas Kvietkus via B4 Relay
2026-09-30 17:18 ` Armandas Kvietkus via B4 Relay [this message]
2026-09-30 17:18 ` [PATCH v2 2/2] Input: aw8697 - " 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-v2-1-40bb1b3943db@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®