From: Jani Nikula <jani.nikula@linux.intel.com>
To: Xaver Hugl <xaver.hugl@gmail.com>,
Mario Limonciello <mario.limonciello@amd.com>
Cc: Leo Li <sunpeng.li@amd.com>,
amd-gfx@lists.freedesktop.org, Simon Ser <contact@emersion.fr>,
Harry Wentland <Harry.Wentland@amd.com>,
dri-devel@lists.freedesktop.org, Sean Paul <seanpaul@google.com>
Subject: Re: [PATCH v3 2/2] drm/amd: Add power_saving_policy drm property to eDP connectors
Date: Thu, 01 Aug 2024 15:33:40 +0300 [thread overview]
Message-ID: <87wml0v2vv.fsf@intel.com> (raw)
In-Reply-To: <CAFZQkGz8DeoiVX2MohoBoTMxraJk1Ou41N_wKP3GkqRrPg_6sg@mail.gmail.com>
On Mon, 01 Jul 2024, Xaver Hugl <xaver.hugl@gmail.com> wrote:
> Am Do., 20. Juni 2024 um 22:22 Uhr schrieb Xaver Hugl <xaver.hugl@gmail.com>:
>> Merging can only happen once a real world userspace application has
>> implemented support for it. I'll try to do that sometime next week in
>> KWin
>
> Here's the promised implementation:
> https://invent.kde.org/plasma/kwin/-/merge_requests/6028
The requirement is that the userspace patches must be reviewed and ready
for merging into a suitable and canonical upstream project.
Are they?
BR,
Jani.
>
> In testing with the patches on top of kernel 6.9.6, setting the
> property to `Require color accuracy` makes the sysfs file correctly
> report "Device or resource busy" when trying to change the power
> saving level, but setting the property to zero doesn't really work.
> Once KWin sets the property to zero, changing the power saving level
> "works" but the screen blanks for a moment (might just be a single
> frame) and reading from the file returns zero again, with the visuals
> and backlight level unchanged as well.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-08-01 12:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 2:04 [PATCH v3 0/2] Add support for 'power saving policy' property Mario Limonciello
2024-06-06 2:04 ` [PATCH v3 1/2] drm: Introduce 'power saving policy' drm property Mario Limonciello
2024-06-06 2:04 ` [PATCH v3 2/2] drm/amd: Add power_saving_policy drm property to eDP connectors Mario Limonciello
2024-06-18 22:36 ` Leo Li
2024-06-19 4:08 ` Mario Limonciello
2024-06-20 20:22 ` Xaver Hugl
2024-07-01 18:47 ` Xaver Hugl
2024-07-01 19:02 ` Mario Limonciello
2024-07-01 22:34 ` Xaver Hugl
2024-07-02 19:19 ` Mario Limonciello
2024-08-01 12:33 ` Jani Nikula [this message]
2024-08-01 12:43 ` Thomas Zimmermann
2024-08-01 12:56 ` Jani Nikula
2024-08-02 12:49 ` Xaver Hugl
2024-08-02 13:28 ` Sebastian Wick
2024-08-02 14:37 ` Harry Wentland
2024-08-02 16:22 ` Sebastian Wick
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=87wml0v2vv.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Harry.Wentland@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=mario.limonciello@amd.com \
--cc=seanpaul@google.com \
--cc=sunpeng.li@amd.com \
--cc=xaver.hugl@gmail.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 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.