Hi all
On Fri, Aug 16, 2019 at 03:22:26PM +0300, Laurent Pinchart wrote:
Hello,
The patch series "[PATCH v4 0/9] DRM panel drivers for omapdrm" added new DRM panel drivers for a set of panels used on OMAP platforms, with the omapdrm and omapfb2 drivers. Both those drivers contain omap-specific panel drivers, which the new DRM panel drivers aims to replace for omapdrm. The new drivers use the same module name as the old ones (with one exception), resulting in module name clashes.
This needs to be fixed separately for omapfb2 and omapdrm.
For omapfb2, we can disable the omapfb2-specific panel drivers in Kconfig when the standard drivers are enabled. As omapfb2 and omapdrm are mutually exclusive, the DRM panel drivers are not useful with omapfb2 in any case. This is done in patch 1/2.
For omapdrm, we can simply drop the omapdrm-specific panel drivers, as the new drivers replace them. This is done in patch 2/2, which was already part of the larger omapdrm patch series "[PATCH 00/60] drm/omap: Replace custom display drivers with drm_bridge and drm_panel".
Laurent Pinchart (2): video: omapfb2: Make standard and custom panel drivers mutually exclusive drm/omap: displays: Remove unused panel drivers
Applied and pushed to drm-misc-next.
Sam