Hi On Thu, Sep 11, 2014 at 8:48 AM, Daniel Vetter <daniel@xxxxxxxx> wrote: > Nice you skid around all the pitfalls and trapdoors, I guess we've all > been rather blind ;-) > > Two high-level comments: > - We also want to forward "bl_power". cros was totally not happy when we > stopped treating brightness == 0 as completely off (it upsets some > panels terminally, so there's a vbt lower limit). Instead we expose this > now through the bl_power knob. > > While at it I think we should expose all the other backlight properties > too (read-only ofc for actual/max_brightness). bl_power is easy to add. I guess v2 will have: "BACKLIGHT-POWER" (range 0-4) actual-brightness is a bit more tricky. Currently, DRM caches property values, so there is no read_property() hook. We'd have to add this. But it'll be quite nasty as we have to call into the backlight driver. So I think we want to run an async-interruptible worker on the backlight, drop the locks in the ioctl and wait for the job to finish. Not sure whether it's worth it.. maybe we can add this later. > - How does udev match on the drm connector name? They are not terribly > stable atm, and if you reload your drm driver, or much more likely, have > two gpus with two drm drivers they change. We probably should change the > name allocation scheme to be per device instance instead of global > first. Within a driver probe order is hopefully deterministic on a given > platform, since even with super dynamic setups (based on dt/acpi) the > firmware tables should change really. You can match on EDID attributes. Ok, so far this is pretty ugly as the EDID property is binary. But we can add rather trivial udev extensions to make EDID binary against text matching possible. While we're at it, I don't really like the brightness-value re-scaling. I currently expose BRIGHTNESS as rang 0-65535 and scale it to the backlight range. This works perfectly well as the backlight is usually a really small range, but it would be much simpler if we could expose the real range. However, this would require DRM property hotplugging. This is currently not supported by DRM.. and it would require multiple different properties for each connector as each might have a different range. But then, we have to suffix the name as we cannot have multiple properties with the same name.. Eh.. re-scaling doesn't sound that bad, does it? Ok, we could expose a separate property called MAX-BRIGHTNESS and drivers simply ignore the range-bounds of the BRIGHTNESS value and use MAX-BRIGHTNESS instead? Sounds ok'ish. Thanks David _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
