From: Hans de Goede <hdegoede@redhat.com>
To: Jani Nikula <jani.nikula@linux.intel.com>, Aaron Lu <aaron.lu@intel.com>
Cc: Sylvain Pasche <sylvain.pasche@gmail.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
dri-devel@lists.freedesktop.org,
platform-driver-x86@vger.kernel.org, linux-acpi@vger.kernel.org,
Ben Skeggs <bskeggs@redhat.com>
Subject: Re: [PATCH v2] acpi-video: Add a parameter to not register the backlight sysfs interface
Date: Thu, 11 Jun 2015 14:13:55 +0200 [thread overview]
Message-ID: <55797B83.7010903@redhat.com> (raw)
In-Reply-To: <87mw065wls.fsf@intel.com>
Hi,
On 11-06-15 13:10, Jani Nikula wrote:
> On Thu, 11 Jun 2015, Hans de Goede <hdegoede@redhat.com> wrote:
>> Hi,
>>
>> On 11-06-15 03:43, Aaron Lu wrote:
>>> On Tue, Jun 09, 2015 at 11:54:45PM +0200, Hans de Goede wrote:
>>>> Hi,
>>>>
>>>> On 06/09/2015 11:10 AM, Aaron Lu wrote:
>>>>> On Tue, Jun 09, 2015 at 10:32:25AM +0200, Hans de Goede wrote:
>>>>>> On some systems acpi-video backlight is broken in the sense that it cannot
>>>>>> control the brightness of the backlight, but it must still be called on
>>>>>> resume to power-up the backlight after resume.
>>>>>
>>>>> All the video module does on resume is a backlight set operation, it
>>>>> can't control backlight but can turn on the screen on resume? Hmm...
>>>>>
>>>>> I'll ask Sylvain to attach acpidump, let's see if there is anything
>>>>> special there.
>>>>
>>>> Ok, lets see what comes out of that. Note in the mean time Sylvain has
>>>> attached his acpidump.
>>>
>>> Thanks.
>>> According to the discussion in the bugzilla place, it doesn't seem we
>>> have any other way to handle this at the moment.
>>>
>>> Acked-by: Aaron Lu <aaron.lu@intel.com>
>>
>> Thanks. So that only leaves Jani's remark:
>>
>> > Nitpick, I'd prefer positively named variables, like enable_foo to avoid
>> > the double negative !disable_foo. enable_foo and !enable_foo read much
>> > better. But up to Aaron and friends.
>>
>> I personally believe that having the option named disable_backlight_sysfs_if
>> is better here since I believe that things which are always enabled except
>> on a few broken model laptops the option name should be disable_foo so
>> that people can clearly see in /proc/cmdline / dmesg that the user is passing
>> an option to disable something which is normally enabled.
>
> Fair enough.
>
>>
>> As for the (!disabled) argument, the code in question here actually is:
>>
>> if (disabled)
>> return 0;
>>
>> :)
>>
>> Still if people want me to change the option to a default-on
>> enable_backlight_sysfs_if option I can do a v3...
>
> I'm not insisting.
Great, thanks :)
So I'm going to assume this v2 patch is ready for merging then, if anyone
wants me to make any changes please let me know.
Regards,
Hans
next prev parent reply other threads:[~2015-06-11 12:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 8:32 [PATCH v2] acpi-video: Add a parameter to not register the backlight sysfs interface Hans de Goede
2015-06-09 9:10 ` Aaron Lu
2015-06-09 21:54 ` Hans de Goede
2015-06-11 1:43 ` Aaron Lu
2015-06-11 10:13 ` Hans de Goede
2015-06-11 11:10 ` Jani Nikula
2015-06-11 12:13 ` Hans de Goede [this message]
2015-06-15 23:18 ` Rafael J. Wysocki
2015-06-09 14:03 ` Jani Nikula
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=55797B83.7010903@redhat.com \
--to=hdegoede@redhat.com \
--cc=aaron.lu@intel.com \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sylvain.pasche@gmail.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