From: Darren Hart <dvhart@infradead.org>
To: "Marco Trevisan (Treviño)" <mail@3v1n0.net>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
platform-driver-x86@vger.kernel.org,
"Henrique de Moraes Holschuh" <ibm-acpi@hmh.eng.br>
Subject: Re: [PATCH] thinkpad_acpi: save kbdlight state on suspend and restore it on resume
Date: Mon, 23 May 2016 15:09:29 -0700 [thread overview]
Message-ID: <20160523220929.GD2735@f23x64.localdomain> (raw)
In-Reply-To: <CAALaSc=b821TsgB1FZGy9nmP-ZG0jjycdP2ktE1hFZUFg_ACog@mail.gmail.com>
On Fri, May 20, 2016 at 05:03:52AM +0200, Marco Trevisan (Treviño) wrote:
> 2016-05-19 9:52 GMT+02:00 Pali Rohár <pali.rohar@gmail.com>:
> > For me whole patch looks like a big hack because LED_CORE_SUSPENDRESUME
> > does not work correctly... I would rather see fixed support for flag
> > LED_CORE_SUSPENDRESUME, not adding another suspend/resume hook if
> > possible. Any idea?
>
> As I wrote you in private mail I think the only way we have is to keep
> the led_cdev->brightness in sync with actual state. And to do this, we
> can listen the ACPI event, keeping this like a private event that we
> just consume to update led brightness value, without delivering it to
> userspace.
>
> However, the custom code needed for getting this done, is probably way
> more than the one I added here.
> Maybe it could be useful to others to read the brightness level before
> suspending, and in this case we could add a new flag to the led
> subsystem, but not sure it's really worth.
>
At the risk of contributing to "the platform platform", I agree with a local fix
here in the near term. If this becomes a pattern, we can look to move this into
the LED subsystem. As it is, this is working as designed, overriding when
necessary.
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2016-05-23 22:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 1:23 [PATCH] thinkpad_acpi: save kbdlight state on suspend and restore it on resume Marco Trevisan
2016-05-19 7:52 ` Pali Rohár
2016-05-20 3:03 ` Marco Trevisan (Treviño)
2016-05-23 22:09 ` Darren Hart [this message]
2016-05-23 21:57 ` Darren Hart
2016-05-23 22:04 ` Pali Rohár
2016-05-23 22:10 ` Marco Trevisan (Treviño)
2016-05-23 22:21 ` Darren Hart
2016-05-23 22:08 ` Marco Trevisan (Treviño)
2016-05-23 22:20 ` Darren Hart
2016-05-24 15:27 ` Henrique de Moraes Holschuh
2016-05-23 22:39 ` [PATCH v2] " Marco Trevisan
2016-05-24 15:49 ` Darren Hart
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=20160523220929.GD2735@f23x64.localdomain \
--to=dvhart@infradead.org \
--cc=ibm-acpi@hmh.eng.br \
--cc=mail@3v1n0.net \
--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