Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp515311ybt; Fri, 26 Jun 2020 05:12:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyf1NKxrI30Fdr6qoDMyNNyxx5tScd3qSIxHKeUA5KtwOjgsS5yieCBZaZfmu3um3zUnyRu X-Received: by 2002:a17:906:3042:: with SMTP id d2mr2178132ejd.420.1593173542802; Fri, 26 Jun 2020 05:12:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593173542; cv=none; d=google.com; s=arc-20160816; b=VP/cT5LsFePNvAsEh5MaaOcWjjV0wbub4IiyoBLFV+fPA/jPf593qYhDLD/ppu5lHz uSTU6NR7JswFtGdQBP7/kHatdCdw3Br5IT4Rh379BGLkfGyUwN7NOPl/E0McOx/yCSMH xLwN553ujVJwjcy9M5L4g9gSaUnNnn0G8N3uWCwEZQyN4k7QxSzv/JwD7hMppxNX+OjU qmOG2BY0zfAARc+h+7oxxK6pz0GBRTEFX+M1b+x/SbkWuw4cy9jNBjblOQG2u0Dr/6zX ZpJevdzCUZgfobCuSqlnjgZClXWGkGePvufKihoSYBfv/FLuHqJHv2TG+zHgk9Wg3cVN KcfA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=YjJDmlFlxL6Xq0A0j0CsMVH7WgNvCaie+do3QAIqAL4=; b=btxCuUZgSuCOkNevWROYpddAYyCytWqY53WTRH4jwdNIExTISFvpoNxR6RxKjhnhzw SOuiXLE+xmMnMhebVmG/VaB8f3zNPAMZtRqJDaxGzkDoZr5WY3GKtJH1KARsC8XN/LnK knsxFGV7QhLnJs+k3NbzNAnjupbCAZhxu1dbIwbMqCHIPumAcU+KCR1BVdXuPccrKeyX Z76AcXCK6hsUkJJPOvwvhcLR8WmuSEkPealmbIak8WIqbfh+/2Q52YRRFxsbUv8L7KCp axVko2XnYfK/P01m/XzZtGk4ybekPLdsdhpx+Bnq6RnwVvwmsln5CXYm7dEOn6xCfD92 FuFA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s25si12547444eds.341.2020.06.26.05.12.00; Fri, 26 Jun 2020 05:12:22 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728303AbgFZLHq (ORCPT + 99 others); Fri, 26 Jun 2020 07:07:46 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:48404 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728232AbgFZLHp (ORCPT ); Fri, 26 Jun 2020 07:07:45 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: andrzej.p) with ESMTPSA id A0FB72A5A67 Subject: Re: [PATCH] tty/sysrq: Add alternative SysRq key To: Pavel Machek Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org, Greg Kroah-Hartman , Dmitry Torokhov , Jiri Slaby , kernel@collabora.com References: <20200511180145.GU89269@dtor-ws> <20200619162819.715-1-andrzej.p@collabora.com> <20200621212106.GB22512@amd> From: Andrzej Pietrasiewicz Message-ID: <8836da2c-b38d-7779-bef0-857ead18b557@collabora.com> Date: Fri, 26 Jun 2020 13:07:38 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <20200621212106.GB22512@amd> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Pavel, W dniu 21.06.2020 o?23:21, Pavel Machek pisze: > Hi! > >> There exist machines which don't have SysRq key at all, e.g. chromebooks. >> >> This patch allows configuring an alternative key to act as SysRq. Devices >> which declare KEY_SYSRQ in their 'keybit' bitmap continue using KEY_SYSRQ, >> but other devices use the alternative SysRq key instead, by default F10. >> Which key is actually used can be modified with sysrq's module parameter. >> >> Signed-off-by: Andrzej Pietrasiewicz > > So... SysRq was selected because you are not going to press > Alt-Printscreen-X by default. This patch does not change the Alt-PrintScreen/SysRq-something sequence. What it does instead is making the 'PrintScreen/SysRq' component of the sequence configurable for input devices which don't declare KEY_SYSRQ in their 'keybit' bitmap, so the sequence becomes: Alt--something If the alternative sysrq key is used (i.e. the input device in question does not declare KEY_SYSRQ), it is F10 by default and _that_ can be changed with the module parameter. To summarize: - devices which do declare KEY_SYSRQ must use Alt-PrintScreen/SysRq-something - devices which don't declare KEY_SYSRQ must use Alt-F10-something, but F10 can be changed with a module parameter to something else Regards, Andrzej