Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp1682699imm; Sat, 16 Jun 2018 00:34:21 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLlUtwj9+aTyraaAe0310hmrpIKsT/oQTcEQ+T2kkrqnGTii6p/D+smyd4khP2hHTwa5JEC X-Received: by 2002:a17:902:246a:: with SMTP id m39-v6mr5582601plg.141.1529134461375; Sat, 16 Jun 2018 00:34:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529134461; cv=none; d=google.com; s=arc-20160816; b=z1X4EklbKU8WDJphIWpdueyiYuEXY9MndfKJryot0xuuzPdesTwwxMVpA5sGxRnRBb KfwbXPZGS7YJJtABFxvCIOhVDn+VESsDkRm4D+IMZyiPdj7SWJAmU5XgCOZ45joALQp6 l4+JqWp1Shsc7fRNAjjX4UXiMp1QTXlWUv28Za3PSTYHAWvQUd1G5JM10o7NtIH3bYkD 2toUk8f3hOlm8jJIROoRF6KnDhZdvoCfDPLiGbtyZknxUmPRCDw7O4HW5rIXp+EFqr5H 1C8WumsFaNe5Q8m1Lpv0zvYQ4lpTVZDC5kupBN9VTHYhZv0FPTqQraU2yKGNPQEgNH7f nU9w== 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:arc-authentication-results; bh=YGa+R9+6Xd8fSH2mgx64zM1PPN+799pYmAH45Yr3fjM=; b=lOtnSZP2lFjY76XesRaAWZ/OD1W+chkD8qZL3FeTIZ28RCmBoCJkXlHLe6KEQL8Soc T2lPC6AS8ekwPcO7eRR6itDs1qfACIu7zbCgpwuixrgbfNgOrzzFCb+TBOS2rShq6tDc ccPR2ReUwtWGhX9yru/E3rct9CJR+0reYr3BOAD2YDG6o3wwscsilsnElIWVqUJ2GPp0 oTYxoGBvvzpEfSBWNuYjr6CzMiWPTy8g4UA1BweMKpIkqyEzWJlobCAfA/91CeNukP/q shJjqr5arBleL4nA8PX3aQsR+Lhdz4ZUk0Dn7NF7q0oECh0M1z8WKkkuW6LG8IByHe3y B7bA== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f17-v6si7860605pgv.383.2018.06.16.00.34.06; Sat, 16 Jun 2018 00:34:21 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754071AbeFPHdl (ORCPT + 99 others); Sat, 16 Jun 2018 03:33:41 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:58225 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753776AbeFPHdj (ORCPT ); Sat, 16 Jun 2018 03:33:39 -0400 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id B2AE880548; Sat, 16 Jun 2018 09:33:37 +0200 (CEST) Date: Sat, 16 Jun 2018 09:33:34 +0200 From: Pavel Machek To: Henrique de Moraes Holschuh Cc: Pali =?iso-8859-1?Q?Roh=E1r?= , Henrique de Moraes Holschuh , ibm-acpi-devel@lists.sourceforge.net, platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: ThinkPad T480s & LED_MUTE, LED_MICMUTE Message-ID: <20180616073334.GA13880@amd> References: <20180608111057.4wxpg7m7nm7suf6n@pali> <20180615112606.GA3986@amd> <20180615113728.h7snxhe2juaqvjyx@pali> <20180615123007.nxsymdvr3nj3it5i@khazad-dum.debian.net> <20180615190915.cdntdeesc52ei35u@pali> <20180615233628.gy2ffgupctheyqof@khazad-dum.debian.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN" Content-Disposition: inline In-Reply-To: <20180615233628.gy2ffgupctheyqof@khazad-dum.debian.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --J/dobhs11T7y2rNN Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! On Fri 2018-06-15 20:36:28, Henrique de Moraes Holschuh wrote: > On Fri, 15 Jun 2018, Pali Roh=E1r wrote: > > This means that kernel should not export any led class device. Or when > > exported, then "set" operation should always fail. >=20 > "not export" is right. >=20 > > > 2. Otherwise implement it in-kernel, so that userspace cannot unmute > > > when the human has activated the "mute" switch, and the LED cannot= be > > > controlled by userspace to lie (report mute when it is not mute). > >=20 > > This looks like a good candidate to use led "trigger" interface. Create > > a mute trigger and attach it to that led device. >=20 > Maybe, as long as done in-kernel and not possible to mess with from > userspace. Question is if we want flexibility or security. If we want security, going through LED subsystem makes no sense, just control the LED as hardware would, or let hardware do it. For full flexibility, just export the LED and use normal mechanisms we have (such as triggers). root should be allowed to configure the LEDs, and he can change the kernel, too, so... Best regards, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --J/dobhs11T7y2rNN Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlskvU4ACgkQMOfwapXb+vK1RQCeLVrYE7V2GyAon12ifTwHynuY BBgAoLNGg86oMopWJezrgikBQEkW/03t =g9hn -----END PGP SIGNATURE----- --J/dobhs11T7y2rNN--