From: Krzysztof Kozlowski <krzk@kernel.org>
To: Qianhui Xu <xiaqinghuan@mail.ustc.edu.cn>,
linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] dt-bindings: input: awinic,aw86927: document the AW86937 variant
Date: Tue, 27 Oct 2026 19:06:02 +0100 [thread overview]
Message-ID: <f76d56db-6ea8-45ef-a70e-e53cc70cf508@kernel.org> (raw)
In-Reply-To: <20261027132929.242158-3-xiaqinghuan@mail.ustc.edu.cn>
On 27/10/2026 14:29, Qianhui Xu wrote:
> The AW86937 is a sibling of the AW86938 with the same register layout and
> a distinct CHIPID. It is described the same way as the AW86938, with the
> AW86927 compatible as fallback; software tells the parts apart by reading
> the CHIPID registers.
>
> Signed-off-by: Qianhui Xu <xiaqinghuan@mail.ustc.edu.cn>
> ---
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-27 18:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 13:29 [PATCH 0/5] Input: aw86927 - add AW86937 support and fix the AW8693X layout Qianhui Xu
2026-10-27 13:29 ` [PATCH 1/5] Input: aw86927 - fix the 7 V boost reference for AW86938 Qianhui Xu
2026-10-27 13:29 ` [PATCH 2/5] dt-bindings: input: awinic,aw86927: document the AW86937 variant Qianhui Xu
2026-10-27 18:06 ` Krzysztof Kozlowski [this message]
2026-10-27 13:29 ` [PATCH 3/5] Input: aw86927 - add support for Awinic AW86937 Qianhui Xu
2026-10-27 13:29 ` [PATCH 4/5] Input: aw86927 - handle the AW8693X play and boost register layout Qianhui Xu
2026-10-27 13:37 ` sashiko-bot
2026-10-27 13:29 ` [PATCH 5/5] Input: aw86927 - stop playback over suspend and on shutdown Qianhui Xu
2026-10-27 13:55 ` sashiko-bot
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=f76d56db-6ea8-45ef-a70e-e53cc70cf508@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=xiaqinghuan@mail.ustc.edu.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.