From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: "drm/i915: Use the correct crtc when sanitizing plane mapping" seems to cause the readback plane state to always be 0
Date: Tue, 20 Nov 2018 13:28:04 +0200 [thread overview]
Message-ID: <20181120112804.GR9144@intel.com> (raw)
In-Reply-To: <1a36a2ab-9d96-a7c3-603c-7dab1fcef697@redhat.com>
On Mon, Nov 19, 2018 at 11:47:00PM +0100, Hans de Goede wrote:
> Hi Ville,
>
> While debugging the briefly purple screen on DSI panels issue for
> which I just send a revert, I also noticed something odd with
> your commit 9b27390139db ("drm/i915: Use the correct crtc when
> sanitizing plane mapping").
>
> When comparing drm.debug=0x1e logs between 4.19 and 4.20-rc1
> I noticed that this bit of the initial hw state readback logging
> in 4.19:
>
> [drm:intel_modeset_setup_hw_state [i915]] pipe B active planes 0x1
> [drm:intel_modeset_setup_hw_state [i915]] pipe B active planes 0x1
> [drm:intel_modeset_setup_hw_state [i915]] pipe B active planes 0x1
> [drm:intel_modeset_setup_hw_state [i915]] pipe B active planes 0x1
>
> Changed to:
>
> [drm:intel_modeset_setup_hw_state [i915]] pipe B active planes 0x0
> [drm:intel_modeset_setup_hw_state [i915]] pipe B active planes 0x0
> [drm:intel_modeset_setup_hw_state [i915]] pipe B active planes 0x0
> [drm:intel_modeset_setup_hw_state [i915]] pipe B active planes 0x0
That debug message is just garbage now. I removed it in the following
commit.
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-11-20 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 22:47 "drm/i915: Use the correct crtc when sanitizing plane mapping" seems to cause the readback plane state to always be 0 Hans de Goede
2018-11-20 11:28 ` Ville Syrjälä [this message]
2018-11-20 12:51 ` Hans de Goede
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=20181120112804.GR9144@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=hdegoede@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.