Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp1861855ybv; Fri, 21 Feb 2020 04:46:32 -0800 (PST) X-Google-Smtp-Source: APXvYqzCVnC4nlr5yf47T49A/vFVlqK3cVnzuL6Jzt53CNikWmxBkSB+g7ks+UidrC1b6sS/oCDq X-Received: by 2002:a05:6830:1691:: with SMTP id k17mr28856163otr.282.1582289192516; Fri, 21 Feb 2020 04:46:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582289192; cv=none; d=google.com; s=arc-20160816; b=kQx7d6gDArwdlEAiFP0u5+uUOUegjO3urZeBULE3LNIuQP/LG/huUHDCydwa64yEDp QK6leZwCmZLDm4x8sXd7hovk589stt0VHM9DQj318QKWJV6Dk7jsjNrBDoRG/w9IA/5l ao1E3fiple6fXWZWRvcOMUMuTkgnOx+k+O535WOV1o9xZai1EsuRQOaIqflgabM+CD5/ +OPtINuUsEIXiIPUj0yc/qz0GcvpID9hBbSwwkh8PFgp7MQbBOR4GZmz0VbJaNuxRaqA ioSC48UU93WoEBlGdo/zQQGbE1PyvLCM+uiNOiI5nq8ey8RoehzlvuQ/JD30KztwmdLo HNyQ== 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:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id:dkim-signature; bh=pBLVBUs542X1Vq8pAdGQmP+xNdNH0Q/EkNS8GTw8+pk=; b=TDGq6mqmL0Ej1dflSSfRbYiM5nZZuYwH2N9uJqQ5Lf39cg06ZBvcznSCFhMlrCGsOX BGDnN4yksJEF1cY9lFIho93SulCxPsMgma500gMflKpFQ6R5x3+bRl1DCKw2uDTGlgaA lkORMHldB6ETvtUJ5MIxjeYywwwV3Qk0CbznfcGKV0gy+e/eLYEnAyzGcxGYD5y52qBr wVpeHBmvszK8GIEz9wfh4Cn0bveQAG+u/TAGm/6WZUtuMbN2Pxtg6L4ejh/jArQYrw/O G+xW8ILeIVc+NcmV2PnvN/AbtIFOcd2z31kpoLsFDFoESMezMX8HZr0yb+45Ex/UDb8j D+DA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=ZmGGFtw0; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j25si724918oij.242.2020.02.21.04.46.17; Fri, 21 Feb 2020 04:46:32 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=ZmGGFtw0; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728114AbgBUMp7 (ORCPT + 99 others); Fri, 21 Feb 2020 07:45:59 -0500 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:55252 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727720AbgBUMp7 (ORCPT ); Fri, 21 Feb 2020 07:45:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1582289157; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=pBLVBUs542X1Vq8pAdGQmP+xNdNH0Q/EkNS8GTw8+pk=; b=ZmGGFtw0L4ZS2T1Or3WGz4/qqfQvJQO+FairyrMoDr19YOzcAR7AkLp+PivlJYkaPOg6pH pgBnyUeF7+0oRFBknb3mkQXxMadhGxffy2sFb9eiCXCxxKMTYwCbjg+2OaFByY3HXQE+E2 fyEEW1VMFVf7bE96gsI8nq10K5slBG8= Received: from mail-wm1-f72.google.com (mail-wm1-f72.google.com [209.85.128.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-302-9giSfDOQOAawzn9_FDGADA-1; Fri, 21 Feb 2020 07:45:56 -0500 X-MC-Unique: 9giSfDOQOAawzn9_FDGADA-1 Received: by mail-wm1-f72.google.com with SMTP id k21so531207wmi.2 for ; Fri, 21 Feb 2020 04:45:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=pBLVBUs542X1Vq8pAdGQmP+xNdNH0Q/EkNS8GTw8+pk=; b=OQrZNYNe7eOzBL9MqyRUAKWWV8lUjJLmPk2cbUGqjdb/hvG7Ozo7WLgteIZqI8M8Ah bCFAleTk5Rt+yAU8iyMT+eWw2xJv7RSoBBvwAtwzY3dFLg+TSAHR3M9s1cnlGZ2wBwYQ mIv7OX4N5DR11n2BIAW8TAzwoISHOZcPqCBJpYzhgb8FCCUvYZp6+be7EmwB0YC4Urpa +0ACFlybYElu5qXdeqS1UW2Jx/TrrkfU1GEXeWLalY5veQ4Q08Z3E1OMSJMIw69KWVzK ireddLNRuq6xLthyJe1WYAphDBd7zeqheo4JtFwJxhedy1Ro8+nwyYoKx2/I8fqfKPOR juhw== X-Gm-Message-State: APjAAAUPoCjuBQrZhoGpBRy/geUyL3OP8rRQoE8uJxDOtWCbi/jz1ray 81yll08YoOzMw2oxAhwGz1Kb1ioACdgwg8v+SdMx7Q3wKwQaXJN44KmahOn65EkyzNBv8Z3aChv I1WAw6IBzddVNgECbEX4kb+8E X-Received: by 2002:adf:f084:: with SMTP id n4mr48240489wro.200.1582289155138; Fri, 21 Feb 2020 04:45:55 -0800 (PST) X-Received: by 2002:adf:f084:: with SMTP id n4mr48240462wro.200.1582289154929; Fri, 21 Feb 2020 04:45:54 -0800 (PST) Received: from dhcp-64-37.muc.redhat.com (nat-pool-muc-t.redhat.com. [149.14.88.26]) by smtp.gmail.com with ESMTPSA id r6sm3972501wrq.92.2020.02.21.04.45.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 21 Feb 2020 04:45:54 -0800 (PST) Message-ID: Subject: Re: [External] Re: [PATCH] thinkpad_acpi: Add sysfs entry for lcdshadow feature From: Benjamin Berg To: Jani Nikula , Rajat Jain , Mark Pearson Cc: Andy Shevchenko , Nitin Joshi , Mat King , Daniel Thompson , Jingoo Han , Henrique de Moraes Holschuh , Darren Hart , Andy Shevchenko , Thinkpad-acpi devel ML , Platform Driver , Nitin Joshi1 , Linux Kernel Mailing List , dri-devel , Greg Kroah-Hartman , Pekka Paalanen Date: Fri, 21 Feb 2020 13:45:53 +0100 In-Reply-To: <87tv3kxgyx.fsf@intel.com> References: <20200220074637.7578-1-njoshi1@lenovo.com> <87tv3kxgyx.fsf@intel.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.34.4 (3.34.4-1.fc31) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Fri, 2020-02-21 at 14:28 +0200, Jani Nikula wrote: > In general I think it's preferrable if the hotkey sends the key event to > userspace that then makes the policy decision of what, if anything, to > do with it. Everything is much easier if the policy is in userspace > control. For example, you could define content based policies for > enabling privacy screen, something that is definitely not possible with > firmware. > > I emphatize with the desire to just bypass everything at the > hardware/firmware level, because that is totally in your control (as an > OEM), and requires no interaction with the operating system > initially. Exposing the read-only state of the privacy screen is > helpful, but prevents the OS from building more advanced features on > top, failing to reach the full potential of the nice hardware feature. There seems to be a slight misunderstanding here. On the Lenovo laptops the feature is automatically adjusted by the Firmware. However, the setting itself is read/write and it can also be controlled from userspace. In principle, I agree that it makes sense to control these things from software and have a toggle key event that is send around. It has the unfortunate disadvantage though that it requires updating the entire userspace. Including the ugly side effect that we continue to have trouble to support these things on X11 due protocol restrictions with "high" key codes (>= 248). Benjamin