From: Ming-Jen <mjchen0829@gmail.com>
To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-input@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, mjchen0829@gmail.com,
sudeep.holla@arm.com, arnd@arndb.de, peng.fan@nxp.com,
conor+dt@kernel.org, krzk+dt@kernel.org, robh@kernel.org,
dmitry.torokhov@gmail.com
Subject: [PATCH v6 0/2] Add support for nuvoton ma35d1 keypad controller
Date: Thu, 9 Jan 2025 00:26:20 +0000 [thread overview]
Message-ID: <20250109002622.771-1-mjchen0829@gmail.com> (raw)
From: Ming-jen Chen <mjchen0829@gmail.com>
v6:
- Update nuvoton,ma35d1-keypad.yaml
- Modify 'compatible' to make filename matching compatible.
- Update ma35d1_keypad.c
- Modify 'compatible' to match the name in the .yaml file.
v5:
- Update nuvoton,ma35d1-keypad.yaml
- Reorders the items in the properties and required blocks to ensure
their order and items are consistent.
v4:
- Update nuvoton,ma35d1-keypad.yaml
- Kept the same order of properties as in the required block.
- Changed register addresses to lowercase.
v3:
- Update nuvoton,ma35d1-keypad.yaml
- Removed vendor-specific properties and replaced them with common properties
- Update ma35d1_keypad.c
- Modified the driver to reflect changes in the YAML properties
v2:
- Update nuvoton,ma35d1-keypad.yaml
- Fixed warnings and errors generated by running checkpatch.pl
- Removed the previous version's properties and rewrote the
properties in the Device Tree schema.
- Renamed the Device Tree binding file to nuvoton,ma35d1-keypad.yaml
- Update Kconfig
- Added COMPILE_TEST to the depends on line in the Kconfig
- Update ma35d1_keypad.c
- Refactored error handling within the probe function.
- Fixed the mixed use of devm and non-devm resource management.
- Corrected alignment issues in the code.
- Updated suspend and resume handling methods.
- Fixed variable naming to remove camel casing.
- Used for_each_set_bit() to check key states.
- Modified the code to align with updates in the device tree binding
Ming-jen Chen (2):
dt-bindings: input: Add Nuvoton MA35D1 keypad
input: keypad: add new keypad driver for MA35D1
.../bindings/input/nuvoton,ma35d1-keypad.yaml | 82 ++++
drivers/input/keyboard/Kconfig | 10 +
drivers/input/keyboard/Makefile | 1 +
drivers/input/keyboard/ma35d1_keypad.c | 387 ++++++++++++++++++
4 files changed, 480 insertions(+)
create mode 100644 Documentation/devicetree/bindings/input/nuvoton,ma35d1-keypad.yaml
create mode 100644 drivers/input/keyboard/ma35d1_keypad.c
--
2.25.1
next reply other threads:[~2025-01-09 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 0:26 Ming-Jen [this message]
2025-01-09 0:26 ` [PATCH v6 1/2] dt-bindings: input: Add Nuvoton MA35D1 keypad Ming-Jen
2025-01-09 8:52 ` Krzysztof Kozlowski
2025-01-09 0:26 ` [PATCH v6 2/2] input: keypad: add new keypad driver for MA35D1 Ming-Jen
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=20250109002622.771-1-mjchen0829@gmail.com \
--to=mjchen0829@gmail.com \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.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).