From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: linux-fbdev@vger.kernel.org,
'Kyungmin Park' <kmpark@infradead.org>,
kay@vrfy.org, Jingoo Han <jg1.han@samsung.com>,
'Henrique de Moraes Holschuh' <ibm-acpi@hmh.eng.br>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
ibm-acpi-devel@lists.sourceforge.net,
'Richard Purdie' <rpurdie@rpsys.net>
Subject: Re: [ibm-acpi-devel] [PATCH] video: backlight: Remove backlight sysfs uevent
Date: Sun, 24 Nov 2013 01:02:57 +0000 [thread overview]
Message-ID: <20131124010257.GA6376@srcf.ucam.org> (raw)
In-Reply-To: <20131124004015.GA19499@khazad-dum.debian.net>
On Sat, Nov 23, 2013 at 10:40:15PM -0200, Henrique de Moraes Holschuh wrote:
> On Fri, 22 Nov 2013, Matthew Garrett wrote:
> > We have userspace that relies on uevents of type
> > BACKLIGHT_UPDATE_HOTKEY. I don't know that we have userspace that relies
> > on uevents of type BACKLIGHT_UPDATE_SYSFS.
>
> Any OSD application would have to rely on both uevent types, or it is broken
> (and to test that, just write a level to sysfs and watch the OSD app fail to
> tell you about the backlight level change...)
Right, OSDs are supposed to respond to keypresses, not arbitrary changes
of backlight. If the user's just echoed 8 into brightness, they know
they set the brightness to 8 - they don't need an OSD to tell them that.
BACKLIGHT_UPDATE_HOTKEY is when the firmware itself has changed the
brightness in response to a keypress, and so reporting the keypress
would result in additional backlight changes.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2013-11-24 1:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 23:57 [PATCH] video: backlight: Remove backlight sysfs uevent Kyungmin Park
2013-11-11 23:57 ` Kyungmin Park
2013-11-12 0:18 ` Jingoo Han
2013-11-12 0:18 ` Jingoo Han
2013-11-12 0:56 ` Henrique de Moraes Holschuh
2013-11-12 0:56 ` Henrique de Moraes Holschuh
2013-11-12 1:07 ` Kyungmin Park
2013-11-12 1:07 ` Kyungmin Park
2013-11-12 1:19 ` Kay Sievers
2013-11-12 1:19 ` Kay Sievers
2013-11-12 2:08 ` Kyungmin Park
2013-11-12 2:08 ` Kyungmin Park
2013-11-12 2:22 ` Kay Sievers
2013-11-12 2:22 ` Kay Sievers
2013-11-20 23:40 ` Matthew Garrett
2013-11-20 23:40 ` Matthew Garrett
2013-11-21 11:43 ` Henrique de Moraes Holschuh
2013-11-21 11:43 ` Henrique de Moraes Holschuh
2013-11-21 14:33 ` Matthew Garrett
2013-11-22 11:36 ` Henrique de Moraes Holschuh
2013-11-22 11:36 ` Henrique de Moraes Holschuh
2013-11-22 17:15 ` Matthew Garrett
2013-11-24 0:40 ` [ibm-acpi-devel] " Henrique de Moraes Holschuh
2013-11-24 0:40 ` Henrique de Moraes Holschuh
2013-11-24 1:02 ` Matthew Garrett [this message]
2013-11-24 3:53 ` Henrique de Moraes Holschuh
2013-11-24 3:53 ` Henrique de Moraes Holschuh
2013-12-16 7:53 ` Andrew Morton
2013-12-16 7:53 ` Andrew Morton
2013-12-18 11:27 ` Henrique de Moraes Holschuh
2013-11-12 0:44 ` Kyungmin Park
2013-11-12 0:44 ` Kyungmin Park
2013-11-12 0:54 ` Kyungmin Park
2013-11-12 0:54 ` Kyungmin Park
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=20131124010257.GA6376@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ibm-acpi@hmh.eng.br \
--cc=jg1.han@samsung.com \
--cc=kay@vrfy.org \
--cc=kmpark@infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.