From: Daniel Vetter <daniel.vetter@ffwll.ch> To: DRI Development <dri-devel@lists.freedesktop.org> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, Intel Graphics Development <intel-gfx@lists.freedesktop.org>, Maxime Ripard <mripard@kernel.org>, Thomas Zimmermann <tzimmermann@suse.de>, Daniel Vetter <daniel.vetter@intel.com> Subject: [Intel-gfx] [PATCH 2/3] drm/fb-helper: drop redundant pixclock check from drm_fb_helper_set_par() Date: Tue, 4 Apr 2023 21:40:37 +0200 [thread overview] Message-ID: <20230404194038.472803-2-daniel.vetter@ffwll.ch> (raw) In-Reply-To: <20230404194038.472803-1-daniel.vetter@ffwll.ch> The fb_check_var hook is supposed to validate all this stuff. Any errors from fb_set_par are considered driver/hw issues and resulting in dmesg warnings. Luckily we do fix up the pixclock already, so this is all fine. Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Cc: Maxime Ripard <mripard@kernel.org> Cc: Thomas Zimmermann <tzimmermann@suse.de> --- drivers/gpu/drm/drm_fb_helper.c | 5 ----- 1 file changed, 5 deletions(-) diff --git a/drivers/gpu/drm/drm_fb_helper.c b/drivers/gpu/drm/drm_fb_helper.c index eb4ece3e0027..b9696d13a741 100644 --- a/drivers/gpu/drm/drm_fb_helper.c +++ b/drivers/gpu/drm/drm_fb_helper.c @@ -1647,11 +1647,6 @@ int drm_fb_helper_set_par(struct fb_info *info) if (oops_in_progress) return -EBUSY; - if (var->pixclock != 0) { - drm_err(fb_helper->dev, "PIXEL CLOCK SET\n"); - return -EINVAL; - } - /* * Normally we want to make sure that a kms master takes precedence over * fbdev, to avoid fbdev flickering and occasionally stealing the -- 2.40.0
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel.vetter@ffwll.ch> To: DRI Development <dri-devel@lists.freedesktop.org> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, Intel Graphics Development <intel-gfx@lists.freedesktop.org>, Thomas Zimmermann <tzimmermann@suse.de>, Daniel Vetter <daniel.vetter@intel.com> Subject: [PATCH 2/3] drm/fb-helper: drop redundant pixclock check from drm_fb_helper_set_par() Date: Tue, 4 Apr 2023 21:40:37 +0200 [thread overview] Message-ID: <20230404194038.472803-2-daniel.vetter@ffwll.ch> (raw) In-Reply-To: <20230404194038.472803-1-daniel.vetter@ffwll.ch> The fb_check_var hook is supposed to validate all this stuff. Any errors from fb_set_par are considered driver/hw issues and resulting in dmesg warnings. Luckily we do fix up the pixclock already, so this is all fine. Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Cc: Maxime Ripard <mripard@kernel.org> Cc: Thomas Zimmermann <tzimmermann@suse.de> --- drivers/gpu/drm/drm_fb_helper.c | 5 ----- 1 file changed, 5 deletions(-) diff --git a/drivers/gpu/drm/drm_fb_helper.c b/drivers/gpu/drm/drm_fb_helper.c index eb4ece3e0027..b9696d13a741 100644 --- a/drivers/gpu/drm/drm_fb_helper.c +++ b/drivers/gpu/drm/drm_fb_helper.c @@ -1647,11 +1647,6 @@ int drm_fb_helper_set_par(struct fb_info *info) if (oops_in_progress) return -EBUSY; - if (var->pixclock != 0) { - drm_err(fb_helper->dev, "PIXEL CLOCK SET\n"); - return -EINVAL; - } - /* * Normally we want to make sure that a kms master takes precedence over * fbdev, to avoid fbdev flickering and occasionally stealing the -- 2.40.0
next prev parent reply other threads:[~2023-04-04 19:40 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-04 19:40 [PATCH 1/3] drm/fb-helper: set x/yres_virtual in drm_fb_helper_check_var Daniel Vetter 2023-04-04 19:40 ` [Intel-gfx] " Daniel Vetter 2023-04-04 19:40 ` Daniel Vetter 2023-04-04 19:40 ` Daniel Vetter [this message] 2023-04-04 19:40 ` [PATCH 2/3] drm/fb-helper: drop redundant pixclock check from drm_fb_helper_set_par() Daniel Vetter 2023-04-05 10:23 ` Javier Martinez Canillas 2023-04-05 10:23 ` [Intel-gfx] " Javier Martinez Canillas 2023-04-04 19:40 ` [PATCH 3/3] drm/fb-helper: fix input validation gaps in check_var Daniel Vetter 2023-04-04 19:40 ` [Intel-gfx] " Daniel Vetter 2023-04-05 10:52 ` Javier Martinez Canillas 2023-04-05 10:52 ` [Intel-gfx] " Javier Martinez Canillas 2023-04-05 13:23 ` Daniel Vetter 2023-04-05 13:23 ` [Intel-gfx] " Daniel Vetter 2023-04-05 16:27 ` Javier Martinez Canillas 2023-04-05 16:27 ` [Intel-gfx] " Javier Martinez Canillas 2023-04-05 17:20 ` Daniel Vetter 2023-04-05 17:20 ` [Intel-gfx] " Daniel Vetter 2023-04-05 17:42 ` Javier Martinez Canillas 2023-04-05 17:42 ` [Intel-gfx] " Javier Martinez Canillas 2023-04-05 20:44 ` Daniel Vetter 2023-04-05 20:44 ` [Intel-gfx] " Daniel Vetter 2023-04-05 21:09 ` Javier Martinez Canillas 2023-04-05 21:09 ` [Intel-gfx] " Javier Martinez Canillas 2023-04-04 22:42 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/fb-helper: set x/yres_virtual in drm_fb_helper_check_var Patchwork 2023-04-04 22:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2023-04-05 8:28 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork 2023-04-05 10:21 ` [PATCH 1/3] " Javier Martinez Canillas 2023-04-05 10:21 ` Javier Martinez Canillas 2023-04-05 10:21 ` [Intel-gfx] " Javier Martinez Canillas 2023-04-05 13:25 ` Daniel Vetter 2023-04-05 13:25 ` [Intel-gfx] " Daniel Vetter 2023-04-05 13:25 ` Daniel Vetter
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=20230404194038.472803-2-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=mripard@kernel.org \ --cc=tzimmermann@suse.de \ /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.