From: Jani Nikula <jani.nikula@linux.intel.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
Harry Wentland <harry.wentland@amd.com>,
Hamza Mahfooz <hamza.mahfooz@amd.com>,
amd-gfx@lists.freedesktop.org
Cc: "Leo Li" <sunpeng.li@amd.com>,
"Rodrigo Siqueira" <Rodrigo.Siqueira@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Alex Hung" <alex.hung@amd.com>,
"Srinivasan Shanmugam" <srinivasan.shanmugam@amd.com>,
"Wayne Lin" <wayne.lin@amd.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] drm/amd/display: add panel_power_savings sysfs entry to eDP connectors
Date: Fri, 16 Feb 2024 10:58:14 +0200 [thread overview]
Message-ID: <87mss04wgp.fsf@intel.com> (raw)
In-Reply-To: <a1d2749b-8db5-46d1-bf60-7820902cfc8f@amd.com>
On Thu, 15 Feb 2024, Mario Limonciello <mario.limonciello@amd.com> wrote:
> I feel the solution to these concerns is that we should make a knob that
> controls whether the DRM property is created or the sysfs file is
> created but not let them happen simultaneously.
*insert the eyeballs emoji here*
I mean no matter what the problem is, this sounds like the solution is
worse than the problem!
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-02-16 8:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 15:28 [PATCH v2] drm/amd/display: add panel_power_savings sysfs entry to eDP connectors Hamza Mahfooz
2024-02-02 16:20 ` Mario Limonciello
2024-02-15 17:54 ` Harry Wentland
2024-02-15 18:15 ` Mario Limonciello
2024-02-16 8:58 ` Jani Nikula [this message]
2024-02-16 8:19 ` Pekka Paalanen
2024-02-16 13:43 ` Hamza Mahfooz
2024-02-16 14:00 ` Hamza Mahfooz
2024-02-16 14:33 ` Harry Wentland
2024-02-16 15:42 ` Pekka Paalanen
2024-02-16 16:11 ` Harry Wentland
2024-02-16 16:13 ` Harry Wentland
2024-02-16 16:32 ` Mario Limonciello
2024-02-19 9:05 ` Pekka Paalanen
2024-02-16 10:29 ` Christian König
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=87mss04wgp.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alex.hung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamza.mahfooz@amd.com \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=srinivasan.shanmugam@amd.com \
--cc=sunpeng.li@amd.com \
--cc=wayne.lin@amd.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