Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Alex Hung <alex.hung@amd.com>,
	dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Cc: Leo Li <sunpeng.li@amd.com>,
	Harry Wentland <harry.wentland@amd.com>,
	intel-gfx@lists.freedesktop.org,
	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
	Daniel Wheeler <daniel.wheeler@amd.com>,
	Hersen Wu <hersenxs.wu@amd.com>, Daniel Vetter <daniel@ffwll.ch>,
	Wenchieh Chien <wenchieh.chien@amd.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	David Airlie <airlied@gmail.com>
Subject: Re: [Intel-gfx] [PATCH 0/4] drm/amd/display: stop using drm_edid_override_connector_update()
Date: Tue, 29 Aug 2023 13:48:30 +0300	[thread overview]
Message-ID: <871qfm2kg1.fsf@intel.com> (raw)
In-Reply-To: <87il965gob.fsf@intel.com>

On Wed, 23 Aug 2023, Jani Nikula <jani.nikula@intel.com> wrote:
> On Tue, 22 Aug 2023, Alex Hung <alex.hung@amd.com> wrote:
>> On 2023-08-22 06:01, Jani Nikula wrote:
>>> Over the past years I've been trying to unify the override and firmware
>>> EDID handling as well as EDID property updates. It won't work if drivers
>>> do their own random things.
>> Let's check how to replace these references by appropriate ones or fork 
>> the function as reverting these patches causes regressions.
>
> I think the fundamental problem you have is conflating connector forcing
> with EDID override. They're orthogonal. The .force callback has no
> business basing the decisions on connector->edid_override. Force is
> force, override is override.
>
> The driver isn't even supposed to know or care if the EDID originates
> from the firmware loader or override EDID debugfs. drm_get_edid() will
> handle that for you transparently. It'll return the EDID, and you
> shouldn't look at connector->edid_blob_ptr either. Using that will make
> future work in drm_edid.c harder.
>
> You can't fix that with minor tweaks. I think you'll be better off
> starting from scratch.
>
> Also, connector->edid_override is debugfs. You actually can change the
> behaviour. If your userspace, whatever it is, has been written to assume
> connector forcing if EDID override is set, you *do* have to fix that,
> and set both.

Any updates on fixing this, or shall we proceed with the reverts?

BR,
Jani.



>
> BR,
> Jani.
>
>
>>
>> Cheers,
>> Alex
>>
>>> 
>>> BR,
>>> Jani.
>>> 
>>> 
>>> Cc: Alex Deucher <alexander.deucher@amd.com>
>>> Cc: Alex Hung <alex.hung@amd.com>
>>> Cc: Chao-kai Wang <Stylon.Wang@amd.com>
>>> Cc: Daniel Wheeler <daniel.wheeler@amd.com>
>>> Cc: Harry Wentland <harry.wentland@amd.com>
>>> Cc: Hersen Wu <hersenxs.wu@amd.com>
>>> Cc: Leo Li <sunpeng.li@amd.com>
>>> Cc: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
>>> Cc: Wenchieh Chien <wenchieh.chien@amd.com>
>>> Cc: David Airlie <airlied@gmail.com>
>>> Cc: Daniel Vetter <daniel@ffwll.ch>
>>> 
>>> Jani Nikula (4):
>>>    Revert "drm/amd/display: drop unused count variable in
>>>      create_eml_sink()"
>>>    Revert "drm/amd/display: assign edid_blob_ptr with edid from debugfs"
>>>    Revert "drm/amd/display: mark amdgpu_dm_connector_funcs_force static"
>>>    Revert "drm/amd/display: implement force function in
>>>      amdgpu_dm_connector_funcs"
>>> 
>>>   .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 44 +++----------------
>>>   1 file changed, 5 insertions(+), 39 deletions(-)
>>> 

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2023-08-29 10:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 12:01 [Intel-gfx] [PATCH 0/4] drm/amd/display: stop using drm_edid_override_connector_update() Jani Nikula
2023-08-22 12:01 ` [Intel-gfx] [PATCH 1/4] Revert "drm/amd/display: drop unused count variable in create_eml_sink()" Jani Nikula
2023-08-22 12:01 ` [Intel-gfx] [PATCH 2/4] Revert "drm/amd/display: assign edid_blob_ptr with edid from debugfs" Jani Nikula
2023-08-22 12:01 ` [Intel-gfx] [PATCH 3/4] Revert "drm/amd/display: mark amdgpu_dm_connector_funcs_force static" Jani Nikula
2023-08-22 12:01 ` [Intel-gfx] [PATCH 4/4] Revert "drm/amd/display: implement force function in amdgpu_dm_connector_funcs" Jani Nikula
2023-08-22 12:06   ` Jani Nikula
2023-08-22 13:22 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/amd/display: stop using drm_edid_override_connector_update() Patchwork
2023-08-22 13:22 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-22 13:35 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-08-22 19:38 ` [Intel-gfx] [PATCH 0/4] " Alex Hung
2023-08-23  8:03   ` Jani Nikula
2023-08-29 10:48     ` Jani Nikula [this message]
2023-08-29 15:29       ` Wu, Hersen
2023-08-29 15:44       ` Alex Deucher
2023-08-29 16:01         ` Wu, Hersen
2023-08-29 16:20         ` Jani Nikula
2023-08-29 17:03           ` Jani Nikula
2023-08-29 18:53             ` Alex Hung
2023-08-30  7:29               ` Jani Nikula
2023-08-30  9:42                 ` Daniel Vetter
2023-08-31 22:01                 ` Alex Hung
2023-09-01 12:27                   ` Jani Nikula
2023-09-01 19:00                   ` Alex Deucher
2023-09-04  7:57                     ` Daniel Vetter
2023-08-23  1:14 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/amd/display: stop using drm_edid_override_connector_update() (rev2) Patchwork
2023-08-23  1:14 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-23  1:32 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-08-23 10:43 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork

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=871qfm2kg1.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=Rodrigo.Siqueira@amd.com \
    --cc=airlied@gmail.com \
    --cc=alex.hung@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=daniel.wheeler@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=hersenxs.wu@amd.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sunpeng.li@amd.com \
    --cc=wenchieh.chien@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