On Mon, 14.10.13 12:17, Aaron Lu (aaron.lu@xxxxxxxxx) wrote: > > Hmm, regarding your patch series, do you plan to skip the registration > > of the acpi backlight device if the "raw" device is supported? I mean, > > Yes, that's right. > > > the intel driver could be compiled as a module (and generally is on the > > popular distros), so at the time the ACPI subsystem wants to register > > the backlight device and know if a raw backlight device is around it > > never will be, so what is the point of that? Or am I missing something? > > For systems with Intel i915 GPU, ACPI video will wait for GPU driver to > run first, see drivers/acpi/video.c acpi_video_init, the actual > acpi_video_register function is called by i915 driver in > i915_driver_load due to operation region related stuff. Since all > problematic systems reported so far has an Intel GPU, I'm doing it this > way now. If things change, we can enhance it then. Sorry, still not getting this. How should this ever work if the intel video driver is compiled as kmod? That means that it isn't clear at all when the kmod is going to be loaded or if it is loaded at all, you cannot delay the registration of the acpi backlight that long, since the time you'd have to wait is basically unbounded... So, how could this ever work? AFAICS all popular distros ship the video drivers as kernel modules, hence trying to avoid registration of the ACPI backlight if the intel driver is compiled will be an entirely pointless excercise on all distros? What am I missing? Lennart -- Lennart Poettering - Red Hat, Inc. -- 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
