mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Igor Gnatenko <i.gnatenko.brain@gmail.com>
To: Aaron Lu <aaron.lu@intel.com>
Cc: ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Matthew Garrett <matthew.garrett@nebula.com>,
	Seth Forshee <seth.forshee@canonical.com>,
	"Lee, Chun-Yi" <joeyli.kernel@gmail.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Len Brown <lenb@kernel.org>,
	Yves-Alexis Perez <corsac@debian.org>,
	Felipe Contreras <felipe.contreras@gmail.com>,
	Lee Chun-Yi <jlee@novell.com>,
	Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Subject: Re: [PATCH 1/2] ACPI / video: seperate backlight control and event interface
Date: Tue, 10 Sep 2013 09:23:43 +0400	[thread overview]
Message-ID: <1378790623.2160.2.camel@ThinkPad-X230.localdomain> (raw)
In-Reply-To: <522D8991.5070707@intel.com>


On Mon, 2013-09-09 at 16:40 +0800, Aaron Lu wrote:
> The backlight control and event delivery functionality provided by ACPI
> video module is mixed together and registered all during video device
> enumeration time. As a result, the two functionality are also removed
> together on module unload time or by the acpi_video_unregister function.
> The two functionalities are actually independent and one may be useful
> while the other one may be broken, so it is desirable to seperate the
> two functionalities such that it is clear and easy to disable one
> functionality without affecting the other one. This patch does the
> seperation and as a result, a new video_bus_head list is introduced to
> store all registered video bus structure and a new function
> acpi_video_unregister_backlight is introduced to unregister backlight
> interfaces for all video devices belonging to stored video buses.
> 
> Currently, there is no need to unregister ACPI video's event delivery
> functionality alone so the function acpi_video_remove_notify_handler is
> not introduced, it can be easily added when needed.
> 
> Signed-off-by: Aaron Lu <aaron.lu@intel.com>
Tested-by: Igor Gnatenko <i.gnatenko.brain@gmail.com>
> ---
>  drivers/acpi/video.c | 451 ++++++++++++++++++++++++++++++---------------------
>  include/acpi/video.h |   2 +
>  2 files changed, 264 insertions(+), 189 deletions(-)

-- 
Igor Gnatenko
Fedora release 20 (Heisenbug)
Linux 3.11.0-3.fc20.x86_64

-- 
Igor Gnatenko
Fedora release 20 (Heisenbug)
Linux 3.11.0-1.fc20.x86_64


  reply	other threads:[~2013-09-10  5:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-09  8:37 [PATCH 0/2] Rework ACPI video driver Aaron Lu
2013-09-09  8:40 ` [PATCH 1/2] ACPI / video: seperate backlight control and event interface Aaron Lu
2013-09-10  5:23   ` Igor Gnatenko [this message]
2013-09-09  8:42 ` [PATCH 2/2] ACPI / video / i915: Remove ACPI backlight if firmware expects Windows 8 Aaron Lu
2013-09-09  9:32   ` Daniel Vetter
2013-09-09 12:16     ` Rafael J. Wysocki
2013-09-09 15:21       ` Daniel Vetter
2013-09-09 15:38         ` Matthew Garrett
2013-09-09 20:23         ` Rafael J. Wysocki
2013-09-10 13:53           ` Jani Nikula
2013-09-10 13:56             ` Matthew Garrett
2013-09-10 14:21               ` Jani Nikula
2013-09-10 14:21                 ` Matthew Garrett
2013-09-10 19:23             ` Rafael J. Wysocki
2013-09-11  1:32               ` Aaron Lu
2013-09-11  8:45                 ` Jani Nikula
2013-09-11  8:45                   ` Matthew Garrett
2013-09-11  9:09                     ` Yves-Alexis Perez
2013-09-11 10:29                     ` Jani Nikula
2013-09-11 10:30                       ` Matthew Garrett
2013-09-12  2:26                   ` Aaron Lu
2013-09-10  6:30     ` Aaron Lu
2013-09-09 11:44   ` Igor Gnatenko
2013-09-10  3:27     ` Aaron Lu
2013-09-10  5:13       ` Igor Gnatenko
2013-09-10  5:16         ` Aaron Lu
2013-09-10  5:22           ` Igor Gnatenko
2013-09-10  5:42             ` Aaron Lu
2013-09-10  5:23   ` Igor Gnatenko

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=1378790623.2160.2.camel@ThinkPad-X230.localdomain \
    --to=i.gnatenko.brain@gmail.com \
    --cc=aaron.lu@intel.com \
    --cc=corsac@debian.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=felipe.contreras@gmail.com \
    --cc=hmh@hmh.eng.br \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jlee@novell.com \
    --cc=joeyli.kernel@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.garrett@nebula.com \
    --cc=rjw@sisk.pl \
    --cc=seth.forshee@canonical.com \
    /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

all inboxes | Powered by JetHome®