From: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
To: linux-input@vger.kernel.org, devicetree@vger.kernel.org
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
andrzej.p@collabora.com, kernel@collabora.com
Subject: [PATCH 1/6] tty/sysrq: Remove linux,sysrq-reset-seq
Date: Mon, 11 May 2020 15:59:13 +0200 [thread overview]
Message-ID: <20200511135918.8203-2-andrzej.p@collabora.com> (raw)
In-Reply-To: <20200511135918.8203-1-andrzej.p@collabora.com>
Nobody in the tree uses linux,sysrq-reset-seq in Device Tree source files.
Remove the corresponding code.
Signed-off-by: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
---
drivers/tty/sysrq.c | 37 -------------------------------------
1 file changed, 37 deletions(-)
diff --git a/drivers/tty/sysrq.c b/drivers/tty/sysrq.c
index 0dc3878794fd..93202fc24308 100644
--- a/drivers/tty/sysrq.c
+++ b/drivers/tty/sysrq.c
@@ -720,41 +720,6 @@ static void sysrq_detect_reset_sequence(struct sysrq_state *state,
}
}
-#ifdef CONFIG_OF
-static void sysrq_of_get_keyreset_config(void)
-{
- u32 key;
- struct device_node *np;
- struct property *prop;
- const __be32 *p;
-
- np = of_find_node_by_path("/chosen/linux,sysrq-reset-seq");
- if (!np) {
- pr_debug("No sysrq node found");
- return;
- }
-
- /* Reset in case a __weak definition was present */
- sysrq_reset_seq_len = 0;
-
- of_property_for_each_u32(np, "keyset", prop, p, key) {
- if (key == KEY_RESERVED || key > KEY_MAX ||
- sysrq_reset_seq_len == SYSRQ_KEY_RESET_MAX)
- break;
-
- sysrq_reset_seq[sysrq_reset_seq_len++] = (unsigned short)key;
- }
-
- /* Get reset timeout if any. */
- of_property_read_u32(np, "timeout-ms", &sysrq_reset_downtime_ms);
-
- of_node_put(np);
-}
-#else
-static void sysrq_of_get_keyreset_config(void)
-{
-}
-#endif
static void sysrq_reinject_alt_sysrq(struct work_struct *work)
{
@@ -984,8 +949,6 @@ static inline void sysrq_register_handler(void)
{
int error;
- sysrq_of_get_keyreset_config();
-
error = input_register_handler(&sysrq_handler);
if (error)
pr_err("Failed to register input handler, error %d", error);
--
2.17.1
next prev parent reply other threads:[~2020-05-11 13:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 13:59 [PATCH 0/6] Magic SysRq extensions Andrzej Pietrasiewicz
2020-05-11 13:59 ` Andrzej Pietrasiewicz [this message]
2020-05-11 17:58 ` [PATCH 1/6] tty/sysrq: Remove linux,sysrq-reset-seq Dmitry Torokhov
2020-05-12 9:21 ` Andrzej Pietrasiewicz
2020-05-11 13:59 ` [PATCH 2/6] dt-bindings: input: Remove linux,sysrq-reset-seq binding Andrzej Pietrasiewicz
2020-05-11 13:59 ` [PATCH 3/6] tty/sysrq: Allow configurable SysRq key Andrzej Pietrasiewicz
2020-05-11 16:18 ` Greg Kroah-Hartman
2020-05-11 18:01 ` Dmitry Torokhov
2020-05-12 9:46 ` Andrzej Pietrasiewicz
2020-06-19 16:28 ` [PATCH] tty/sysrq: Add alternative " Andrzej Pietrasiewicz
2020-06-21 21:21 ` Pavel Machek
2020-06-26 11:07 ` Andrzej Pietrasiewicz
2020-06-22 6:24 ` Jiri Slaby
2020-06-26 11:51 ` Andrzej Pietrasiewicz
2020-07-09 5:05 ` Dmitry Torokhov
2020-07-09 8:15 ` Andrzej Pietrasiewicz
2020-05-11 13:59 ` [PATCH 4/6] tty/sysrq: Extend the sysrq_key_table to cover capital letters Andrzej Pietrasiewicz
2020-05-11 13:59 ` [PATCH 5/6] tty/sysrq: Add configurable handler to signal a process Andrzej Pietrasiewicz
2020-05-11 16:20 ` Greg Kroah-Hartman
2020-05-14 9:06 ` kbuild test robot
2020-05-11 13:59 ` [PATCH 6/6] tty/sysrq: Add configurable handler to execute a compound action Andrzej Pietrasiewicz
2020-05-11 16:21 ` Greg Kroah-Hartman
2020-05-11 18:29 ` Dmitry Torokhov
2020-05-12 9:15 ` Andrzej Pietrasiewicz
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=20200511135918.8203-2-andrzej.p@collabora.com \
--to=andrzej.p@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=kernel@collabora.com \
--cc=linux-input@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).