From: Samuel Holland <samuel@sholland.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@siol.net>,
devicetree@vger.kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev,
Samuel Holland <samuel@sholland.org>
Subject: [PATCH v3 0/2] sunxi LRADC/volume key wakeup support
Date: Thu, 29 Apr 2021 23:20:01 -0500 [thread overview]
Message-ID: <20210430042003.4591-1-samuel@sholland.org> (raw)
This series allows the volume keys on the PinePhone (and other devices
with LRADC buttons) to wake up the device.
Currently `make dtbs_check` complains because the DT update was merged
without the binding.
Changes since v2:
- Dropped unnecessary pr_err in platform_get_irq() error path
- Dropped patch 3 (DT update) as it was merged
- Added Acked-by/Reviewed-by tags
Changes since v1:
- Add requisite DT binding change
- Only add wakeup capability if "wakeup-source" is present
- Warn but do not error out if setting the wake IRQ fails
- Add "wakeup-source" property to PinePhone device tree
Ondrej Jirman (1):
input: sun4i-lradc-keys - Add wakup support
Samuel Holland (1):
dt-bindings: sun4i-a10-lradc-keys: Accept wakeup-source property
.../input/allwinner,sun4i-a10-lradc-keys.yaml | 2 ++
drivers/input/keyboard/sun4i-lradc-keys.c | 20 +++++++++++++++----
2 files changed, 18 insertions(+), 4 deletions(-)
--
2.26.3
next reply other threads:[~2021-04-30 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 4:20 Samuel Holland [this message]
2021-04-30 4:20 ` [PATCH v3 1/2] dt-bindings: sun4i-a10-lradc-keys: Accept wakeup-source property Samuel Holland
2021-04-30 4:20 ` [PATCH v3 2/2] input: sun4i-lradc-keys - Add wakup support Samuel Holland
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=20210430042003.4591-1-samuel@sholland.org \
--to=samuel@sholland.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=jernej.skrabec@siol.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).