Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Brian Masney <masneyb@onstation.org>
To:     dmitry.torokhov@gmail.com
Cc:     robh+dt@kernel.org, linux-input@vger.kernel.org,
        linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
        linux-arm-msm@vger.kernel.org, sboyd@kernel.org
Subject: [PATCH v2 RESEND 0/2] Input: remove msm-vibrator driver and bindings
Date:   Tue, 12 May 2020 21:31:38 -0400
Message-Id: <20200513013140.69935-1-masneyb@onstation.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Here's a small patch series that removes the msm-vibrator driver and
bindings. These two patches are broken out from this patch series from
December:

https://lore.kernel.org/lkml/20191205002503.13088-5-masneyb@onstation.org/

And a resend of what I sent out in February:

https://lore.kernel.org/lkml/20200211121318.144067-1-masneyb@onstation.org/

In a nutshell, the address referenced by this driver is within the
Qualcomm Clock namespace and needs to be managed by the clk subsystem.
This driver needs to go away to clean up the upstream kernel.

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
will be needed in the input subsystem.

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