From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Jingoo Han <jg1.han@samsung.com>
Cc: "'Kyungmin Park'" <kmpark@infradead.org>,
"'Henrique de Moraes Holschuh'" <ibm-acpi@hmh.eng.br>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kay@vrfy.org, "'Richard Purdie'" <rpurdie@rpsys.net>,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] video: backlight: Remove backlight sysfs uevent
Date: Mon, 11 Nov 2013 22:56:28 -0200 [thread overview]
Message-ID: <20131112005628.GA2914@khazad-dum.debian.net> (raw)
In-Reply-To: <002901cedf3c$a7e77a00$f7b66e00$%han@samsung.com>
On Tue, 12 Nov 2013, Jingoo Han wrote:
> On Tuesday, November 12, 2013 8:57 AM, Kyungmin Park wrote:
> > From: Kyungmin Park <kyungmin.park@samsung.com>
> >
> > The most mobile phones have Ambient Light Sensors and it changes brightness according lux.
> > It means it changes backlight brightness frequently by just writing sysfs node, so it generates uevent.
> >
> > Usually there's no user to use this backlight changes. But it forks udev worker threads and it takes
> > about 5ms. The main problem is that it hurts other process activities. so remove it.
> >
> > Kay said
> > "Uevents are for the major, low-frequent, global device state-changes,
> > not for carrying-out any sort of measurement data. Subsystems which
> > need that should use other facilities like poll()-able sysfs file or
> > any other subscription-based, client-tracking interface which does not
> > cause overhead if it isn't used. Uevents are not the right thing to
> > use here, and upstream udev should not paper-over broken kernel
> > subsystems."
True.
Now, let's take a look at reality: should you poll()/select() on a sysfs
node that doesn't suport it, it will wait until the poll/select timeout
happens (or EINTR happens), and userspace has absolutely NO way to detect
whether a sysfs node has poll/select support.
What happens if the sysfs interface did not provide poll/select support
since day one, but rather added it later? Nobody will use it for a *long*
time, if ever... unless you actually took pains to version the sysfs
interface, and people actually care.
> 'thinkpad_acpi.c' uses the 'BACKLIGHT_UPDATE_SYSFS'.
> Henrique, can we remove it?
Can't you fix this by rate-limiting, or otherwise adding an attribute that
backlight devices should set when they need to supress change events?
Is there a proper on-screen-display support path for the backlight class
nowadays? Otherwise, you'd be removing the only way userspace ever had to
do proper OSD of backlight changes...
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2013-11-12 0:56 UTC|newest]
Thread overview: 19+ 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-12 0:18 ` Jingoo Han
2013-11-12 0:56 ` Henrique de Moraes Holschuh [this message]
2013-11-12 1:07 ` Kyungmin Park
2013-11-12 1:19 ` Kay Sievers
2013-11-12 2:08 ` Kyungmin Park
2013-11-12 2:22 ` Kay Sievers
2013-11-20 23:40 ` Matthew Garrett
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 17:15 ` Matthew Garrett
2013-11-24 0:40 ` [ibm-acpi-devel] " Henrique de Moraes Holschuh
2013-11-24 1:02 ` Matthew Garrett
2013-11-24 3:53 ` Henrique de Moraes Holschuh
2013-12-16 7:53 ` Andrew Morton
2013-12-18 11:27 ` Henrique de Moraes Holschuh
-- strict thread matches above, loose matches on Subject: below --
2013-11-12 0:44 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=20131112005628.GA2914@khazad-dum.debian.net \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox