From: Ladislav Michl <ladis@linux-mips.org>
To: linux-input@vger.kernel.org
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: [RFC 0/2] Input: gpio-beeper: drive output by hrtimer
Date: Wed, 29 Nov 2017 12:06:27 +0100 [thread overview]
Message-ID: <20171129110627.GA24064@lenoch> (raw)
I have board here, where beeper cannot by driven by PWM as its pin
cannot be muxed there. This is an unfortunate result of evolution
and fixing thousands boards in hardware would be too expensive.
So here we are. I'm not pushing for inclusion to mainline, but
parhaps this could be usefull for others. You decide.
In case you'll find it usefull, I'm ready to solve any objections
and comments.
Ladislav Michl (2):
Input: gpio-beeper: use helper variable to access device info
Input: gpio-beeper: drive beeper pin by hrtimer
Documentation/devicetree/bindings/input/gpio-beeper.txt | 5
drivers/input/misc/gpio-beeper.c | 99 +++++++++++++---
2 files changed, 91 insertions(+), 13 deletions(-)
next reply other threads:[~2017-11-29 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 11:06 Ladislav Michl [this message]
2017-11-29 11:07 ` [PATCH 1/2] Input: gpio-beeper: use helper variable to access device info Ladislav Michl
2017-11-29 11:08 ` [PATCH 2/2] Input: gpio-beeper: drive beeper pin by hrtimer Ladislav Michl
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=20171129110627.GA24064@lenoch \
--to=ladis@linux-mips.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.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).