From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Jasper St. Pierre" <jstpierre@mecheye.net>,
Alex Deucher <alexdeucher@gmail.com>
Cc: "Hans de Goede" <hdegoede@redhat.com>,
"Martin Gräßlin" <mgraesslin@kde.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: KMS backlight ABI proposition
Date: Wed, 22 Feb 2017 16:00:06 +0200 [thread overview]
Message-ID: <87vas2iavt.fsf@intel.com> (raw)
In-Reply-To: <CAA0H+QQFanCA4E-P+HPZe3OpEcL8sE6frDzY=deGUpLACC25fg@mail.gmail.com>
On Tue, 21 Feb 2017, "Jasper St. Pierre" <jstpierre@mecheye.net> wrote:
> Instead of normalizing to 100, I think we should expose a max level, and
> specify that's max brightness. Every single step in the range should have a
> visible difference in output lumens.
The drivers can't guarantee that.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-02-22 14:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 12:58 KMS backlight ABI proposition Martin Peres
2017-02-20 12:46 ` Martin Peres
2017-02-20 14:11 ` Daniel Thompson
2017-02-22 15:05 ` Jani Nikula
2017-02-22 15:18 ` Martin Peres
2017-02-22 16:20 ` Hans de Goede
2017-02-23 8:55 ` Jani Nikula
2017-02-23 13:44 ` Hans de Goede
2017-02-20 16:25 ` Thierry Reding
2017-02-22 15:38 ` Jani Nikula
2017-02-20 19:27 ` Dave Airlie
2017-02-20 19:57 ` Hans de Goede
2017-02-22 15:08 ` Martin Peres
2017-02-20 22:40 ` Alex Deucher
2017-02-20 23:01 ` Jasper St. Pierre
2017-02-22 14:00 ` Jani Nikula [this message]
2017-02-22 16:35 ` Jasper St. Pierre
2017-02-22 15:48 ` Jani Nikula
2017-02-20 20:09 ` Hans de Goede
2017-02-22 14:14 ` Jani Nikula
2017-02-22 19:07 ` Stéphane Marchesin
2017-02-23 8:40 ` Jani Nikula
2017-02-23 13:38 ` Hans de Goede
2017-02-23 17:31 ` Stéphane Marchesin
2017-02-24 8:43 ` Jani Nikula
2017-02-24 8:55 ` Hans de Goede
2017-02-24 9:34 ` Jani Nikula
2017-02-24 9:46 ` Hans de Goede
2017-02-24 9:48 ` Hans de Goede
2017-02-24 9:59 ` Hans de Goede
2017-02-24 10:23 ` Martin Peres
2017-02-24 10:44 ` Hans de Goede
2017-02-24 12:56 ` Martin Peres
2017-02-24 11:16 ` Daniel Thompson
2017-02-24 11:41 ` Jani Nikula
2017-02-23 17:41 ` Jasper St. Pierre
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=87vas2iavt.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=jstpierre@mecheye.net \
--cc=mgraesslin@kde.org \
/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