From: Daniel Vetter <daniel@ffwll.ch>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: Anthony Wong <anthony.wong@canonical.com>,
dri-devel@lists.freedesktop.org,
Mario Limonciello <mario.limonciello@dell.com>
Subject: Re: OLED panel brightness support
Date: Wed, 24 Jul 2019 13:48:51 +0200 [thread overview]
Message-ID: <20190724114851.GY15868@phenom.ffwll.local> (raw)
In-Reply-To: <28D3097A-5295-4445-BD73-1A338EFA546D@canonical.com>
On Tue, Jul 23, 2019 at 06:46:55PM +0800, Kai-Heng Feng wrote:
> Hi,
>
> Currently, OLED panel brightness [1] is not supported.
> We have a similar Dell system that also affect by lack of OLED brightness
> support.
>
> I’ve investigated both kernel and user space but I haven’t found a good
> general solution yet.
> Dell systems use EDID descriptor 4 as Dell specific descriptor, which
> reports its panel type and we can know it’s an OLED panel or not.
>
> My initial thought is to add a new attribute “oled" in drm_sysfs.c [2] to
> let userspace like clutter [3] to control the brightness.
> However other DEs may need to implement their own OLED brightness support
> which isn’t ideal.
>
> So I’d like to know if there’s any good way to support OLED brightness in
> good old backlight sysfs, to let userspace keep to the current interface.
>
> [1] https://bugs.freedesktop.org/show_bug.cgi?id=97883
> [2] https://pastebin.ubuntu.com/p/QYrRBppVT9/
> [3] https://gitlab.gnome.org/GNOME/clutter/blob/master/clutter/clutter-brightness-contrast-effect.c#L559
I think the Most Proper Solution would be to integrate the backlight
support into drm, by adding the backlight knobs as kms properties to the
correct connector. This would fix a whole bag of issue:
- no more ill-defined magic for userspace to find the right backlight
- we could have well-defined semantics what happens with the backlight
across a kms modeset
- issues like this could be solved with a small helper and a bit of code
in the kernel (there's also other DDC knobs to control backlight, which
we also don't really expose in a consistent way).
Downside is how to roll this out in a backward compatible way, without
breaking the world:
- fbcon/fbdev needs to be taught to not do it's own backlight wrangling
for kms drivers which handle backlight natively
- we might need an opt-in magic for this, if it turns out that the kms
driver handling the backlight breaks stuff
- userspace ofc needs to fall back to its current pile of hacks if the
backlight stuff isn't supported natively.
Adding more ill-defined sysfs files, or more magice ordering rules, or
anything else like that doesn't sound too appealing.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-07-24 11:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 10:46 OLED panel brightness support Kai-Heng Feng
2019-07-24 11:48 ` Daniel Vetter [this message]
[not found] ` <30f693a33f5a45ce84673fd8d7cecc7a@AUSX13MPC105.AMER.DELL.COM>
2019-07-25 7:35 ` Kai-Heng Feng
2019-07-25 11:59 ` Daniel Vetter
2019-07-25 13:12 ` Sam Ravnborg
2019-07-25 14:02 ` Daniel Vetter
2019-07-25 14:24 ` Sam Ravnborg
2019-07-29 8:34 ` Jani Nikula
2019-07-29 8:26 ` Jani Nikula
2019-07-29 8:43 ` Kai-Heng Feng
2019-07-29 9:19 ` 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=20190724114851.GY15868@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=anthony.wong@canonical.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kai.heng.feng@canonical.com \
--cc=mario.limonciello@dell.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