From: Brian Masney <masneyb@onstation.org>
To: dmitry.torokhov@gmail.com
Cc: linux-input@vger.kernel.org, sboyd@kernel.org,
robh+dt@kernel.org, mark.rutland@arm.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: [PATCH v2 0/2] Input: remove msm-vibrator driver and bindings
Date: Tue, 11 Feb 2020 07:13:16 -0500 [thread overview]
Message-ID: <20200211121318.144067-1-masneyb@onstation.org> (raw)
Here's a small patch series that removes the msm-vibrator driver and
bindings. These two patches are broken out from this patch series:
https://lore.kernel.org/lkml/20191205002503.13088-5-masneyb@onstation.org/
In a nutshell, I'm waiting for someone from Qualcomm to either post a
patch to support setting the clock duty cycle or someone to post
information about the m,n,d registers for the clocks. Once that's done,
no other changes should be needed in the input subsystem.
In the mean time, the msm-vibrator driver needs to be removed from
upstream.
Changes since v1:
- Updated commit messages to remove references to clk-vibrator.
Brian Masney (2):
dt-bindings: Input: remove msm-vibrator
Input: remove msm-vibrator driver
.../bindings/input/msm-vibrator.txt | 36 ---
drivers/input/misc/Kconfig | 10 -
drivers/input/misc/Makefile | 1 -
drivers/input/misc/msm-vibrator.c | 281 ------------------
4 files changed, 328 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/input/msm-vibrator.txt
delete mode 100644 drivers/input/misc/msm-vibrator.c
--
2.24.1
next reply other threads:[~2020-02-11 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 12:13 Brian Masney [this message]
2020-02-11 12:13 ` [PATCH v2 1/2] dt-bindings: Input: remove msm-vibrator Brian Masney
2020-02-11 12:13 ` [PATCH v2 2/2] Input: remove msm-vibrator driver Brian Masney
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=20200211121318.144067-1-masneyb@onstation.org \
--to=masneyb@onstation.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
/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).