From: Daniel Vetter <daniel.vetter@ffwll.ch> To: DRI Development <dri-devel@lists.freedesktop.org> Cc: Rob Clark <robdclark@chromium.org>, Rajendra Nayak <rnayak@codeaurora.org>, Daniel Vetter <daniel.vetter@ffwll.ch>, Intel Graphics Development <intel-gfx@lists.freedesktop.org>, Tanmay Shah <tanmay@codeaurora.org>, Jordan Crouse <jordan@cosmicpenguin.net>, Qinglang Miao <miaoqinglang@huawei.com>, Daniel Vetter <daniel.vetter@intel.com>, Kalyan Thota <kalyant@codeaurora.org> Subject: [PATCH 06/12] drm/msm/dpu1: Don't set allow_fb_modifiers explicitly Date: Tue, 13 Apr 2021 11:48:57 +0200 [thread overview] Message-ID: <20210413094904.3736372-6-daniel.vetter@ffwll.ch> (raw) In-Reply-To: <20210413094904.3736372-1-daniel.vetter@ffwll.ch> Since commit 890880ddfdbe256083170866e49c87618b706ac7 Author: Paul Kocialkowski <paul.kocialkowski@bootlin.com> Date: Fri Jan 4 09:56:10 2019 +0100 drm: Auto-set allow_fb_modifiers when given modifiers at plane init this is done automatically as part of plane init, if drivers set the modifier list correctly. Which is the case here. Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> Cc: Rob Clark <robdclark@chromium.org> Cc: Kalyan Thota <kalyant@codeaurora.org> Cc: Jordan Crouse <jordan@cosmicpenguin.net> Cc: Eric Anholt <eric@anholt.net> Cc: Tanmay Shah <tanmay@codeaurora.org> Cc: Rajendra Nayak <rnayak@codeaurora.org> Cc: Jeykumar Sankaran <jsanka@codeaurora.org> Cc: Qinglang Miao <miaoqinglang@huawei.com> --- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 5 ----- 1 file changed, 5 deletions(-) diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c index 85f2c3564c96..074fb37ed49f 100644 --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c @@ -1020,11 +1020,6 @@ static int dpu_kms_hw_init(struct msm_kms *kms) dpu_kms->catalog->caps->max_mixer_width * 2; dev->mode_config.max_height = 4096; - /* - * Support format modifiers for compression etc. - */ - dev->mode_config.allow_fb_modifiers = true; - /* * _dpu_kms_drm_obj_init should create the DRM related objects * i.e. CRTCs, planes, encoders, connectors and so forth -- 2.31.0 _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel.vetter@ffwll.ch> To: DRI Development <dri-devel@lists.freedesktop.org> Cc: Rob Clark <robdclark@chromium.org>, Rajendra Nayak <rnayak@codeaurora.org>, Daniel Vetter <daniel.vetter@ffwll.ch>, Intel Graphics Development <intel-gfx@lists.freedesktop.org>, Tanmay Shah <tanmay@codeaurora.org>, Jordan Crouse <jordan@cosmicpenguin.net>, Eric Anholt <eric@anholt.net>, Qinglang Miao <miaoqinglang@huawei.com>, Daniel Vetter <daniel.vetter@intel.com>, Jeykumar Sankaran <jsanka@codeaurora.org>, Kalyan Thota <kalyant@codeaurora.org> Subject: [Intel-gfx] [PATCH 06/12] drm/msm/dpu1: Don't set allow_fb_modifiers explicitly Date: Tue, 13 Apr 2021 11:48:57 +0200 [thread overview] Message-ID: <20210413094904.3736372-6-daniel.vetter@ffwll.ch> (raw) In-Reply-To: <20210413094904.3736372-1-daniel.vetter@ffwll.ch> Since commit 890880ddfdbe256083170866e49c87618b706ac7 Author: Paul Kocialkowski <paul.kocialkowski@bootlin.com> Date: Fri Jan 4 09:56:10 2019 +0100 drm: Auto-set allow_fb_modifiers when given modifiers at plane init this is done automatically as part of plane init, if drivers set the modifier list correctly. Which is the case here. Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> Cc: Rob Clark <robdclark@chromium.org> Cc: Kalyan Thota <kalyant@codeaurora.org> Cc: Jordan Crouse <jordan@cosmicpenguin.net> Cc: Eric Anholt <eric@anholt.net> Cc: Tanmay Shah <tanmay@codeaurora.org> Cc: Rajendra Nayak <rnayak@codeaurora.org> Cc: Jeykumar Sankaran <jsanka@codeaurora.org> Cc: Qinglang Miao <miaoqinglang@huawei.com> --- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 5 ----- 1 file changed, 5 deletions(-) diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c index 85f2c3564c96..074fb37ed49f 100644 --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c @@ -1020,11 +1020,6 @@ static int dpu_kms_hw_init(struct msm_kms *kms) dpu_kms->catalog->caps->max_mixer_width * 2; dev->mode_config.max_height = 4096; - /* - * Support format modifiers for compression etc. - */ - dev->mode_config.allow_fb_modifiers = true; - /* * _dpu_kms_drm_obj_init should create the DRM related objects * i.e. CRTCs, planes, encoders, connectors and so forth -- 2.31.0 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-04-13 9:49 UTC|newest] Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-13 9:48 [PATCH 01/12] drm/arm: Don't set allow_fb_modifiers explicitly Daniel Vetter 2021-04-13 9:48 ` [Intel-gfx] " Daniel Vetter 2021-04-13 9:48 ` [PATCH 02/12] drm/arm/malidp: Always list modifiers Daniel Vetter 2021-04-13 9:48 ` [Intel-gfx] " Daniel Vetter 2021-04-13 9:48 ` Daniel Vetter 2021-04-13 9:48 ` [PATCH 03/12] drm/exynos: Don't set allow_fb_modifiers explicitly Daniel Vetter 2021-04-13 9:48 ` [Intel-gfx] " Daniel Vetter 2021-04-13 9:48 ` Daniel Vetter 2021-04-13 9:48 ` Daniel Vetter 2021-04-20 6:31 ` Inki Dae 2021-04-20 6:31 ` [Intel-gfx] " Inki Dae 2021-04-20 6:31 ` Inki Dae 2021-04-20 6:31 ` Inki Dae 2021-04-20 8:41 ` Daniel Vetter 2021-04-20 8:41 ` [Intel-gfx] " Daniel Vetter 2021-04-20 8:41 ` Daniel Vetter 2021-04-20 8:41 ` Daniel Vetter 2021-04-13 9:48 ` [PATCH 04/12] drm/i915: " Daniel Vetter 2021-04-13 9:48 ` [Intel-gfx] " Daniel Vetter 2021-04-13 9:48 ` [PATCH 05/12] drm/imx: " Daniel Vetter 2021-04-13 9:48 ` [Intel-gfx] " Daniel Vetter 2021-04-13 9:48 ` Daniel Vetter 2021-04-13 11:47 ` Lucas Stach 2021-04-13 11:47 ` [Intel-gfx] " Lucas Stach 2021-04-13 11:47 ` Lucas Stach 2021-04-13 14:04 ` Daniel Vetter 2021-04-13 14:04 ` [Intel-gfx] " Daniel Vetter 2021-04-13 14:04 ` Daniel Vetter 2021-04-13 14:14 ` Lucas Stach 2021-04-13 14:14 ` [Intel-gfx] " Lucas Stach 2021-04-13 14:14 ` Lucas Stach 2021-04-14 2:24 ` Liu Ying 2021-04-14 2:24 ` [Intel-gfx] " Liu Ying 2021-04-14 2:24 ` Liu Ying 2021-04-14 9:10 ` Daniel Vetter 2021-04-14 9:10 ` [Intel-gfx] " Daniel Vetter 2021-04-14 9:10 ` Daniel Vetter 2021-04-15 11:35 ` Daniel Vetter 2021-04-15 11:35 ` [Intel-gfx] " Daniel Vetter 2021-04-15 11:35 ` Daniel Vetter 2021-04-13 9:48 ` Daniel Vetter [this message] 2021-04-13 9:48 ` [Intel-gfx] [PATCH 06/12] drm/msm/dpu1: " Daniel Vetter 2021-04-13 9:48 ` [PATCH 07/12] drm/msm/mdp4: Fix modifier support enabling Daniel Vetter 2021-04-13 9:48 ` [Intel-gfx] " Daniel Vetter 2021-04-13 9:48 ` Daniel Vetter 2021-04-13 9:48 ` [PATCH 08/12] drm/nouveau: Don't set allow_fb_modifiers explicitly Daniel Vetter 2021-04-13 9:48 ` [Intel-gfx] " Daniel Vetter 2021-04-13 9:48 ` Daniel Vetter 2021-04-13 9:48 ` [Nouveau] " Daniel Vetter 2021-04-13 9:49 ` [PATCH 09/12] drm/stm: " Daniel Vetter 2021-04-13 9:49 ` [Intel-gfx] " Daniel Vetter 2021-04-13 9:49 ` Daniel Vetter 2021-04-13 9:49 ` [PATCH 10/12] drm/tegra: " Daniel Vetter 2021-04-13 9:49 ` [Intel-gfx] " Daniel Vetter 2021-04-13 9:49 ` Daniel Vetter 2021-04-13 11:37 ` Thierry Reding 2021-04-13 11:37 ` [Intel-gfx] " Thierry Reding 2021-04-13 11:37 ` Thierry Reding 2021-04-15 11:33 ` Daniel Vetter 2021-04-15 11:33 ` [Intel-gfx] " Daniel Vetter 2021-04-15 11:33 ` Daniel Vetter 2021-04-13 9:49 ` [PATCH 11/12] drm/vc4: " Daniel Vetter 2021-04-13 9:49 ` [Intel-gfx] " Daniel Vetter 2021-04-14 8:51 ` Maxime Ripard 2021-04-14 8:51 ` [Intel-gfx] " Maxime Ripard 2021-04-13 9:49 ` [PATCH 12/12] drm/modifiers: Enforce consistency between the cap an IN_FORMATS Daniel Vetter 2021-04-13 9:49 ` [Intel-gfx] " Daniel Vetter 2021-04-13 11:54 ` Lucas Stach 2021-04-13 11:54 ` [Intel-gfx] " Lucas Stach 2021-04-13 14:17 ` Daniel Vetter 2021-04-13 14:17 ` [Intel-gfx] " Daniel Vetter 2021-04-13 11:56 ` Pekka Paalanen 2021-04-13 11:56 ` [Intel-gfx] " Pekka Paalanen 2021-04-13 14:11 ` Daniel Vetter 2021-04-13 14:11 ` [Intel-gfx] " Daniel Vetter 2021-04-13 14:19 ` Daniel Vetter 2021-04-13 14:19 ` [Intel-gfx] " Daniel Vetter 2021-04-14 7:45 ` Pekka Paalanen 2021-04-14 7:45 ` [Intel-gfx] " Pekka Paalanen 2021-04-13 15:22 ` Simon Ser 2021-04-13 15:22 ` [Intel-gfx] " Simon Ser 2021-04-14 8:52 ` Maxime Ripard 2021-04-14 8:52 ` [Intel-gfx] " Maxime Ripard 2021-04-14 9:08 ` [PATCH] " Daniel Vetter 2021-04-14 9:08 ` [Intel-gfx] " Daniel Vetter 2021-04-14 12:14 ` Pekka Paalanen 2021-04-14 12:14 ` [Intel-gfx] " Pekka Paalanen 2021-04-16 6:30 ` Simon Ser 2021-04-16 6:30 ` [Intel-gfx] " Simon Ser 2021-04-13 12:10 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/12] drm/arm: Don't set allow_fb_modifiers explicitly Patchwork 2021-04-13 12:17 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork 2021-04-13 12:38 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2021-04-13 14:24 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork 2021-04-14 12:24 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [01/12] drm/arm: Don't set allow_fb_modifiers explicitly (rev2) 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=20210413094904.3736372-6-daniel.vetter@ffwll.ch \ --to=daniel.vetter@ffwll.ch \ --cc=daniel.vetter@intel.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=intel-gfx@lists.freedesktop.org \ --cc=jordan@cosmicpenguin.net \ --cc=kalyant@codeaurora.org \ --cc=miaoqinglang@huawei.com \ --cc=rnayak@codeaurora.org \ --cc=robdclark@chromium.org \ --cc=tanmay@codeaurora.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: linkBe 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.