linux-kernel - Re: [PATCH 3/3] platform/chrome: Add Wilco EC keyboard backlight LEDs support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 22 Mar 2019 09:49:57 -0600
From:   Nick Crews <ncrews@...omium.org>
To:     Pavel Machek <pavel@....cz>
Cc:     Enric Balletbo i Serra <enric.balletbo@...labora.com>,
        Benson Leung <bleung@...omium.org>, linux-leds@...r.kernel.org,
        jacek.anaszewski@...il.com,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Duncan Laurie <dlaurie@...omium.org>,
        Simon Glass <sjg@...gle.com>,
        Guenter Roeck <groeck@...gle.com>,
        Dmitry Torokhov <dtor@...gle.com>, Simon Que <sque@...gle.com>
Subject: Re: [PATCH 3/3] platform/chrome: Add Wilco EC keyboard backlight LEDs support

On Fri, Mar 22, 2019 at 5:35 AM Pavel Machek <pavel@....cz> wrote:
>
> Hi!
>
> > The EC is in charge of controlling the keyboard backlight on
> > the Wilco platform. We expose a standard LED class device at
> > /sys/class/leds/wilco::kbd_backlight. This driver is modeled
> > after the standard Chrome OS keyboard backlight driver at
> > drivers/platform/chrome/cros_kbd_led_backlight.c
>
> Please make it platform::kbd_backlight . Userland should not need to
> know what wilco is...

The corresponding device for normal chromeos devices is
"chromeos::kbd_backlight". I wanted to differentiate this device from
that one, so I thought that "wilco" a similar level of specific-ness as
"chromeos". Using "platform" seems too general. The power manager
daemon that controls the backlight just searches for LEDs ending with
"*:kbd_backlight" so it should work for that, and I figured any user just
browsing through sysfs would be able to guess what the LED does.

This is maybe a question for those who will need to maintain the
Chrome OS system after adding this? Could some more
Chrome OS-specific people chime in on this? I also CC'ed Simon
Que, the author of the original driver (Simon, we are talking about
https://lkml.org/lkml/2019/3/21/999)

>
> What is wilco, anyway?

Wilco is a new Chrome OS device which does not use the same embedded
controller as the rest of the Chrome OS ecosystem. Thus, we need this new
driver because the old one will not be compatible.

>
>                                                                         Pavel
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html