From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Dave Airlie <airlied@redhat.com>,
intel-gfx@lists.freedesktop.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [Intel-gfx] [PATCH 06/11] drm/i915: migrate skl planes code new file (v3)
Date: Thu, 14 Jan 2021 17:56:55 +0200 [thread overview]
Message-ID: <YABpx599AISB4xD0@intel.com> (raw)
In-Reply-To: <9b51add03de3ffce8a1e9dd59ede79e4e1134c89.1610622609.git.jani.nikula@intel.com>
On Thu, Jan 14, 2021 at 01:13:50PM +0200, Jani Nikula wrote:
> From: Dave Airlie <airlied@redhat.com>
>
> Rework the plane init calls to do the gen test one level higher.
>
> Rework some of the plane helpers so they can live in new file,
> there is still some scope to clean up the plane/fb interactions
> later.
>
> v2: drop atomic code back, rename file to Ville suggestions,
> add header file.
> v3: move scaler bits back
>
> Signed-off-by: Dave Airlie <airlied@redhat.com>
> [Jani: fixed up sparse warnings.]
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> Reported-by: kernel test robot <lkp@intel.com>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
<snip>
> -unsigned int
> -intel_plane_fence_y_offset(const struct intel_plane_state *plane_state)
> -{
> - int x = 0, y = 0;
> -
> - intel_plane_adjust_aligned_offset(&x, &y, plane_state, 0,
> - plane_state->color_plane[0].offset, 0);
> -
> - return y;
> -}
This getting moved around is messing up the diff.
<snip>
> @@ -4386,15 +3633,6 @@ static int skl_update_scaler_plane(struct intel_crtc_state *crtc_state,
> return 0;
> }
>
> -void skl_scaler_disable(const struct intel_crtc_state *old_crtc_state)
> -{
> - struct intel_crtc *crtc = to_intel_crtc(old_crtc_state->uapi.crtc);
> - int i;
> -
> - for (i = 0; i < crtc->num_scalers; i++)
> - skl_detach_scaler(crtc, i);
> -}
Same here.
<snip>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> index f76e2c2a83b8..8e4b6647752f 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp_mst.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> @@ -39,6 +39,7 @@
> #include "intel_dp_mst.h"
> #include "intel_dpio_phy.h"
> #include "intel_hdcp.h"
> +#include "skl_universal_plane.h"
Why is this here?
>
> static int intel_dp_mst_compute_link_config(struct intel_encoder *encoder,
> struct intel_crtc_state *crtc_state,
> diff --git a/drivers/gpu/drm/i915/display/intel_psr.c b/drivers/gpu/drm/i915/display/intel_psr.c
> index c24ae69426cf..0d0b0d3c52a1 100644
> --- a/drivers/gpu/drm/i915/display/intel_psr.c
> +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> @@ -31,6 +31,7 @@
> #include "intel_psr.h"
> #include "intel_sprite.h"
> #include "intel_hdmi.h"
> +#include "skl_universal_plane.h"
Is this due to the psr damage stuff?
<snip>
> diff --git a/drivers/gpu/drm/i915/display/vlv_dsi.c b/drivers/gpu/drm/i915/display/vlv_dsi.c
> index f94025ec603a..ebf266457518 100644
> --- a/drivers/gpu/drm/i915/display/vlv_dsi.c
> +++ b/drivers/gpu/drm/i915/display/vlv_dsi.c
> @@ -38,6 +38,7 @@
> #include "intel_fifo_underrun.h"
> #include "intel_panel.h"
> #include "intel_sideband.h"
> +#include "skl_universal_plane.h"
Why do we need this here?
>
> /* return pixels in terms of txbyteclkhs */
> static u16 txbyteclkhs(u16 pixels, int bpp, int lane_count,
> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> index bbc73df7f753..bc40ecc17a52 100644
> --- a/drivers/gpu/drm/i915/intel_pm.c
> +++ b/drivers/gpu/drm/i915/intel_pm.c
> @@ -38,6 +38,7 @@
> #include "display/intel_display_types.h"
> #include "display/intel_fbc.h"
> #include "display/intel_sprite.h"
> +#include "display/skl_universal_plane.h"
>
> #include "gt/intel_llc.h"
>
> --
> 2.20.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
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:[~2021-01-14 15:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 11:13 [Intel-gfx] [PATCH 00/11] [rfc v7.1] rebased refactor of intel_display Jani Nikula
2021-01-14 11:13 ` [Intel-gfx] [PATCH 01/11] drm/i915: refactor some crtc code out of intel display. (v2) Jani Nikula
2021-01-14 11:13 ` [Intel-gfx] [PATCH 02/11] drm/i915: refactor pll code out into intel_dpll.c Jani Nikula
2021-01-14 11:13 ` [Intel-gfx] [PATCH 03/11] drm/i915: split fdi code out from intel_display.c Jani Nikula
2021-01-15 22:23 ` Jani Nikula
2021-01-14 11:13 ` [Intel-gfx] [PATCH 04/11] drm/i915: refactor ddi translations into a separate file Jani Nikula
2021-01-14 15:41 ` Ville Syrjälä
2021-01-14 11:13 ` [Intel-gfx] [PATCH 05/11] drm/i915: migrate hsw fdi code to new file Jani Nikula
2021-01-14 15:45 ` Ville Syrjälä
2021-01-14 11:13 ` [Intel-gfx] [PATCH 06/11] drm/i915: migrate skl planes code new file (v3) Jani Nikula
2021-01-14 15:56 ` Ville Syrjälä [this message]
2021-01-21 3:37 ` Dave Airlie
2021-01-14 11:13 ` [Intel-gfx] [PATCH 07/11] drm/i915: move pipe update code into crtc Jani Nikula
2021-01-14 11:13 ` [Intel-gfx] [PATCH 08/11] drm/i915: split fb scalable checks into g4x and skl versions Jani Nikula
2021-01-14 11:13 ` [Intel-gfx] [PATCH 09/11] drm/i915: move is_ccs_modifier to an inline Jani Nikula
2021-01-14 15:58 ` Ville Syrjälä
2021-01-14 11:13 ` [Intel-gfx] [PATCH 10/11] drm/i915: migrate pll enable/disable code to intel_dpll.[ch] Jani Nikula
2021-01-14 15:59 ` Ville Syrjälä
2021-01-14 11:13 ` [Intel-gfx] [PATCH 11/11] drm/i915: migrate i9xx plane get config Jani Nikula
2021-01-14 16:00 ` Ville Syrjälä
2021-01-14 13:43 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for rebased refactor of intel_display Patchwork
2021-01-14 13:45 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-01-14 14:13 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-01-15 13:51 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for rebased refactor of intel_display (rev2) Patchwork
2021-01-15 13:52 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-01-15 14:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-01-15 19:27 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2021-01-14 9:05 [Intel-gfx] [rfc v7] rebased refactor of intel_display Dave Airlie
2021-01-14 9:05 ` [Intel-gfx] [PATCH 06/11] drm/i915: migrate skl planes code new file (v3) Dave Airlie
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=YABpx599AISB4xD0@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=airlied@redhat.com \
--cc=dan.carpenter@oracle.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 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.