How to backlight_device_register with some kind of "low prior" (for KMS)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

There are some unfunny cases, when ACPI can not be used for
controlling backlight level.

Example can be my Sony VAIO
(http://bugzilla.kernel.org/show_bug.cgi?id=11682) where bl control
doesn't work with sony-laptop. This notebook has ATI GPU that is
responsible for backlight level.

So we have to implement that in radeon module, which has access to
card and can just use register/AtomBIOS to manage backlight. Of course
KMS is perfect place for that.

However we don't want to play with controlling backlight when there is
specific vendor driver for that. Many notebooks are well supported by
sony-laptop (and other modules) and in these cases we don't want to
change that.

Is there some way of detecting if there is vendor-specific driver that
cares backlight? Or can we register bl device with some low priority,
so when acpi module registers with higher, it will be used? Hope you
understand what I mean.

Using anything like
is_backlight_dev_already_registered
is not enought, as we can not be sure which kernel module will be loaded first.

--
Rafał
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux