Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp3515490ybp; Sun, 6 Oct 2019 13:43:12 -0700 (PDT) X-Google-Smtp-Source: APXvYqwidO6xPrCQ+AsRRPrl5NGwjoShZABP7I5i4NQ0J0BtlJtYAmOc1l0rhOQlnmLKV4HpTuTR X-Received: by 2002:a50:cf8b:: with SMTP id h11mr24902138edk.236.1570394591958; Sun, 06 Oct 2019 13:43:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570394591; cv=none; d=google.com; s=arc-20160816; b=IwQEGDsDVWhfQzyJblROm9Hfsm0C9jKEU+y7I+0TaLbalcIZbMpJv1N18E07DtXL/U 0MofurLHpx9aBMQiBynTupGyMvzWNlZzndvu0TvhUZZS6xf3uqvbIsflxON8jG0z1/aW Df5DL2g0NcAoUYib2RRBBUN2/IIA++o7HNJIH5BxQ5BI9XXNYAGdTdzUrqT5erLL28Bb tCvp1VIwZIevBCW+VvWa9fXZQlIJDJL8M70zJR+L9Qkm9TWVWaaFODAgEfrYpQ12Yx31 v6nxgs5wN8iXeGcArwP0xV++0AgaHyn+B/+Dx6cgfszBUFGa1LLduzzdWMWyGeChm1LM VytQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:dkim-signature; bh=ejeoZ3ISdZsRr54JCVMXEDJt/1VFp4bSIyHVCBG50b8=; b=fOTbyfw49HVcR2L3HQFGkmCqYqXZO7GP6WvBEfDd4ZKOd+DcB4iM8CspmocUYGXw60 HUWbOPuTbm6VF+GreYy14rilEeIYRRU/lFHkwzUmMEg6DnS6z3/in07Z1+2xyALpG5sJ Hpg9m9Z5VQtAz5NN+lrSVF4yhE0yQ0iPMdqk9uYffm7r7etkx79kqgdz+p16REzu8HYO 3Kc2+yxT+ahXn499hc5rMsr2PNKm45/XOwYM3M+5AcVKLWAactHyvr5JkY3McHS5h7rW dUO1/Jr6xM8+2P1vQRnuUFLgXUDmjPHx2ucdu556ikyEQxqZ1dVfw7hXan/M+/22mPo7 KoYQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@hmh.eng.br header.s=fm3 header.b="mHHW/VKL"; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=xrKbdHsW; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f1si6009045eje.338.2019.10.06.13.42.46; Sun, 06 Oct 2019 13:43:11 -0700 (PDT) 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=@hmh.eng.br header.s=fm3 header.b="mHHW/VKL"; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=xrKbdHsW; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726712AbfJFUk6 (ORCPT + 99 others); Sun, 6 Oct 2019 16:40:58 -0400 Received: from wnew4-smtp.messagingengine.com ([64.147.123.18]:49041 "EHLO wnew4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725953AbfJFUk5 (ORCPT ); Sun, 6 Oct 2019 16:40:57 -0400 X-Greylist: delayed 404 seconds by postgrey-1.27 at vger.kernel.org; Sun, 06 Oct 2019 16:40:57 EDT Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailnew.west.internal (Postfix) with ESMTP id 2110C3EC; Sun, 6 Oct 2019 16:34:12 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Sun, 06 Oct 2019 16:34:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hmh.eng.br; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=ejeoZ3ISdZsRr54JCVMXEDJt/1V Fp4bSIyHVCBG50b8=; b=mHHW/VKLracUbzT5k/Yt/2zRfz6PcGuqBRiKbisrLOy YtyOjbUfAq/9fJ2ZoRWnMBBouN+CtMbptke0sdVkzxgNfXNK4fXr5NwU2TCml+CD Gou69jWnyqS+XBOfvhKRU2kD05KF9oMt+nDyI1osG8dEh87GchKnAKVX0nRiOoKm sxjrfniejyMc2Ueh8gmQSGqhPXBOU24qLLkA3s7FyWMEhz2gIefsaJA2lLSTtP2h Lpyy3Pe5qQ7U01c4eyi4jLiFlRYVFo4McCUY4tSjsj/YPAtNqs+8U6R4FpaZgMUl 8oGfzelTrlI0KuATIjokWOXZ+CObcXMQFKvxYUxTpng== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=ejeoZ3 ISdZsRr54JCVMXEDJt/1VFp4bSIyHVCBG50b8=; b=xrKbdHsWlLiTRqHDsYu+te DiSiarnwMVNrf6IHi3Up2h6zQhhJhpn8haR3Gq5GO9iil89OWjBzN2aYNXKkxdac glWTIOoHbfKXNQc8IEcNgyUt9dCulbHizKaEHIBJ3IFHbsuIRafEDxNeomAWP3bB 8ZYdDkafQAdN3YG+Ntf76ClDXtqAsErAPn6uUSY0nhUuEklyKT+m2t8iN1MuwWUS 7M6UElsmFH1H0hgHNJtXQwz8swjBa5uTQzJpXpRz9PKWCc2kwIxboDKiUHaN2kNO pgrHPQfJ/XaVwiClqz9eipCUVXN7wPGFU1VadWme6yt19An6NxweIDtNJilO0w3g == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrheehgdduheegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjfgesthdttddttdervdenucfhrhhomhepjfgvnhhr ihhquhgvucguvgcuofhorhgrvghsucfjohhlshgthhhuhhcuoehhmhhhsehhmhhhrdgvnh hgrdgsrheqnecukfhppedvtddurdekvddrgeehrddvfeegnecurfgrrhgrmhepmhgrihhl fhhrohhmpehhmhhhsehhmhhhrdgvnhhgrdgsrhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from khazad-dum.debian.net (unknown [201.82.45.234]) by mail.messagingengine.com (Postfix) with ESMTPA id 8D971D60057; Sun, 6 Oct 2019 16:34:10 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by localhost.khazad-dum.debian.net (Postfix) with ESMTP id 06BA2340015B; Sun, 6 Oct 2019 17:34:09 -0300 (-03) X-Virus-Scanned: Debian amavisd-new at khazad-dum.debian.net Received: from khazad-dum.debian.net ([127.0.0.1]) by localhost (khazad-dum2.khazad-dum.debian.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id imtwoQQbVsa9; Sun, 6 Oct 2019 17:34:08 -0300 (-03) Received: by khazad-dum.debian.net (Postfix, from userid 1000) id 10243340015A; Sun, 6 Oct 2019 17:34:07 -0300 (-03) Date: Sun, 6 Oct 2019 17:34:07 -0300 From: Henrique de Moraes Holschuh To: Daniel Thompson Cc: Jani Nikula , Jonathan Corbet , Mat King , rafael@kernel.org, gregkh@linuxfoundation.org, Ross Zwisler , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Jingoo Han , Rajat Jain , Lee Jones , Alexander Schremmer , Andy Shevchenko Subject: Re: New sysfs interface for privacy screens Message-ID: <20191006203407.GA14301@khazad-dum.debian.net> References: <20191002094650.3fc06a85@lwn.net> <87muei9r7i.fsf@intel.com> <20191003102254.dmwl6qimdca3dbrv@holly.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191003102254.dmwl6qimdca3dbrv@holly.lan> X-GPG-Fingerprint1: 4096R/0x0BD9E81139CB4807: C467 A717 507B BAFE D3C1 6092 0BD9 E811 39CB 4807 User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 03 Oct 2019, Daniel Thompson wrote: > I guess... although the Thinkpad code hasn't added any standard > interfaces (no other laptop should be placing controls for a privacy > screen in /proc/acpi/ibm/... ). Maybe its not too late. As far as I am concerned, it is *not* too late. And you can always have a driver-private way of messing with something, and a more generic way of doing the same thing. thinkpad-acpi will always welcome patches switching to the new generic way (as long as we can have a deprecation period *for long-time-used facilities* -- which is not the case of the privacy screen, no deprecation period need there). The privacy thing is too new, feel free to design a generic one and send in a patch *switching* thinkpad-acpi to the new generic one. I would ACK that. If the subsystem maintainer also agrees, (and nobody *seriously* complain about it from userspace), the private interface would be gone just like that. -- Henrique Holschuh