From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: James Simmons <jsimmons@infradead.org>
Cc: Richard Purdie <rpurdie@rpsys.net>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
paulus@samba.org, Lennart Poettering <mzxreary@0pointer.de>,
Andriy Skulysh <askulysh@image.kiev.ua>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, Antonino Daplas <adaplas@pol.net>,
Holger Macht <hmacht@suse.de>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH] backlight: do not power off backlight when unregistering
Date: Tue, 21 Nov 2006 01:01:46 -0200 [thread overview]
Message-ID: <20061121030146.GA31304@khazad-dum.debian.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0611201928310.17639@pentafluge.infradead.org>
On Mon, 20 Nov 2006, James Simmons wrote:
> > The following in-tree (latest linux-2.6 git tree) drivers are desktop/laptop
> > devices and likely do not want the "dim and power off backlight on
> > backlight_device_unregister" behavior:
> >
> > drivers/video/aty/*
> > drivers/video/riva/fbdev.c
> > drivers/video/nvidia/nv_backlight.c
> > drivers/misc/msi-laptop.c
>
> ...
>
> > I have CC'ed the relevant people (please forgive me any ommissions) for the
> > drivers listed above, so they can chime in if their driver should retain the
> > "dim and power off backlight on backlight_device_unregister" behaviour.
>
> Hm. In the case of some drivers the hardware state on x86 is set back to
> text mode in some cases. So do we in that case dim the backlight?
I would very much *hate* that happening on any x86 box of mine. I won't
presume I understand enough of the usage pattern on weird devices, and it
would make some sense to power off the display if you are removing the
*only* way to talk to the video device (but I still think this is naively
assuming the local admin don't want to just leave the display as-is).
But as you said yourself, in regular desktop/laptops (at least x86 ones)
textmode is there, and works just fine, so killing the display on module
removal is wrong IMO.
--
"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
prev parent reply other threads:[~2006-11-21 3:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 22:54 [PATCH] backlight: do not power off backlight when unregistering Henrique de Moraes Holschuh
2006-11-06 0:36 ` Richard Purdie
2006-11-06 1:26 ` Henrique de Moraes Holschuh
2006-11-10 0:08 ` Henrique de Moraes Holschuh
2006-11-10 0:32 ` [PATCH] backlight: do not power off backlight when unregistering (try 2) Henrique de Moraes Holschuh
2006-11-10 10:44 ` Richard Purdie
2006-11-20 19:31 ` [PATCH] backlight: do not power off backlight when unregistering James Simmons
2006-11-21 3:01 ` Henrique de Moraes Holschuh [this message]
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=20061121030146.GA31304@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=adaplas@pol.net \
--cc=askulysh@image.kiev.ua \
--cc=benh@kernel.crashing.org \
--cc=hmacht@suse.de \
--cc=jsimmons@infradead.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mzxreary@0pointer.de \
--cc=paulus@samba.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