From: Paz Zcharya <pazz@chromium.org>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, Andrzej Hajda <andrzej.hajda@intel.com>
Subject: Re: [PATCH v3 12/16] drm/i915: Simplify intel_initial_plane_config() calling convention
Date: Tue, 30 Jan 2024 23:24:01 +0000 [thread overview]
Message-ID: <ZbmFEeZbNTihhxon@google.com> (raw)
In-Reply-To: <20240116075636.6121-13-ville.syrjala@linux.intel.com>
On Tue, Jan 16, 2024 at 09:56:32AM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> There's no reason the caller of intel_initial_plane_config() should
> have to loop over the CRTCs. Pull the loop into the function to
> make life simpler for the caller.
>
> Cc: Paz Zcharya <pazz@chromium.org>
> Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Hi Ville,
Thank you so much for this incredible series.
It solves the issue regarding MTL initial plane readout
that Andrzej Hajda and I worked on in
https://patchwork.freedesktop.org/patch/570811/?series=127130&rev=2
In addition, it solved the issue with the new GOP.
I tested it on two different devices with Meteor Lake and it worked perfectly:
no i915 errors, no flickers or observable issues.
Tested-by: Paz Zcharya <pazz@chromium.org>
> ---
> .../drm/i915/display/intel_display_driver.c | 7 +---
> .../drm/i915/display/intel_plane_initial.c | 40 +++++++++++--------
> .../drm/i915/display/intel_plane_initial.h | 4 +-
> 3 files changed, 26 insertions(+), 25 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_driver.c b/drivers/gpu/drm/i915/display/intel_display_driver.c
> index ecf9cb74734b..f3fe1743243b 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_driver.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_driver.c
> @@ -415,7 +415,6 @@ int intel_display_driver_probe_nogem(struct drm_i915_private *i915)
> {
> struct drm_device *dev = &i915->drm;
> enum pipe pipe;
> - struct intel_crtc *crtc;
> int ret;
>
> if (!HAS_DISPLAY(i915))
> @@ -467,11 +466,7 @@ int intel_display_driver_probe_nogem(struct drm_i915_private *i915)
> intel_acpi_assign_connector_fwnodes(i915);
> drm_modeset_unlock_all(dev);
>
> - for_each_intel_crtc(dev, crtc) {
> - if (!to_intel_crtc_state(crtc->base.state)->uapi.active)
> - continue;
> - intel_crtc_initial_plane_config(crtc);
> - }
> + intel_initial_plane_config(i915);
>
> /*
> * Make sure hardware watermarks really match the state we read out.
> diff --git a/drivers/gpu/drm/i915/display/intel_plane_initial.c b/drivers/gpu/drm/i915/display/intel_plane_initial.c
> index 78bff6181ceb..b7e12b60d68b 100644
> --- a/drivers/gpu/drm/i915/display/intel_plane_initial.c
> +++ b/drivers/gpu/drm/i915/display/intel_plane_initial.c
> @@ -357,25 +357,31 @@ static void plane_config_fini(struct intel_initial_plane_config *plane_config)
> i915_vma_put(plane_config->vma);
> }
>
> -void intel_crtc_initial_plane_config(struct intel_crtc *crtc)
> +void intel_initial_plane_config(struct drm_i915_private *i915)
> {
> - struct drm_i915_private *dev_priv = to_i915(crtc->base.dev);
> - struct intel_initial_plane_config plane_config = {};
> + struct intel_crtc *crtc;
>
> - /*
> - * Note that reserving the BIOS fb up front prevents us
> - * from stuffing other stolen allocations like the ring
> - * on top. This prevents some ugliness at boot time, and
> - * can even allow for smooth boot transitions if the BIOS
> - * fb is large enough for the active pipe configuration.
> - */
> - dev_priv->display.funcs.display->get_initial_plane_config(crtc, &plane_config);
> + for_each_intel_crtc(&i915->drm, crtc) {
> + struct intel_initial_plane_config plane_config = {};
>
> - /*
> - * If the fb is shared between multiple heads, we'll
> - * just get the first one.
> - */
> - intel_find_initial_plane_obj(crtc, &plane_config);
> + if (!to_intel_crtc_state(crtc->base.state)->uapi.active)
> + continue;
>
> - plane_config_fini(&plane_config);
> + /*
> + * Note that reserving the BIOS fb up front prevents us
> + * from stuffing other stolen allocations like the ring
> + * on top. This prevents some ugliness at boot time, and
> + * can even allow for smooth boot transitions if the BIOS
> + * fb is large enough for the active pipe configuration.
> + */
> + i915->display.funcs.display->get_initial_plane_config(crtc, &plane_config);
> +
> + /*
> + * If the fb is shared between multiple heads, we'll
> + * just get the first one.
> + */
> + intel_find_initial_plane_obj(crtc, &plane_config);
> +
> + plane_config_fini(&plane_config);
> + }
> }
> diff --git a/drivers/gpu/drm/i915/display/intel_plane_initial.h b/drivers/gpu/drm/i915/display/intel_plane_initial.h
> index c7e35ab3182b..64ab95239cd4 100644
> --- a/drivers/gpu/drm/i915/display/intel_plane_initial.h
> +++ b/drivers/gpu/drm/i915/display/intel_plane_initial.h
> @@ -6,8 +6,8 @@
> #ifndef __INTEL_PLANE_INITIAL_H__
> #define __INTEL_PLANE_INITIAL_H__
>
> -struct intel_crtc;
> +struct drm_i915_private;
>
> -void intel_crtc_initial_plane_config(struct intel_crtc *crtc);
> +void intel_initial_plane_config(struct drm_i915_private *i915);
>
> #endif
> --
> 2.41.0
>
next prev parent reply other threads:[~2024-01-30 23:25 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 7:56 [PATCH v3 00/16] drm/i915: (stolen) memory region related fixes Ville Syrjala
2024-01-16 7:56 ` [PATCH v3 01/16] drm/i915: Use struct resource for memory region IO as well Ville Syrjala
2024-01-16 10:23 ` Nirmoy Das
2024-01-30 23:15 ` Paz Zcharya
2024-01-16 7:56 ` [PATCH v3 02/16] drm/i915: Print memory region info during probe Ville Syrjala
2024-01-16 10:20 ` Nirmoy Das
2024-01-30 23:16 ` Paz Zcharya
2024-01-16 7:56 ` [PATCH v3 03/16] drm/i915: Remove ad-hoc lmem/stolen debugs Ville Syrjala
2024-01-16 10:23 ` Nirmoy Das
2024-01-30 23:17 ` Paz Zcharya
2024-01-16 7:56 ` [PATCH v3 04/16] drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access Ville Syrjala
2024-01-16 10:31 ` Nirmoy Das
2024-01-25 10:27 ` [PATCH v4 " Ville Syrjala
2024-01-30 23:19 ` Paz Zcharya
2024-01-16 7:56 ` [PATCH v3 05/16] drm/i915: Disable the "binder" Ville Syrjala
2024-01-16 10:32 ` Nirmoy Das
2024-01-17 14:13 ` Michał Winiarski
2024-01-17 17:46 ` Nirmoy Das
2024-01-18 23:12 ` Ville Syrjälä
2024-01-19 10:47 ` Nirmoy Das
2024-01-19 10:49 ` Nirmoy Das
2024-01-25 9:08 ` Ville Syrjälä
2024-01-25 14:59 ` Michał Winiarski
2024-01-31 11:33 ` Ville Syrjälä
2024-01-25 10:27 ` [PATCH v4 " Ville Syrjala
2024-01-30 23:20 ` Paz Zcharya
2024-01-16 7:56 ` [PATCH v3 06/16] drm/i915: Rename the DSM/GSM registers Ville Syrjala
2024-01-16 10:45 ` Nirmoy Das
2024-01-25 10:28 ` [PATCH v4 " Ville Syrjala
2024-01-30 23:20 ` Paz Zcharya
2024-01-16 7:56 ` [PATCH v3 07/16] drm/i915: Fix PTE decode during initial plane readout Ville Syrjala
2024-01-16 10:46 ` Nirmoy Das
2024-01-30 23:21 ` Paz Zcharya
2024-01-16 7:56 ` [PATCH v3 08/16] drm/i915: Fix region start " Ville Syrjala
2024-01-22 15:07 ` Shankar, Uma
2024-01-30 23:21 ` Paz Zcharya
2024-01-16 7:56 ` [PATCH v3 09/16] drm/i915: Fix MTL " Ville Syrjala
2024-01-22 15:09 ` Shankar, Uma
2024-01-30 23:22 ` Paz Zcharya
2024-01-16 7:56 ` [PATCH v3 10/16] drm/i915: s/phys_base/dma_addr/ Ville Syrjala
2024-01-30 23:22 ` Paz Zcharya
2024-01-16 7:56 ` [PATCH v3 11/16] drm/i915: Split the smem and lmem plane readout apart Ville Syrjala
2024-01-30 23:23 ` Paz Zcharya
2024-01-16 7:56 ` [PATCH v3 12/16] drm/i915: Simplify intel_initial_plane_config() calling convention Ville Syrjala
2024-01-28 4:18 ` kernel test robot
2024-01-30 23:24 ` Paz Zcharya [this message]
2024-02-02 15:14 ` Jani Nikula
2024-02-02 16:12 ` Ville Syrjälä
2024-02-02 16:15 ` Jani Nikula
2024-02-02 23:58 ` kernel test robot
2024-01-16 7:56 ` [PATCH v3 13/16] drm/i915/fbdev: Fix smem_start for LMEMBAR stolen objects Ville Syrjala
2024-01-30 23:25 ` Paz Zcharya
2024-01-16 7:56 ` [PATCH v3 14/16] drm/i915: Tweak BIOS fb reuse check Ville Syrjala
2024-01-30 23:26 ` Paz Zcharya
2024-01-16 7:56 ` [PATCH v3 15/16] drm/i915: Try to relocate the BIOS fb to the start of ggtt Ville Syrjala
2024-01-30 23:27 ` Paz Zcharya
2024-01-16 7:56 ` [PATCH v3 16/16] drm/i915: Annotate more of the BIOS fb takeover failure paths Ville Syrjala
2024-01-22 15:12 ` Shankar, Uma
2024-01-30 23:27 ` Paz Zcharya
2024-01-16 9:02 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: (stolen) memory region related fixes (rev6) Patchwork
2024-01-16 9:02 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-01-16 9:21 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-01-17 16:23 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: (stolen) memory region related fixes (rev7) Patchwork
2024-01-17 16:23 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-01-17 16:40 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-01-25 12:00 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: (stolen) memory region related fixes (rev10) Patchwork
2024-01-25 12:00 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-01-25 12:02 ` ✓ Fi.CI.BAT: success " Patchwork
2024-01-25 14:39 ` ✗ Fi.CI.IGT: failure " 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=ZbmFEeZbNTihhxon@google.com \
--to=pazz@chromium.org \
--cc=andrzej.hajda@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;
as well as URLs for NNTP newsgroup(s).