From: David Lechner <david@lechnology.com>
To: linux-input@vger.kernel.org, devicetree@vger.kernel.org
Cc: David Lechner <david@lechnology.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] Input: add optional amplifier regulator to pwm-beeper (previously "Input: add optional enable gpio to pwm-beeper")
Date: Wed, 11 Jan 2017 14:01:58 -0600 [thread overview]
Message-ID: <1484164921-30587-1-git-send-email-david@lechnology.com> (raw)
This series adds an optional regulator to the pwm-beeper driver and device tree
bindings. The regulator acts as an amplifier that powers the beeper.
v2 changes:
* Changed from using a gpio to a regulator
* Rebased on the pwm-beeper cleanup series "Input: pwm-beeper - remove calls to
legacy pwm_request API"
David Lechner (3):
Input: pwm-beeper: suppress error message on probe defer
dt-bindings: Input: Add optional amp-supply property to pwm-beeper
Input: pwm-beeper: add optional amplifier regulator
.../devicetree/bindings/input/pwm-beeper.txt | 16 ++++++++++
drivers/input/misc/pwm-beeper.c | 36 +++++++++++++++++++---
2 files changed, 48 insertions(+), 4 deletions(-)
--
2.7.4
next reply other threads:[~2017-01-11 20:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 20:01 David Lechner [this message]
2017-01-11 20:01 ` [PATCH v2 1/3] Input: pwm-beeper: suppress error message on probe defer David Lechner
2017-01-14 19:17 ` Dmitry Torokhov
2017-01-11 20:02 ` [PATCH v2 2/3] dt-bindings: Input: Add optional amp-supply property to pwm-beeper David Lechner
2017-01-18 19:58 ` Rob Herring
2017-01-11 20:02 ` [PATCH v2 3/3] Input: pwm-beeper: add optional amplifier regulator David Lechner
2017-01-14 19:19 ` Dmitry Torokhov
2017-01-16 0:12 ` David Lechner
2017-01-16 0:34 ` Dmitry Torokhov
2017-01-16 1:04 ` David Lechner
2017-01-19 22:34 ` Dmitry Torokhov
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=1484164921-30587-1-git-send-email-david@lechnology.com \
--to=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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