From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Sebastian Wick <sebastian.wick@redhat.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
wayland <wayland-devel@lists.freedesktop.org>
Subject: Re: Meeting (BOF) at Plumbers Dublin to discuss backlight brightness as connector object property RFC?
Date: Fri, 9 Sep 2022 15:05:15 +0300 [thread overview]
Message-ID: <Yxsr+11xH7n92p4e@intel.com> (raw)
In-Reply-To: <c796e05d-6c74-3011-89d3-226e54455f06@redhat.com>
On Fri, Sep 09, 2022 at 12:23:53PM +0200, Hans de Goede wrote:
> Hi All,
>
> I will be at Plumbers Dublin next week and I was wondering if
> anyone interested in this wants to get together for a quick
> discussion / birds of a feather session about this?
>
> I have just posted version 2 of the RFC:
> https://lore.kernel.org/dri-devel/b61d3eeb-6213-afac-2e70-7b9791c86d2e@redhat.com/T/#u
>
> If you are interested in meeting up please send me
> an email off-list (no need to spam the list further with this)
> also please let me know if there are any times which do not
> work for you, and/or times which have your preference.
>
> I don't have a specific room/time for this yet, but if people
> are interested I will try to get a room from the organization
> and if that does not work out I'm sure we will figure something
> out.
>
> One of the things which I would like to discuss is using
> the backlight brightness as connector object property vs
> external (not part of the compositor) tools to control the
> brightness like e.g. xbacklight, quoting from the RFC:
>
> "people using
> non fully integrated desktop environments like e.g. sway often use custom
> scripts binded to hotkeys to get functionality like the brightness
> up/down keyboard hotkeys changing the brightness. This typically involves
> e.g. the xbacklight utility.
>
> Even if the xbacklight utility is ported to use kms with the new connector
> object brightness properties then this still will not work because
> changing the properties will require drm-master rights and e.g. sway will
> already hold those."
>
> Note one obvious solution here would be for these use-cases to keep
> using the old /sys/class/backlight interface for this, with the downside
> that we will then be stuck to that interface for ever...
Isn't xbacklight the thing that only works when you *have* the
backlight property? Ie. currently only works on intel ddx which
adds a custom property but doesn't work on modesetting ddx for
example.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2022-09-09 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 10:23 Meeting (BOF) at Plumbers Dublin to discuss backlight brightness as connector object property RFC? Hans de Goede
2022-09-09 11:50 ` Simon Ser
2022-09-09 14:36 ` Daniel Stone
2022-09-09 12:05 ` Ville Syrjälä [this message]
2022-09-11 9:24 ` Hans de Goede
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=Yxsr+11xH7n92p4e@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=sebastian.wick@redhat.com \
--cc=wayland-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.