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 4/8] drm/msm/dpu1: Don't set allow_fb_modifiers explicitly
Date: Tue, 27 Apr 2021 11:20:14 +0200 [thread overview]
Message-ID: <20210427092018.832258-4-daniel.vetter@ffwll.ch> (raw)
In-Reply-To: <20210427092018.832258-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.
v2: Rebase.
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 88e9cc38c13b..93bc3575bf53 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;
-
dev->max_vblank_count = 0xffffffff;
/* Disable vblank irqs aggressively for power-saving */
dev->vblank_disable_immediate = true;
--
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 4/8] drm/msm/dpu1: Don't set allow_fb_modifiers explicitly
Date: Tue, 27 Apr 2021 11:20:14 +0200 [thread overview]
Message-ID: <20210427092018.832258-4-daniel.vetter@ffwll.ch> (raw)
In-Reply-To: <20210427092018.832258-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.
v2: Rebase.
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 88e9cc38c13b..93bc3575bf53 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;
-
dev->max_vblank_count = 0xffffffff;
/* Disable vblank irqs aggressively for power-saving */
dev->vblank_disable_immediate = true;
--
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-27 9:20 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 9:20 [PATCH 1/8] drm/arm: Don't set allow_fb_modifiers explicitly Daniel Vetter
2021-04-27 9:20 ` [Intel-gfx] " Daniel Vetter
2021-04-27 9:20 ` [PATCH 2/8] drm/arm/malidp: Always list modifiers Daniel Vetter
2021-04-27 9:20 ` [Intel-gfx] " Daniel Vetter
2021-04-27 9:20 ` Daniel Vetter
2021-04-27 15:41 ` Liviu Dudau
2021-04-27 15:41 ` [Intel-gfx] " Liviu Dudau
2021-04-27 15:41 ` Liviu Dudau
2021-04-27 9:20 ` [PATCH 3/8] drm/i915: Don't set allow_fb_modifiers explicitly Daniel Vetter
2021-04-27 9:20 ` [Intel-gfx] " Daniel Vetter
2021-04-27 9:20 ` Daniel Vetter [this message]
2021-04-27 9:20 ` [Intel-gfx] [PATCH 4/8] drm/msm/dpu1: " Daniel Vetter
2021-04-27 9:20 ` [PATCH 5/8] drm/msm/mdp4: Fix modifier support enabling Daniel Vetter
2021-04-27 9:20 ` [Intel-gfx] " Daniel Vetter
2021-04-27 9:20 ` Daniel Vetter
2021-04-27 9:20 ` [PATCH 6/8] drm/nouveau: Don't set allow_fb_modifiers explicitly Daniel Vetter
2021-04-27 9:20 ` [Intel-gfx] " Daniel Vetter
2021-04-27 9:20 ` Daniel Vetter
2021-04-27 9:20 ` [Nouveau] " Daniel Vetter
2021-04-27 9:20 ` [PATCH 7/8] drm/stm: " Daniel Vetter
2021-04-27 9:20 ` [Intel-gfx] " Daniel Vetter
2021-04-27 9:20 ` Daniel Vetter
2021-04-29 19:35 ` Philippe CORNU - foss
2021-04-29 19:35 ` [Intel-gfx] " Philippe CORNU - foss
2021-04-29 19:35 ` Philippe CORNU - foss
2021-04-27 9:20 ` [PATCH 8/8] drm/modifiers: Enforce consistency between the cap an IN_FORMATS Daniel Vetter
2021-04-27 9:20 ` [Intel-gfx] " Daniel Vetter
2021-04-27 9:30 ` Simon Ser
2021-04-27 9:30 ` [Intel-gfx] " Simon Ser
2021-04-27 11:32 ` Emil Velikov
2021-04-27 11:32 ` [Intel-gfx] " Emil Velikov
2021-04-27 12:22 ` Daniel Vetter
2021-04-27 12:22 ` [Intel-gfx] " Daniel Vetter
2021-05-04 14:10 ` Emil Velikov
2021-05-04 14:10 ` [Intel-gfx] " Emil Velikov
2021-05-04 14:58 ` Simon Ser
2021-05-04 14:58 ` [Intel-gfx] " Simon Ser
2021-05-04 15:48 ` Emil Velikov
2021-05-04 15:48 ` [Intel-gfx] " Emil Velikov
2021-05-04 13:38 ` Pekka Paalanen
2021-05-04 13:38 ` [Intel-gfx] " Pekka Paalanen
2021-05-05 19:24 ` Daniel Vetter
2021-05-05 19:24 ` [Intel-gfx] " Daniel Vetter
2021-05-06 9:55 ` Daniel Vetter
2021-05-06 9:55 ` [Intel-gfx] " Daniel Vetter
2021-04-27 10:58 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/8] drm/arm: Don't set allow_fb_modifiers explicitly Patchwork
2021-04-27 11:28 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-04-27 15:25 ` [PATCH 1/8] " Liviu Dudau
2021-04-27 15:25 ` [Intel-gfx] " Liviu Dudau
2021-04-27 15:46 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/8] " 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=20210427092018.832258-4-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: 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.