[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20211025075756.3479157-1-javierm@redhat.com>
Date: Mon, 25 Oct 2021 09:57:54 +0200
From: Javier Martinez Canillas <javierm@...hat.com>
To: linux-kernel@...r.kernel.org
Cc: Neal Gompa <ngompa13@...il.com>,
Thomas Zimmermann <tzimmermann@...e.de>,
Peter Robinson <pbrobinson@...il.com>,
Ville Syrjälä
<ville.syrjala@...ux.intel.com>,
Javier Martinez Canillas <javierm@...hat.com>,
Daniel Vetter <daniel@...ll.ch>,
David Airlie <airlied@...ux.ie>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
dri-devel@...ts.freedesktop.org
Subject: [PATCH v2 0/2] Add a drm.disable_native_drivers command line option
This patch-series add a drm.disable_native_drivers option that can be used
to prevent native DRM drivers to be probed. That way, the simpledrm driver
won't be removed which can be useful to troubleshoot DRM drivers problems.
Patch #1 is just a small preparatory patch that moves the logic to remove
the conflicting fbdev frame buffer to a helper function.
Patch #2 adds the new kernel command line option and if set, prevents the
drm_aperture_remove_conflicting_framebuffers() function to succeed.
This is a v2 that addresses the issues pointed out by Thomas and Neal.
Best regards,
Javier
Changes in v2:
- Rename command line parameter to drm.disable_native_drivers.
- Return -EBUSY instead of -EINVAL when the function fails.
- Invert the parameter logic and make it false by default.
Javier Martinez Canillas (2):
drm/aperture: Move conflicting fbdev frame buffer removal to a helper
drm/aperture: Prevent conflicting framebuffers removal if option is
set
drivers/gpu/drm/drm_aperture.c | 54 ++++++++++++++++++++++++++--------
1 file changed, 42 insertions(+), 12 deletions(-)
--
2.31.1
Powered by blists - more mailing lists