From: Yassine Oudjana <y.oudjana@protonmail.com>
To: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>
Cc: Yassine Oudjana <y.oudjana@protonmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"phone-devel@vger.kernel.org" <phone-devel@vger.kernel.org>,
"~postmarketos/upstreaming@lists.sr.ht"
<~postmarketos/upstreaming@lists.sr.ht>
Subject: [PATCH v2 0/2] Input: cypress-sf - Add support for Cypress Streetfighter touchkeys
Date: Tue, 04 May 2021 19:20:04 +0000 [thread overview]
Message-ID: <235fu6MnvzCoMBgP3Wkhz2ZmKOIG2ZYDBzYNBEJlbk@cp4-web-036.plabs.ch> (raw)
This patchset adds support for the Cypress StreetFighter touchkey device.
This driver is based on the driver from the vendor kernel for the Xiaomi
Mi Note 2[1][2], which is also the device where this was tested.
[1] https://github.com/MiCode/Xiaomi_Kernel_OpenSource/blob/scorpio-m-oss/drivers/input/touchscreen/cyttsp_button.c
[2] https://github.com/MiCode/Xiaomi_Kernel_OpenSource/blob/scorpio-m-oss/arch/arm/boot/dts/qcom/scorpio-msm8996-mtp.dtsi#L300-L322
Changes in v2:
- Changed version variables in probe to int to allow storing error codes.
- Fixed some issues in dt binding.
Yassine Oudjana (2):
Input: cypress-sf - Add Cypress StreetFighter touchkey driver
dt-bindings: input: Add binding for cypress-sf
.../devicetree/bindings/input/cypress-sf.yaml | 61 +++++
drivers/input/keyboard/Kconfig | 10 +
drivers/input/keyboard/Makefile | 1 +
drivers/input/keyboard/cypress-sf.c | 219 ++++++++++++++++++
4 files changed, 291 insertions(+)
create mode 100644 Documentation/devicetree/bindings/input/cypress-sf.yaml
create mode 100644 drivers/input/keyboard/cypress-sf.c
--
2.31.1
reply other threads:[~2021-05-04 19:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=235fu6MnvzCoMBgP3Wkhz2ZmKOIG2ZYDBzYNBEJlbk@cp4-web-036.plabs.ch \
--to=y.oudjana@protonmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@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 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).