Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1599025yba; Thu, 4 Apr 2019 14:09:27 -0700 (PDT) X-Google-Smtp-Source: APXvYqy1eCwg7JyfpHhMVLK31yHP2jOlGDBPlp6m6EtGI/9CK73C6MFHk1DV8Hil6MG0myeyK9mu X-Received: by 2002:a17:902:6bc5:: with SMTP id m5mr8755833plt.180.1554412167832; Thu, 04 Apr 2019 14:09:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554412167; cv=none; d=google.com; s=arc-20160816; b=gHiiricFQ694T6Tjfv/yqUYY8zsnK4is32cjU5Xxwn2qfgq5mT1TrRXvrnWBnNV8eX 2a3EKQmUZ1DbcrHEa0wXC9ZC4VxegPd6Rtr/K4MR0awOeL6flNYk6OjN95sLYOf9jB7j sthZUu4W8koldw5n/faQVkRzkayGBddfZKILKYjDb/H0DfLD6g5aHU/5UgGC3EVeAR8o FW9xUQqOdw6O+k5atxArG9q5RcZebDcfXX7+LHY5GWeGcn1fIgm4gx5Mv/Ekg3VqUSMW 021Own/0iJu5rayq2KE+pXyyc1OC2PJk8i8bMs7iNlBghOStAWx6ygdU7PycyqZtcyPt +edQ== 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; bh=Q1Q4mZDhNQo67cVnEl925j/FtkLlwY7nyXSQx+Qf8nc=; b=OC7ac80qw1U0i9iII1neHc1PCc4Cysenb7st+Eh+pZkMAVgV2BMb0Jl700juI87qUh tQNBHkpg49f4nkBNTotsXSZhIpwducXGxEZvL/PCikEdWfSc3c9+iah58hHWcAHWgXg+ DMnnmD678F+VZL9eBK1juVGi0WBNBEyJkJvcNi6rcS2dYZ0c42/aqbSwKCxW4Ad1IKUx z4Uq4/a/aBfq7n5iWydGzMeugF8gJL8z+CMAdmZOx1GxaDIaqmilk5XfCl71BMs45PAg wgFcMy76zKoYdE7J0WWw8Hm12LquPFHQKCOL63OOHPLUnOxSptYNL4wKmGoU2qCphxOW xwqw== 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 ci5si10581583plb.145.2019.04.04.14.09.12; Thu, 04 Apr 2019 14:09:27 -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 S1730802AbfDDUUn (ORCPT + 99 others); Thu, 4 Apr 2019 16:20:43 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:33886 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729184AbfDDUUm (ORCPT ); Thu, 4 Apr 2019 16:20:42 -0400 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id 39D79802DD; Thu, 4 Apr 2019 22:20:31 +0200 (CEST) Date: Thu, 4 Apr 2019 22:20:42 +0200 From: Pavel Machek To: Dmitry Torokhov Cc: Nick Crews , Guenter Roeck , Enric Balletbo i Serra , Benson Leung , linux-leds@vger.kernel.org, Jacek Anaszewski , Alexandre Belloni , Alessandro Zummo , linux-rtc@vger.kernel.org, linux-kernel , Duncan Laurie , Simon Glass Subject: Re: [PATCH v5 3/3] platform/chrome: Standardize Chrome OS keyboard backlight name Message-ID: <20190404202042.GF29984@amd> References: <20190404185919.GB27340@amd> <20190404191931.GA29984@amd> <20190404200658.GD29984@amd> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="R6sEYoIZpp9JErk7" Content-Disposition: inline In-Reply-To: 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 --R6sEYoIZpp9JErk7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu 2019-04-04 13:13:34, Dmitry Torokhov wrote: > On Thu, Apr 4, 2019 at 1:06 PM Pavel Machek wrote: > > > > Hi! > > > > > > > It is *function* and maybe color that userspace is interested in,= and > > > > > here we have proper standardization in form of "kbd_backlight". D= evice > > > > > name is, well, device name. It should uniquely identify the devic= e led > > > > > is attached to, but otherwise is rarely interesting. If userspace= is > > > > > really concerned what kind of keyboard backlight it is it should > > > > > investigate parent device(s) and see what they end up with. > > > > > > > > That does not work. Userspace wants to know if it is internal keybo= ard > > > > or USB keyboard, not what kind of i2c controller the LED is connect= ed > > > > to. > > > > > > Why does userspace want to know it? > > > > For example to turn off backlight on internal keyboard when the lid is = closed. >=20 > Would you not want to turn off external as well? Not really. If I'm using machine with lid closed, external monitor and USB keyboard attached, I want to control backlight of USB keyboard, but backlight of internal keyboard can stay off. > And what to do if internal keyboard is not platform but USB? Like > Google "Whiskers"? (I am not sure why you decided to drop my mention > of internal USB keyboards completely off your reply). I don't have answers for everything. Even if you have USB keyboard, you'll likely still have backlight connected to embedded controller. If not, then maybe you have exception userland needs to know about. Still better than making everything an exception. > > > > grep for platform::mic_mute . > > > > > > > > (And platform is even pretty good match for how the LED is connected > > > > in your case). > > > > > > Until we get a secondary interface that is also "platform"... > > > > How would that happen? >=20 > It won't happen on Wilco, but you can't imagine that several blocks > get reused in the same device and they end up clashing? In the end, there will be just one internal keyboard backlight, right? Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --R6sEYoIZpp9JErk7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlymZxoACgkQMOfwapXb+vLn5QCfSbNvjo91bsUzD0yC/OdKMe60 gKoAnjqsLnPZ538cfiN5/TCl3hIXhsG7 =Dr/v -----END PGP SIGNATURE----- --R6sEYoIZpp9JErk7--