public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Dmitry Torokhov <dtor@chromium.org>
Cc: Nick Crews <ncrews@chromium.org>,
	enric.balletbo@collabora.com, Benson Leung <bleung@chromium.org>,
	linux-leds@vger.kernel.org, jacek.anaszewski@gmail.com,
	lkml <linux-kernel@vger.kernel.org>,
	dlaurie@chromium.org, Daniel Erat <derat@google.com>,
	Guenter Roeck <groeck@google.com>
Subject: Re: [PATCH] platform/chrome: Add Wilco EC keyboard backlight LEDs support
Date: Fri, 8 Mar 2019 23:13:07 +0100	[thread overview]
Message-ID: <20190308221307.GB16125@amd> (raw)
In-Reply-To: <CAE_wzQ-Ds5a9iPuLTpV5mBHBtoUUh_-fRw66s0Su7eOifygqKQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]

Hi!

> > This patch is meant to be applied on top of the for-next
> > branch of the platform/chrome repository, as it uses some of
> > the code staged there.
> >
> > 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
> >
> > Some Wilco devices do not support a keyboard backlight. This
> > is checked in probe(), and in this case the sysfs entry will
> > not appear, and everything will behave normally.
> 
> It would be even better if we did not register platform device if EC
> does not support backlight.
> 
> > +       data->led.brightness_set = keyboard_led_set_brightness;
> > +       data->led.brightness_get = keyboard_led_get_brightness;
> 
> wilco_ec_mailbox() may sleep, so you need to assign it to
> led.brightness_set_blocking.

Hmm. Seeing get method there... can the EC change the brightness
without command from kernel?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2019-03-08 22:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08 20:38 [PATCH] platform/chrome: Add Wilco EC keyboard backlight LEDs support Nick Crews
2019-03-08 21:08 ` Pavel Machek
2019-03-11 15:29   ` Nick Crews
2019-04-04 11:24     ` Pavel Machek
2019-04-04 14:11       ` Nick Crews
2019-04-04 16:13       ` Dmitry Torokhov
2019-04-04 19:03         ` Pavel Machek
2019-04-04 19:09           ` Dmitry Torokhov
2019-04-04 19:23             ` Pavel Machek
2019-04-04 20:07               ` Dmitry Torokhov
2019-04-04 20:11                 ` Pavel Machek
2019-04-04 20:22                   ` Dmitry Torokhov
2019-04-04 20:34                     ` Pavel Machek
2019-03-08 22:01 ` Dmitry Torokhov
2019-03-08 22:13   ` Pavel Machek [this message]
     [not found]     ` <CAHX4x84pgHeseVphBUq0HLJ70KU-Fz1TQtaq1=iz=mFCDZuJkw@mail.gmail.com>
2019-03-11 21:52       ` Pavel Machek
2019-03-12 16:05     ` Nick Crews

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190308221307.GB16125@amd \
    --to=pavel@ucw.cz \
    --cc=bleung@chromium.org \
    --cc=derat@google.com \
    --cc=dlaurie@chromium.org \
    --cc=dtor@chromium.org \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@google.com \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=ncrews@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox