From: Darren Hart <dvhart@infradead.org>
To: Gabriele Mazzotta <gabriele.mzt@gmail.com>
Cc: mjg59@srcf.ucam.org, pali.rohar@gmail.com,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, A.Sloman@cs.bham.ac.uk,
computersforpeace@gmail.com
Subject: Re: [PATCH] dell-laptop: use dedicated sysfs file for ALS
Date: Sun, 18 Jan 2015 09:52:42 -0800 [thread overview]
Message-ID: <20150118175241.GA56582@vmdeb7> (raw)
In-Reply-To: <1421244357-31103-1-git-send-email-gabriele.mzt@gmail.com>
On Wed, Jan 14, 2015 at 03:05:57PM +0100, Gabriele Mazzotta wrote:
> The ambient light sensor doesn't act like an input trigger, so it has
> to be kept separate. The sensor readings are used to determine whether
> the conditions to change the keyboard illumination are satisfied or
> not the moment an input trigger is used. Ambient light changes alone
> can't change the keyboard backlight illumination and don't restart the
> timer.
>
> Signed-off-by: Gabriele Mazzotta <gabriele.mzt@gmail.com>
> ---
...
> +static ssize_t kbd_led_als_enabled_store(struct device *dev,
> + struct device_attribute *attr,
> + const char *buf, size_t count)
> +{
> + struct kbd_state new_state;
> + struct kbd_state state;
> + bool triggers_enabled = false;
> + int enable;
> + int ret;
> +
> + if (!kbd_als_supported) {
> + pr_warn("ALS mode is not supported\n");
> + return -ENODEV;
Will this sysfs file exist if !kbd_als_supported? If so, can we prevent that?
...
Generally speaking, there is a lot more change here than I would like for an
RC5. I'm going to have to consider this one carefully. If we can't come up with
a simpler fix for this RC series, we may have to revert the previous patch and
target this for 3.20.
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2015-01-18 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 14:05 [PATCH] dell-laptop: use dedicated sysfs file for ALS Gabriele Mazzotta
2015-01-14 14:07 ` Gabriele Mazzotta
2015-01-18 18:08 ` Darren Hart
2015-01-18 18:34 ` Gabriele Mazzotta
2015-01-21 18:38 ` Darren Hart
2015-01-21 22:32 ` Gabriele Mazzotta
2015-01-18 17:52 ` Darren Hart [this message]
2015-02-10 9:36 ` Pali Rohár
2015-02-13 14:30 ` Gabriele Mazzotta
2015-02-18 19:09 ` Pali Rohár
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=20150118175241.GA56582@vmdeb7 \
--to=dvhart@infradead.org \
--cc=A.Sloman@cs.bham.ac.uk \
--cc=computersforpeace@gmail.com \
--cc=gabriele.mzt@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pali.rohar@gmail.com \
--cc=platform-driver-x86@vger.kernel.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