Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/bios: debug log ddi port info after parsing
Date: Thu, 30 Jun 2022 15:06:02 +0300	[thread overview]
Message-ID: <8735fmpd91.fsf@intel.com> (raw)
In-Reply-To: <YrTEUxR3lEiBBYhY@intel.com>

On Thu, 23 Jun 2022, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Thu, Jun 23, 2022 at 08:04:54PM +0300, Jani Nikula wrote:
>> On Thu, 23 Jun 2022, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
>> > On Tue, Jun 21, 2022 at 03:37:32PM +0300, Jani Nikula wrote:
>> >> The ddc pin and aux channel sanitization may disable DVI/HDMI and DP,
>> >> respectively, of ports parsed earlier, in "last one wins" fashion. With
>> >> parsing and printing interleaved, we'll end up logging support first and
>> >> disabling later anyway.
>> >> 
>> >> Now that we've split ddi port info parsing and printing, take it further
>> >> by doing the printing in a separate loop, fixing the logging.
>> >> 
>> >> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> >> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> >
>> > Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> 
>> Just realized this also changes the printing order from VBT child device
>> order to port number order. Is that a bug or a feature?
>
> I suppose it doesn't really matter. The only things where the order
> really matters are conflicts and we should still get some extra debug
> spew for those right?

Correct.

Pushed to din, thanks for the review.

BR,
Jani.



>
>> 
>> BR,
>> Jani.
>> 
>> >
>> >> ---
>> >>  drivers/gpu/drm/i915/display/intel_bios.c | 8 ++++++--
>> >>  1 file changed, 6 insertions(+), 2 deletions(-)
>> >> 
>> >> diff --git a/drivers/gpu/drm/i915/display/intel_bios.c b/drivers/gpu/drm/i915/display/intel_bios.c
>> >> index ab23324c0402..51dde5bfd956 100644
>> >> --- a/drivers/gpu/drm/i915/display/intel_bios.c
>> >> +++ b/drivers/gpu/drm/i915/display/intel_bios.c
>> >> @@ -2670,8 +2670,6 @@ static void parse_ddi_port(struct intel_bios_encoder_data *devdata)
>> >>  
>> >>  	sanitize_device_type(devdata, port);
>> >>  
>> >> -	print_ddi_port(devdata, port);
>> >> -
>> >>  	if (intel_bios_encoder_supports_dvi(devdata))
>> >>  		sanitize_ddc_pin(devdata, port);
>> >>  
>> >> @@ -2689,12 +2687,18 @@ static bool has_ddi_port_info(struct drm_i915_private *i915)
>> >>  static void parse_ddi_ports(struct drm_i915_private *i915)
>> >>  {
>> >>  	struct intel_bios_encoder_data *devdata;
>> >> +	enum port port;
>> >>  
>> >>  	if (!has_ddi_port_info(i915))
>> >>  		return;
>> >>  
>> >>  	list_for_each_entry(devdata, &i915->vbt.display_devices, node)
>> >>  		parse_ddi_port(devdata);
>> >> +
>> >> +	for_each_port(port) {
>> >> +		if (i915->vbt.ports[port])
>> >> +			print_ddi_port(i915->vbt.ports[port], port);
>> >> +	}
>> >>  }
>> >>  
>> >>  static void
>> >> -- 
>> >> 2.30.2
>> 
>> -- 
>> Jani Nikula, Intel Open Source Graphics Center

-- 
Jani Nikula, Intel Open Source Graphics Center

      reply	other threads:[~2022-06-30 12:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21 12:37 [Intel-gfx] [PATCH] drm/i915/bios: debug log ddi port info after parsing Jani Nikula
2022-06-21 14:00 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-06-22  0:14 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-06-23  9:25 ` [Intel-gfx] [PATCH] " Ville Syrjälä
2022-06-23 17:04   ` Jani Nikula
2022-06-23 19:51     ` Ville Syrjälä
2022-06-30 12:06       ` 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=8735fmpd91.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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