From: Aaron Lu <aaron.lu@intel.com>
To: Hans de Goede <hdegoede@redhat.com>, Lee Chun-Yi <jlee@suse.com>
Cc: Zhang Rui <rui.zhang@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: [RFC 1/3] acpi-video: Add an acpi_video_unregister_backlight function
Date: Thu, 15 May 2014 09:48:23 +0800 [thread overview]
Message-ID: <53741CE7.402@intel.com> (raw)
In-Reply-To: <53733281.6060707@redhat.com>
On 05/14/2014 05:08 PM, Hans de Goede wrote:
> Hi,
>
> On 05/13/2014 05:11 PM, Aaron Lu wrote:
>> On 05/13/2014 02:03 AM, Hans de Goede wrote:
>>> -static int acpi_video_bus_register_backlight(struct acpi_video_bus *video)
>>> +static void acpi_video_bus_register_backlight(struct acpi_video_bus *video)
>>> {
>>> struct acpi_video_device *dev;
>>>
>>> @@ -1851,10 +1851,6 @@ static int acpi_video_bus_register_backlight(struct acpi_video_bus *video)
>>> list_for_each_entry(dev, &video->video_device_list, entry)
>>> acpi_video_dev_register_backlight(dev);
>>> mutex_unlock(&video->device_list_lock);
>>> -
>>> - video->pm_nb.notifier_call = acpi_video_resume;
>>> - video->pm_nb.priority = 0;
>>> - return register_pm_notifier(&video->pm_nb);
>>
>> Hmm, I don't understand this. The pm notifier is used to restore
>> backlight level on system resume, so should be there when we have
>> created the backlight interface and gone when we unregistered the
>> backlight interface. It doesn't have anything to do with hotkey
>> processing.
>
> A valid point, I did things this way because I wanted the new
> acpi_video_unregister_backlight to result in the same behavior as
> having set the acpi_video=vendor / called acpi_video_dmi_promote_vendor()
> before acpi_video_register runs.
>
> So this means undoing what-ever acpi_video_register() does, which it
> would not have done if acpi_video_dmi_promote_vendor() came first.
>
> If you look at the current code (so without this patch) then
> the pm notifier gets installed unconditionally by
> acpi_video_bus_register_backlight() which gets called unconditionally
> by acpi_video_bus_add(). So even with acpi_video=vendor it still gets
> installed.
>
> acpi_video=vendor / acpi_video_dmi_promote_vendor() influences
> acpi_video_backlight_support() which only gets called by
> acpi_video_verify_backlight_support() which only gets called by
> acpi_video_dev_register_backlight(). So acpi_video=vendor only causes
> the backlight devices to not register, the pm notifier will still be
> installed. My intend was to behave the same independent of module
> loading / init order hence I moved the pm notifier install / uninstall
> to keep the pm notifier installed when calling the new
> acpi_video_unregister_backlight().
>
> Looking at the code you're right that this is not really sensible, since
> the acpi_video_resume call done by the notifier will be a nop when there
> are no backlight devices registered.
>
> So I can split this patch into 2 patches, 1 to not install the pm notifier
> if we're not going to register backlight devices anyways, and a 2nd patch
> adding the new acpi_video_unregister_backlight().
>
> Does that sound like a plan ?
Yes, sounds great, thanks!
-Aaron
next prev parent reply other threads:[~2014-05-15 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 18:03 [RFC 0/3] Add acpi_video_unregister_backlight and use it in acer-wmi Hans de Goede
2014-05-12 18:03 ` [RFC 1/3] acpi-video: Add an acpi_video_unregister_backlight function Hans de Goede
2014-05-13 15:11 ` Aaron Lu
2014-05-14 9:08 ` Hans de Goede
2014-05-15 1:48 ` Aaron Lu [this message]
2014-05-12 18:03 ` [RFC 2/3] acer-wmi: Switch to acpi_video_unregister_backlight Hans de Goede
2014-05-12 18:03 ` [RFC 3/3] acer-wmi: Add Aspire 5741 to video_vendor_dmi_table Hans de Goede
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=53741CE7.402@intel.com \
--to=aaron.lu@intel.com \
--cc=hdegoede@redhat.com \
--cc=jlee@suse.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.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 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.