From: Sebastian Reichel <sebastian.reichel@collabora.com> To: Sebastian Reichel <sre@kernel.org>, Tomi Valkeinen <tomi.valkeinen@ti.com>, Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>, Stephen Rothwell <sfr@canb.auug.org.au>, Sam Ravnborg <sam@ravnborg.org>, dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-next@vger.kernel.org, Sebastian Reichel <sebastian.reichel@collabora.com>, kernel@collabora.com Subject: [PATCHv1] video: omapfb2: Make standard and custom DSI command mode panel driver mutually exclusive Date: Fri, 8 Jan 2021 12:24:41 +0100 [thread overview] Message-ID: <20210108112441.14609-1-sebastian.reichel@collabora.com> (raw) In-Reply-To: <20210108122540.657501b2@canb.auug.org.au> Standard DRM panel driver for DSI command mode panel used by omapfb2 is also available now. Just like the other panels its module name clashes with the module from drivers/video/fbdev/omap2/omapfb/displays, part of the deprecated omapfb2 fbdev driver. As omapfb2 can only be compiled when the omapdrm driver is disabled, and the DRM panel drivers are useless in that case, make the omapfb2 panel depend on the standard DRM panels being disabled to fix the name clash. Fixes: cf64148abcfd ("drm/panel: Move OMAP's DSI command mode panel driver") Reported-by: Stephen Rothwell <sfr@canb.auug.org.au> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com> --- Laurent introduced and fixed the same issue for the other panels and this simply replicates the same solution for DSI command mode panel. --- drivers/video/fbdev/omap2/omapfb/displays/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/video/fbdev/omap2/omapfb/displays/Kconfig b/drivers/video/fbdev/omap2/omapfb/displays/Kconfig index 744416dc530e..384d74a126dc 100644 --- a/drivers/video/fbdev/omap2/omapfb/displays/Kconfig +++ b/drivers/video/fbdev/omap2/omapfb/displays/Kconfig @@ -43,6 +43,7 @@ config FB_OMAP2_PANEL_DPI config FB_OMAP2_PANEL_DSI_CM tristate "Generic DSI Command Mode Panel" depends on BACKLIGHT_CLASS_DEVICE + depends on DRM_PANEL_DSI_CM = n help Driver for generic DSI command mode panels. -- 2.29.2
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Reichel <sebastian.reichel@collabora.com> To: Sebastian Reichel <sre@kernel.org>, Tomi Valkeinen <tomi.valkeinen@ti.com>, Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Sebastian Reichel <sebastian.reichel@collabora.com>, linux-next@vger.kernel.org, Laurent Pinchart <laurent.pinchart@ideasonboard.com>, kernel@collabora.com, Sam Ravnborg <sam@ravnborg.org> Subject: [PATCHv1] video: omapfb2: Make standard and custom DSI command mode panel driver mutually exclusive Date: Fri, 8 Jan 2021 12:24:41 +0100 [thread overview] Message-ID: <20210108112441.14609-1-sebastian.reichel@collabora.com> (raw) In-Reply-To: <20210108122540.657501b2@canb.auug.org.au> Standard DRM panel driver for DSI command mode panel used by omapfb2 is also available now. Just like the other panels its module name clashes with the module from drivers/video/fbdev/omap2/omapfb/displays, part of the deprecated omapfb2 fbdev driver. As omapfb2 can only be compiled when the omapdrm driver is disabled, and the DRM panel drivers are useless in that case, make the omapfb2 panel depend on the standard DRM panels being disabled to fix the name clash. Fixes: cf64148abcfd ("drm/panel: Move OMAP's DSI command mode panel driver") Reported-by: Stephen Rothwell <sfr@canb.auug.org.au> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com> --- Laurent introduced and fixed the same issue for the other panels and this simply replicates the same solution for DSI command mode panel. --- drivers/video/fbdev/omap2/omapfb/displays/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/video/fbdev/omap2/omapfb/displays/Kconfig b/drivers/video/fbdev/omap2/omapfb/displays/Kconfig index 744416dc530e..384d74a126dc 100644 --- a/drivers/video/fbdev/omap2/omapfb/displays/Kconfig +++ b/drivers/video/fbdev/omap2/omapfb/displays/Kconfig @@ -43,6 +43,7 @@ config FB_OMAP2_PANEL_DPI config FB_OMAP2_PANEL_DSI_CM tristate "Generic DSI Command Mode Panel" depends on BACKLIGHT_CLASS_DEVICE + depends on DRM_PANEL_DSI_CM = n help Driver for generic DSI command mode panels. -- 2.29.2 _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-01-08 11:25 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-08 0:55 linux-next: build failure after merge of the drm tree Stephen Rothwell 2021-01-08 0:55 ` Stephen Rothwell 2021-01-08 1:25 ` Stephen Rothwell 2021-01-08 1:25 ` [Intel-gfx] " Stephen Rothwell 2021-01-08 1:25 ` Stephen Rothwell 2021-01-08 11:24 ` Sebastian Reichel [this message] 2021-01-08 11:24 ` [PATCHv1] video: omapfb2: Make standard and custom DSI command mode panel driver mutually exclusive Sebastian Reichel 2021-01-08 19:58 ` Sam Ravnborg 2021-01-08 19:58 ` Sam Ravnborg 2021-01-12 12:02 ` Sebastian Reichel 2021-01-12 12:02 ` Sebastian Reichel 2021-01-12 13:10 ` Tomi Valkeinen 2021-01-12 13:10 ` Tomi Valkeinen 2021-01-12 16:24 ` omapfb removal (was: Re: [PATCHv1] video: omapfb2: Make standard and custom DSI command mode panel driver mutually exclusive) Sebastian Reichel 2021-01-12 16:24 ` Sebastian Reichel 2021-01-12 16:29 ` Laurent Pinchart 2021-01-12 16:29 ` Laurent Pinchart 2021-01-10 23:56 ` linux-next: build failure after merge of the drm tree Stephen Rothwell 2021-01-10 23:56 ` [Intel-gfx] " Stephen Rothwell 2021-01-10 23:56 ` Stephen Rothwell 2021-01-18 0:59 ` Stephen Rothwell 2021-01-18 0:59 ` [Intel-gfx] " Stephen Rothwell 2021-01-18 0:59 ` Stephen Rothwell 2021-01-18 1:06 ` Dave Airlie 2021-01-18 1:06 ` [Intel-gfx] " Dave Airlie 2021-01-18 1:06 ` Dave Airlie 2021-01-20 12:12 ` Daniel Vetter 2021-01-20 12:12 ` [Intel-gfx] " Daniel Vetter 2021-01-20 12:12 ` Daniel Vetter 2021-01-20 20:44 ` Stephen Rothwell 2021-01-20 20:44 ` [Intel-gfx] " Stephen Rothwell 2021-01-20 20:44 ` Stephen Rothwell
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=20210108112441.14609-1-sebastian.reichel@collabora.com \ --to=sebastian.reichel@collabora.com \ --cc=b.zolnierkie@samsung.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=kernel@collabora.com \ --cc=laurent.pinchart@ideasonboard.com \ --cc=linux-fbdev@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-next@vger.kernel.org \ --cc=sam@ravnborg.org \ --cc=sfr@canb.auug.org.au \ --cc=sre@kernel.org \ --cc=tomi.valkeinen@ti.com \ /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.