Changes in Kconfig

bb6dafdb - video: omapfb2: Make standard and custom DSI command mode panel driver mutually exclusive

Fri, 08 Jan 2021 11:24:41 +0000

video: omapfb2: Make standard and custom DSI command mode panel driver mutually exclusiveStandard DRM panel driver for DSI command mode panel used by omapfb2 is alsoavailable now. Just like the other panels its module name clashes with themodule from drivers/video/fbdev/omap2/omapfb/displays, part of the deprecatedomapfb2 fbdev driver. As omapfb2 can only be compiled when the omapdrm driveris disabled, and the DRM panel drivers are useless in that case, make theomapfb2 panel depend on the standard DRM panels being disabled to fixthe name clash.Fixes: cf64148abcfd ("drm/panel: Move OMAP's DSI command mode panel driver")Reported-by: Stephen Rothwell Signed-off-by: Sebastian Reichel Acked-by: Sam Ravnborg Signed-off-by: Tomi Valkeinen Link: https://patchwork.freedesktop.org/patch/msgid/20210108112441.14609-1-sebastian.reichel@collabora.com List of files: /linux-6.15/drivers/video/fbdev/omap2/omapfb/displays/Kconfig

1e938755 - video: omapfb2: Make standard and custom panel drivers mutually exclusive

Fri, 16 Aug 2019 12:22:27 +0000

video: omapfb2: Make standard and custom panel drivers mutually exclusiveStandard DRM panel drivers for several panels used by omapfb2 are nowavailable. Their module name clashes with the modules fromdrivers/video/fbdev/omap2/omapfb/displays, part of the deprecated omapfb2fbdev driver. As omapfb2 can only be compiled when the omapdrm driver isdisabled, and the DRM panel drivers are useless in that case, make theomapfb2 panels depend on the standard DRM panels being disabled to fixthe name clash.Signed-off-by: Laurent Pinchart Reviewed-by: Tomi Valkeinen Reported-by: Stephen Rothwell Fixes: dc2e1e5b279966 ("drm/panel: Add driver for the Toppoly TD043MTEA1 panel")Fixes: 415b8dd0871188 ("drm/panel: Add driver for the Toppoly TD028TTEC1 panel")Fixes: 1c8fc3f0c5d280 ("drm/panel: Add driver for the Sony ACX565AKM panel")Fixes: c9cf4c2a3bd35f ("drm/panel: Add driver for the Sharp LS037V7DW01 panel")Fixes: df439abe650177 ("drm/panel: Add driver for the NEC NL8048HL11 panel")Cc: Bartlomiej Zolnierkiewicz Signed-off-by: Sam Ravnborg [added tags]Link: https://patchwork.freedesktop.org/patch/msgid/20190816122228.9475-2-laurent.pinchart@ideasonboard.com List of files: /linux-6.15/drivers/video/fbdev/omap2/omapfb/displays/Kconfig

ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig

Sun, 19 May 2019 12:07:45 +0000

treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is: GPL-2.0-onlySigned-off-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/video/fbdev/omap2/omapfb/displays/Kconfig

a4bd2525 - drivers: video: fbdev: Kconfig: pedantic cleanups

Mon, 01 Apr 2019 15:46:57 +0000

drivers: video: fbdev: Kconfig: pedantic cleanupsFormatting of Kconfig files doesn't look so pretty, so let theGreat White Handkerchief come around and clean it up.Signed-off-by: Enrico Weigelt, metux IT consult [b.zolnierkie: add missing patch description]Signed-off-by: Bartlomiej Zolnierkiewicz List of files: /linux-6.15/drivers/video/fbdev/omap2/omapfb/displays/Kconfig

d232fd04 - omapfb/displays: change CONFIG_DISPLAY_* to CONFIG_FB_OMAP2_*

Wed, 09 Dec 2015 17:27:48 +0000

omapfb/displays: change CONFIG_DISPLAY_* to CONFIG_FB_OMAP2_*We need to change the config symbols of omapfb's private copy of thepanel and encoder drivers so that we won't have config symbol conflicts.This patch changes the symbols from the panel and encoder drivers usingsimple replacement of DISPLAY_* to FB_OMAP2*.Signed-off-by: Tomi Valkeinen Acked-by: Dave Airlie Acked-by: Rob Clark List of files: /linux-6.15/drivers/video/fbdev/omap2/omapfb/displays/Kconfig

f76ee892 - omapfb: copy omapdss & displays for omapfb

Wed, 09 Dec 2015 16:28:28 +0000

omapfb: copy omapdss & displays for omapfbThis patch makes a copy of the omapdss driver and the omap panel &encoder drivers for omapfb. The purpose is to separate omapdrm andomapfb drivers from each other.Note that this patch only does a direct copy of the files without anyother modifications. The files are not yet used.The original files are in:drivers/video/fbdev/omap2/dss/drivers/video/fbdev/omap2/displays-new/Here's a more detailed explanation about this and the following patches,from the introduction mail of the patch series:A short background on the current status. We have the followingentities:* omapdss, located in drivers/video/fbdev/omap2/dss/. This is a driver for the display subsystem IPs used on OMAP (and related) SoCs. It offers only a kernel internal API, and does not implement anything for fbdev or drm.* omapdss panels and encoders, located in drivers/video/fbdev/omap2/displays-new/. These are panel and external encoder drivers, which use APIs offered by omapdss driver. These also don't implement anything for fbdev or drm.* omapdrm, located in drivers/gpu/drm/omapdrm/. This is a drm driver, which uses omapdss and the panel/encoder drivers to operate the hardware.* omapfb, located in drivers/video/fbdev/omap2/omapfb/. This is an fbdev driver, which uses omapdss and the panel/encoder drivers to operate the hardware.* omap_vout, located in drivers/media/platform/omap/. This is a v4l2 driver, which uses omapdss and omapfb to implement a v4l2 API for the video overlays.So, on the top level, we have either omapdrm, or omapfb+omap_vout. Both ofthose use the same low level drivers. Without going to the historical detailswhy the architecture is like that, I think it's finally time to change that.The situation with omapfb+omap_vout is that it still works, but no new featureshave been added for a long time, and I want to keep it working as it's stillbeing used. At some point in the future I'd like to remove omapfb andomap_vout altogether.Omapdrm, on the other hand, is being actively developed. Sharing the low levelparts with omapfb makes that development more difficult than it should be. Italso "hides" half of the development, as everything happening in the low levelparts resides under fbdev directory, not in the drm directory.I've been wanting to clean this up for a long time, but I haven't figured out avery good way to do it. I still haven't, but here's the best way I have come upwith.This series makes a full copy of the low level parts, omapdss and panel/encoderdrivers. Both omapfb+omap_vout and omapdrm will have their own versions. Thecopy omapfb+omap_vout get is a new copy, and the copy that omapdrm gets is justthe current files moved. This way git will associate the omapdrm version withthe old files.The omapfb+omap_vout versions won't be touched unless there are some big issuesthere.The omapdrm versions can be refactored and cleaned up, as the omapfb supportcode is no longer needed. We can perhaps also merge omapdss and omapdrm intothe same kernel module.This series only does the copy, and the absolutely necessary parts. No furthercleanups are done yet.Signed-off-by: Tomi Valkeinen Acked-by: Dave Airlie Acked-by: Rob Clark List of files: /linux-6.15/drivers/video/fbdev/omap2/omapfb/displays/Kconfig