From: James Ogletree <james.ogletree@cirrus.com>
To: <dmitry.torokhov@gmail.com>
Cc: James Ogletree <james.ogletree@cirrus.com>,
Fred Treven <fred.treven@cirrus.com>,
Ben Bright <ben.bright@cirrus.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, "Lee Jones" <lee@kernel.org>,
Markus Schneider-Pargmann <msp@baylibre.com>,
"ChiYuan Huang" <cy_huang@richtek.com>,
Joel Stanley <joel@jms.id.au>,
Randy Dunlap <rdunlap@infradead.org>,
Arnd Bergmann <arnd@arndb.de>, Jacky Bai <ping.bai@nxp.com>,
Jean Delvare <jdelvare@suse.de>,
Eddie James <eajames@linux.ibm.com>,
Jeff LaBundy <jeff@labundy.com>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
<patches@cirrus.com>, <linux-input@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v3 0/2] Add support for CS40L50
Date: Wed, 9 Aug 2023 19:10:26 +0000 [thread overview]
Message-ID: <20230809191032.820271-1-james.ogletree@cirrus.com> (raw)
Changes in v2:
- Fix checkpatch warnings
Changes in v3:
- YAML formatting corrections
- Fix typo in MAINTAINERS
- Use generic node name "haptic-driver"
- Fix regulator error code path
- Use sizeof(*)
- Remove tree reference in MAINTAINERS
James Ogletree (2):
dt-bindings: input: cirrus,cs40l50: Support for CS40L50
Input: cs40l50 - Initial support for Cirrus Logic CS40L50
.../bindings/input/cirrus,cs40l50.yaml | 77 ++
MAINTAINERS | 10 +
drivers/input/misc/Kconfig | 33 +
drivers/input/misc/Makefile | 3 +
drivers/input/misc/cs40l50-i2c.c | 67 ++
drivers/input/misc/cs40l50-spi.c | 67 ++
drivers/input/misc/cs40l50.c | 1008 +++++++++++++++++
include/linux/input/cs40l50.h | 321 ++++++
8 files changed, 1586 insertions(+)
create mode 100644 Documentation/devicetree/bindings/input/cirrus,cs40l50.yaml
create mode 100644 drivers/input/misc/cs40l50-i2c.c
create mode 100644 drivers/input/misc/cs40l50-spi.c
create mode 100644 drivers/input/misc/cs40l50.c
create mode 100644 include/linux/input/cs40l50.h
--
2.25.1
next reply other threads:[~2023-08-09 19:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 19:10 James Ogletree [this message]
2023-08-09 19:10 ` [PATCH v3 1/2] dt-bindings: input: cirrus,cs40l50: Support " James Ogletree
2023-08-10 6:19 ` Krzysztof Kozlowski
2023-08-09 19:10 ` [PATCH v3 2/2] Input: cs40l50 - Initial support for Cirrus Logic CS40L50 James Ogletree
2023-08-10 6:17 ` Krzysztof Kozlowski
2023-08-15 15:56 ` James Ogletree
2023-08-15 19:23 ` Krzysztof Kozlowski
2023-08-10 10:30 ` Charles Keepax
2023-08-15 22:33 ` James Ogletree
2023-08-16 8:11 ` Charles Keepax
2023-08-11 4:07 ` Jeff LaBundy
2023-08-16 21:02 ` James Ogletree
2023-08-22 12:43 ` Jeff LaBundy
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=20230809191032.820271-1-james.ogletree@cirrus.com \
--to=james.ogletree@cirrus.com \
--cc=arnd@arndb.de \
--cc=bartosz.golaszewski@linaro.org \
--cc=ben.bright@cirrus.com \
--cc=conor+dt@kernel.org \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=eajames@linux.ibm.com \
--cc=fred.treven@cirrus.com \
--cc=jdelvare@suse.de \
--cc=jeff@labundy.com \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=patches@cirrus.com \
--cc=ping.bai@nxp.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=wsa+renesas@sang-engineering.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
all inboxes | Powered by JetHome®