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 linux-cve-announce PHC
Open Source and information security mailing list archives

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

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

Message-ID: <CAE_wzQ8oRKjmA0x01+gmPuQQQ=yCxS+v+c9=VyQSg1EKP8bDkQ@mail.gmail.com>
Date:   Mon, 25 Mar 2019 13:48:54 -0700
From:   Dmitry Torokhov <dtor@...gle.com>
To:     Pavel Machek <pavel@....cz>
Cc:     Nick Crews <ncrews@...omium.org>, enric.balletbo@...labora.com,
        Benson Leung <bleung@...omium.org>, linux-leds@...r.kernel.org,
        jacek.anaszewski@...il.com, lkml <linux-kernel@...r.kernel.org>,
        dlaurie@...omium.org, sjg@...gle.com,
        Guenter Roeck <groeck@...gle.com>
Subject: Re: [PATCH 3/3] platform/chrome: Add Wilco EC keyboard backlight LEDs support

On Fri, Mar 22, 2019 at 4: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...

It should not. But the current convention is "<device>::kbd-backlight":

dtor@...r-ws:~/kernel/work $ git grep "::kbd_backlight" -- drivers/
drivers/hid/hid-asus.c: drvdata->kbd_backlight->cdev.name =
"asus::kbd_backlight";
drivers/hid/hid-google-hammer.c:        kbd_backlight->cdev.name =
"hammer::kbd_backlight";
drivers/hwmon/applesmc.c:       .name                   = "smc::kbd_backlight",
drivers/input/misc/ims-pcu.c:            "pcu%d::kbd_backlight",
pcu->device_no);
drivers/platform/chrome/cros_kbd_led_backlight.c:       cdev->name =
"chromeos::kbd_backlight";
drivers/platform/x86/asus-laptop.c:             cdev->name =
"asus::kbd_backlight";
drivers/platform/x86/asus-wmi.c:                asus->kbd_led.name =
"asus::kbd_backlight";
drivers/platform/x86/dell-laptop.c:     .name           = "dell::kbd_backlight",
drivers/platform/x86/samsung-laptop.c:          samsung->kbd_led.name
= "samsung::kbd_backlight";
drivers/platform/x86/thinkpad_acpi.c:           .name           =
"tpacpi::kbd_backlight",
drivers/platform/x86/toshiba_acpi.c:            dev->kbd_led.name =
"toshiba::kbd_backlight";

and userspace already knows how to handle these.

Thanks.

-- 
Dmitry