Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "Nikula, Jani" <jani.nikula@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/debugfs: stop using edid_blob_ptr
Date: Wed, 7 Jun 2023 08:25:53 +0000	[thread overview]
Message-ID: <5a1ad448df6cd5540103d68c76db7fb7bde56c79.camel@intel.com> (raw)
In-Reply-To: <20230602132321.3199445-1-jani.nikula@intel.com>

On Fri, 2023-06-02 at 16:23 +0300, Jani Nikula wrote:
> Only the EDID code and sysfs should look at the EDID property. Stop
> using it.

Reviewed-by: Jouni Högander <jouni.hogander@intel.com>

> 
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_display_debugfs.c | 12 ++++++----
> --
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> index 2a4df62692a6..165e2c7e3126 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> @@ -6,6 +6,7 @@
>  #include <linux/string_helpers.h>
>  
>  #include <drm/drm_debugfs.h>
> +#include <drm/drm_edid.h>
>  #include <drm/drm_fourcc.h>
>  
>  #include "hsw_ips.h"
> @@ -228,19 +229,18 @@ static void intel_hdcp_info(struct seq_file *m,
>         seq_puts(m, "\n");
>  }
>  
> -static void intel_dp_info(struct seq_file *m,
> -                         struct intel_connector *intel_connector)
> +static void intel_dp_info(struct seq_file *m, struct intel_connector
> *connector)
>  {
> -       struct intel_encoder *intel_encoder =
> intel_attached_encoder(intel_connector);
> +       struct intel_encoder *intel_encoder =
> intel_attached_encoder(connector);
>         struct intel_dp *intel_dp = enc_to_intel_dp(intel_encoder);
> -       const struct drm_property_blob *edid = intel_connector-
> >base.edid_blob_ptr;
> +       const struct edid *edid = drm_edid_raw(connector-
> >detect_edid);
>  
>         seq_printf(m, "\tDPCD rev: %x\n", intel_dp-
> >dpcd[DP_DPCD_REV]);
>         seq_printf(m, "\taudio support: %s\n",
> -                  str_yes_no(intel_connector-
> >base.display_info.has_audio));
> +                  str_yes_no(connector-
> >base.display_info.has_audio));
>  
>         drm_dp_downstream_debug(m, intel_dp->dpcd, intel_dp-
> >downstream_ports,
> -                               edid ? edid->data : NULL, &intel_dp-
> >aux);
> +                               edid, &intel_dp->aux);
>  }
>  
>  static void intel_dp_mst_info(struct seq_file *m,


  parent reply	other threads:[~2023-06-07  8:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 13:23 [Intel-gfx] [PATCH] drm/i915/debugfs: stop using edid_blob_ptr Jani Nikula
2023-06-02 16:57 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-06-04 23:37 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-06-07  8:25 ` Hogander, Jouni [this message]
2023-06-07 10:20   ` [Intel-gfx] [PATCH] " Jani Nikula

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=5a1ad448df6cd5540103d68c76db7fb7bde56c79.camel@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.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