From: Caleb Connolly <caleb@connolly.tech>
To: Caleb Connolly <caleb@connolly.tech>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-input@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Jami Kettunen <jami.kettunen@somainline.org>,
Joel Selvaraj <jo@jsfamily.in>
Subject: [PATCH v3 0/6] input: Introduce support for SPMI haptics found on Qcom PMICs
Date: Mon, 16 Aug 2021 22:19:44 +0000 [thread overview]
Message-ID: <20210816221931.1998187-1-caleb@connolly.tech> (raw)
This series introduces a driver for the SPMI haptics hardware block
found in Qualcomm PMICs. SPMI haptics support LRA (Linear Resonant
Actuator) style haptics, as well as ERM (Eccentric Rotating Mass).
It also supports several modes of driving the haptics, e.g. by loading
the pattern to play into an internal buffer, or using PWM.
More information about the hardware can be found here:
https://gitlab.com/sdm845-mainline/linux/-/wikis/PMI8998-QPNP-Haptics
This driver has been written based on downstream sources as no public
documentation is available. It includes initial support for LRA haptics
in buffer mode, this combination seems to be the most common and will
enable haptics on the OnePlus 6 and 6T, PocoPhone F1, OnePlus 5 and
several other Qualcomm devices with mainline kernel support.
The driver is implemented using the ff-memless (forcefeedback) input
framework and makes an attempt to control the strength of vibration relative
to the magnitude set from userspace.
~ Caleb
Changes since v2:
- Addressed Rob's comments on dt-bindings (I'm not sure what to do
about the pmic compatible?)
- Fixed some typos
Changes since v1:
- Replace old QPNP naming with SPMI
- Address Bjorn's comments on the driver, various style and code cleanups
- Address Bjorn's comments on the DT bindings and DTS
- Pickup patches from Joel and Jami to enable haptics on the OnePlus 5
and Poco F1.
---
Caleb Connolly (4):
dt-bindings: input: add Qualcomm SPMI haptics driver
input: add Qualcomm SPMI haptics driver
arm64: dts: qcom: pmi8998: introduce spmi haptics
arm64: dts: qcom: sdm845-oneplus-common: add haptics
Jami Kettunen (1):
arm64: dts: qcom: msm8998-oneplus-common: Enable PMI8998 haptics
Joel Selvaraj (1):
arm64: dts: qcom: sdm845-xiaomi-beryllium: add haptics
.../bindings/input/qcom,spmi-haptics.yaml | 128 +++
.../boot/dts/qcom/msm8998-oneplus-common.dtsi | 6 +
arch/arm64/boot/dts/qcom/pmi8998.dtsi | 16 +
.../boot/dts/qcom/sdm845-oneplus-common.dtsi | 6 +
.../boot/dts/qcom/sdm845-xiaomi-beryllium.dts | 5 +
drivers/input/misc/Kconfig | 12 +
drivers/input/misc/Makefile | 1 +
drivers/input/misc/qcom-spmi-haptics.c | 981 ++++++++++++++++++
include/dt-bindings/input/qcom,spmi-haptics.h | 32 +
9 files changed, 1187 insertions(+)
create mode 100644 Documentation/devicetree/bindings/input/qcom,spmi-haptics.yaml
create mode 100644 drivers/input/misc/qcom-spmi-haptics.c
create mode 100644 include/dt-bindings/input/qcom,spmi-haptics.h
--
2.32.0
next reply other threads:[~2021-08-16 22:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 22:19 Caleb Connolly [this message]
2021-08-16 22:19 ` [PATCH v3 1/6] dt-bindings: input: add Qualcomm SPMI haptics driver Caleb Connolly
2021-08-17 12:10 ` Rob Herring
2021-08-16 22:20 ` [PATCH v3 2/6] " Caleb Connolly
2021-08-17 2:12 ` kernel test robot
2021-08-17 2:12 ` kernel test robot
2021-08-16 22:20 ` [PATCH v3 3/6] arm64: dts: qcom: pmi8998: introduce spmi haptics Caleb Connolly
2021-08-16 22:20 ` [PATCH v3 4/6] arm64: dts: qcom: sdm845-oneplus-common: add haptics Caleb Connolly
2021-08-16 22:20 ` [PATCH v3 5/6] arm64: dts: qcom: sdm845-xiaomi-beryllium: " Caleb Connolly
2021-08-16 22:20 ` [PATCH v3 6/6] arm64: dts: qcom: msm8998-oneplus-common: Enable PMI8998 haptics Caleb Connolly
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=20210816221931.1998187-1-caleb@connolly.tech \
--to=caleb@connolly.tech \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jami.kettunen@somainline.org \
--cc=jo@jsfamily.in \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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.