public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 00/16] drm/edid: EDID override refactoring and fixes
Date: Wed, 26 Oct 2022 11:33:34 +0300	[thread overview]
Message-ID: <87zgdjc7c1.fsf@intel.com> (raw)
In-Reply-To: <cover.1666614699.git.jani.nikula@intel.com>

On Mon, 24 Oct 2022, Jani Nikula <jani.nikula@intel.com> wrote:
> v2 of drm/edid: EDID override refactoring and fixes
>
> Address review comments, add patch 15.

Thanks for the reviews, pushed the series to drm-misc-next.

BR,
Jani.


>
> BR,
> Jani.
>
>
> Jani Nikula (16):
>   drm/i915/hdmi: do dual mode detect only if connected
>   drm/i915/hdmi: stop using connector->override_edid
>   drm/amd/display: stop using connector->override_edid
>   drm/edid: debug log EDID override set/reset
>   drm/edid: abstract debugfs override EDID show better
>   drm/edid: rename drm_add_override_edid_modes() to
>     drm_edid_override_connector_update()
>   drm/edid: split drm_edid block count helper
>   drm/edid: add function for checking drm_edid validity
>   drm/edid: detach debugfs EDID override from EDID property update
>   drm/edid/firmware: drop redundant connector_name variable/parameter
>   drm/edid/firmware: rename drm_load_edid_firmware() to
>     drm_edid_load_firmware()
>   drm/edid: use struct drm_edid for override/firmware EDID
>   drm/edid: move edid load declarations to internal header
>   drm/edid/firmware: convert to drm device specific logging
>   drm/edid: add [CONNECTOR:%d:%s] to debug logging
>   drm/edid: convert to device specific logging
>
>  .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c |   3 -
>  drivers/gpu/drm/drm_connector.c               |   1 +
>  drivers/gpu/drm/drm_crtc_internal.h           |  15 +-
>  drivers/gpu/drm/drm_debugfs.c                 |   8 +-
>  drivers/gpu/drm/drm_edid.c                    | 346 +++++++++++-------
>  drivers/gpu/drm/drm_edid_load.c               | 109 ++----
>  drivers/gpu/drm/drm_probe_helper.c            |   2 +-
>  drivers/gpu/drm/i915/display/intel_hdmi.c     |  20 +-
>  include/drm/drm_connector.h                   |  16 +-
>  include/drm/drm_edid.h                        |  10 +-
>  10 files changed, 283 insertions(+), 247 deletions(-)

-- 
Jani Nikula, Intel Open Source Graphics Center

      parent reply	other threads:[~2022-10-26  8:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 12:33 [Intel-gfx] [PATCH v2 00/16] drm/edid: EDID override refactoring and fixes Jani Nikula
2022-10-24 12:33 ` [Intel-gfx] [PATCH v2 01/16] drm/i915/hdmi: do dual mode detect only if connected Jani Nikula
2022-10-24 12:33 ` [Intel-gfx] [PATCH v2 02/16] drm/i915/hdmi: stop using connector->override_edid Jani Nikula
2022-10-24 15:13   ` Ville Syrjälä
2022-10-24 12:33 ` [Intel-gfx] [PATCH v2 03/16] drm/amd/display: " Jani Nikula
2022-10-24 12:33 ` [Intel-gfx] [PATCH v2 04/16] drm/edid: debug log EDID override set/reset Jani Nikula
2022-10-24 12:33 ` [Intel-gfx] [PATCH v2 05/16] drm/edid: abstract debugfs override EDID show better Jani Nikula
2022-10-24 12:33 ` [Intel-gfx] [PATCH v2 06/16] drm/edid: rename drm_add_override_edid_modes() to drm_edid_override_connector_update() Jani Nikula
2022-10-24 12:33 ` [Intel-gfx] [PATCH v2 07/16] drm/edid: split drm_edid block count helper Jani Nikula
2022-10-24 12:33 ` [Intel-gfx] [PATCH v2 08/16] drm/edid: add function for checking drm_edid validity Jani Nikula
2022-10-24 12:33 ` [Intel-gfx] [PATCH v2 09/16] drm/edid: detach debugfs EDID override from EDID property update Jani Nikula
2022-10-24 17:53   ` Ville Syrjälä
2022-10-24 12:33 ` [Intel-gfx] [PATCH v2 10/16] drm/edid/firmware: drop redundant connector_name variable/parameter Jani Nikula
2022-10-24 12:33 ` [Intel-gfx] [PATCH v2 11/16] drm/edid/firmware: rename drm_load_edid_firmware() to drm_edid_load_firmware() Jani Nikula
2022-10-24 12:33 ` [Intel-gfx] [PATCH v2 12/16] drm/edid: use struct drm_edid for override/firmware EDID Jani Nikula
2022-10-24 12:33 ` [Intel-gfx] [PATCH v2 13/16] drm/edid: move edid load declarations to internal header Jani Nikula
2022-10-24 12:33 ` [Intel-gfx] [PATCH v2 14/16] drm/edid/firmware: convert to drm device specific logging Jani Nikula
2022-10-24 16:00   ` Ville Syrjälä
2022-10-24 12:33 ` [Intel-gfx] [PATCH v2 15/16] drm/edid: add [CONNECTOR:%d:%s] to debug logging Jani Nikula
2022-10-24 13:27   ` Simon Ser
2022-10-24 12:33 ` [Intel-gfx] [PATCH v2 16/16] drm/edid: convert to device specific logging Jani Nikula
2022-10-24 16:02   ` Ville Syrjälä
2022-10-24 14:43 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/edid: EDID override refactoring and fixes (rev2) Patchwork
2022-10-24 14:43 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-10-24 15:05 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-10-25 12:35 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/edid: EDID override refactoring and fixes (rev3) Patchwork
2022-10-25 12:57 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-25 18:25 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-10-26  8:33 ` Jani Nikula [this message]

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=87zgdjc7c1.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox