Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp60109ybn; Thu, 3 Oct 2019 01:23:19 -0700 (PDT) X-Google-Smtp-Source: APXvYqzvXW7PPTyc+IeZ31gAD18alsN7qWe8og+jrAVh8nm3FPHm52EgWqbiH65verTxw1NwkOZN X-Received: by 2002:a50:934c:: with SMTP id n12mr8331179eda.12.1570090999389; Thu, 03 Oct 2019 01:23:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570090999; cv=none; d=google.com; s=arc-20160816; b=oSHURTJY36SJrINyGJ/JGbO1wiPA6mhWKYZmGDU+1z+cmEdQuDqF68eSIEAYTJhVXA R+r4C9pca4rny+hxlOtDpFABt8fZSYfUuo5hnttjZ+BM6E/bkwo+iS2yhPCRFqhzMS57 tV3zsD1hlCjNJ4jWzXi2bm7R2SRwk3vlhfTJ4eDwrsuBKe2cyPOPOqhjPk3arKioZn+W gKtFItpJsQ03njwgMNWvK9bbq3KsgUoQntO0Xp500PjWEfApuQ33mqyXyQBNLyy7oy/Z 20RNO+dab34CQExxefwQqma0dj2D6PRmiExJnVCpjVpy3/E4Ak7iN8v9uRE8jBI9pjdv 1w3g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :organization:in-reply-to:subject:cc:to:from; bh=q5V7ZTcL1C7MF4/VTQjWRNoSa/IyU8l1T71z4wtOpQI=; b=MFwpRby6npdi0J0z/qYQR+qS2ZECdEhIhbnD3nMC5b21VlNdmEfuU2nhv1aTcdXzAu MTXa6HfYRYN4dD25s/VbN3b18d4eNrskPJMKslcfkmkH0L3gT5pDjWJ/h8/q9x8SB509 fe9Q8oUL1jugrETEYG31YuL4EHHbykgd5UhAFj96B4vVCSPAUP4faFdAA9II1tTS60aJ miTcVkZz/AC9gt3TItMF4joFGL2TGIdkZH8L4Y5eZ0nXcViVJZyL10OOUGBu6AMFq7Mr l4LpDgk0Zo8/C6EL8BAZNbP2vprSTZ1Yr2owf80KxnPYrmveiNKgQYVcxDt6dCgrczL0 m7+w== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h91si1008807edd.270.2019.10.03.01.22.54; Thu, 03 Oct 2019 01:23:19 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727357AbfJCITY (ORCPT + 99 others); Thu, 3 Oct 2019 04:19:24 -0400 Received: from mga05.intel.com ([192.55.52.43]:63621 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725497AbfJCITX (ORCPT ); Thu, 3 Oct 2019 04:19:23 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Oct 2019 01:19:23 -0700 X-IronPort-AV: E=Sophos;i="5.67,251,1566889200"; d="scan'208";a="182316984" Received: from jnikula-mobl3.fi.intel.com (HELO localhost) ([10.237.66.161]) by orsmga007-auth.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Oct 2019 01:19:16 -0700 From: Jani Nikula To: Jonathan Corbet , Mat King Cc: Daniel Thompson , 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 In-Reply-To: <20191002094650.3fc06a85@lwn.net> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20191002094650.3fc06a85@lwn.net> Date: Thu, 03 Oct 2019 11:19:13 +0300 Message-ID: <87muei9r7i.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 02 Oct 2019, Jonathan Corbet wrote: > On Tue, 1 Oct 2019 10:09:46 -0600 > Mat King wrote: > >> I have been looking into adding Linux support for electronic privacy >> screens which is a feature on some new laptops which is built into the >> display and allows users to turn it on instead of needing to use a >> physical privacy filter. In discussions with my colleagues the idea of >> using either /sys/class/backlight or /sys/class/leds but this new >> feature does not seem to quite fit into either of those classes. > > FWIW, it seems that you're not alone in this; 5.4 got some support for > such screens if I understand things correctly: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=110ea1d833ad Oh, I didn't realize it got merged already, I thought this was related... So we've already replicated the backlight sysfs interface problem for privacy screens. :( BR, Jani. -- Jani Nikula, Intel Open Source Graphics Center