On Wed, Oct 26, 2022 at 11:59:28AM +0200, Hans de Goede wrote:
> Ok, so this is a local customization to what is already a custom BIOS
> for a custom motherboard. There is a lot of custom in that sentence and
> TBH at some point things might become too custom for them to be expected
> to work OOTB.
But it *did* work OOTB before. You broke it. I accept that I'm a
ludicrously weird corner case here, but there are going to be other
systems that are also affected by this.
> I'm afraid things are not that simple. I assume that with
> "if ACPI backlight control is expected to work" you mean don't
> use ACPI backlight control when (acpi_osi_is_win8() && native_available)
> evaluates to true because it is known to be broken on some of
> those systems because Windows 8 stopped using it ?
Correct.
> Unfortunately something similar applies to vendor interfaces,
> When Windows XP started using (and mandating for certification
> IIRC) ACPI backlight control, vendors still kept their own
> vendor specific EC/smbios/ACPI/WMI backlight interfaces around for
> a long long time, except they were often no longer tested.
The current situation (both before your patchset and with its current
implementation) is that vendor is preferred to native, so if the vendor
interface is present then we're already using it.
> > The
> > problem you're dealing with is that the knowledge of whether or not
> > there's a vendor interface isn't something the core kernel code knows
> > about. What you're proposing here is effectively for us to expose
> > additional information about whether or not there's a vendor interface
> > in the system firmware, but since we're talking in some cases about
> > hardware that's almost 20 years old, we're not realistically going to
> > get those old machines fixed.
>
> I don't understand why you keep talking about the old vendor interfaces,
> at least for the chromebook part of this thread the issue is that
> the i915 driver no longer registers the intel_backlight device which
> is a native device type, which is caused by the patch this email
> thread is about (and old vendor interfaces do not come into play
> at all here). So AFAICT this is a native vs acpi backlight control
> issue ?
I'm referring to your proposed patch that changed the default from
backlight_vendor to backlight_native, which would fix my machine and
Chromebooks but break anything that relies on the vendor interfaces.
> I really want to resolve your bug, but I still lack a lot of info,
> like what backlight interface you were actually using in 6.0 ?
Native.
> {
> .callback = video_detect_force_video,
> /* ThinkPad X201s */
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> DMI_MATCH(DMI_PRODUCT_VERSION, "ThinkPad X201s"),
> },
> },
>
> will trigger.
In this case you'd break anyone else running the system who isn't using
the hacked EC and different ACPI tables - obviously there's ways round
this, but realistically since I'm (as far as I know) the only person in
this situation it makes more sense for me to add a kernel parameter than
carry around an exceedingly niche DMI quirk. I'm fine with that. But the
point I'm trying to make is that the machines *are* telling you whether
they'd prefer vendor or native, and you're not taking that into account
in the video_detect code.
