Changes in Makefile

036105e3 - video: Provide screen_info_get_pci_dev() to find screen_info's PCI device

Mon, 12 Feb 2024 09:06:10 +0000

video: Provide screen_info_get_pci_dev() to find screen_info's PCI deviceAdd screen_info_get_pci_dev() to find the PCI device of an instanceof screen_info. Does nothing on systems without PCI bus.v3: * search PCI device with pci_get_base_class() (Sui)v2: * remove ret from screen_info_pci_dev() (Javier)Signed-off-by: Thomas Zimmermann Reviewed-by: Javier Martinez Canillas Link: https://patchwork.freedesktop.org/patch/msgid/20240212090736.11464-3-tzimmermann@suse.de List of files: /linux-6.15/drivers/video/Makefile

75fa9b7e - video: Add helpers for decoding screen_info

Mon, 12 Feb 2024 09:06:09 +0000

video: Add helpers for decoding screen_infoThe plain values as stored in struct screen_info need to be decodedbefore being used. Add helpers that decode the type of video outputand the framebuffer I/O aperture.Old or non-x86 systems may not set the type of video directly, butonly indicate the presence by storing 0x01 in orig_video_isVGA. Thedecoding logic in screen_info_video_type() takes this into account.It then follows similar code in vgacon's vgacon_startup() to detectthe video type from the given values.A call to screen_info_resources() returns all known resources of thegiven screen_info. The resources' values have been taken from existingcode in vgacon and vga16fb. These drivers can later be converted touse the new interfaces.v2: * return ssize_t from screen_info_resources() * don't call __screen_info_has_lfb() unnecessarilySigned-off-by: Thomas Zimmermann Reviewed-by: Javier Martinez Canillas Link: https://patchwork.freedesktop.org/patch/msgid/20240212090736.11464-2-tzimmermann@suse.de List of files: /linux-6.15/drivers/video/Makefile

71fc3249 - video/nomodeset: Select nomodeset= parameter with CONFIG_VIDEO

Thu, 18 Jan 2024 09:05:28 +0000

video/nomodeset: Select nomodeset= parameter with CONFIG_VIDEOEnable support for nomodeset= parameter via CONFIG_VIDEO. Both,DRM and fbdev, already select this option. Remove the existingoption CONFIG_VIDEO_NOMODESET. Simplifies the Kconfig rules.Signed-off-by: Thomas Zimmermann Reviewed-by: Daniel Vetter Link: https://patchwork.freedesktop.org/patch/msgid/20240118090721.7995-4-tzimmermann@suse.de List of files: /linux-6.15/drivers/video/Makefile

a3b6792e - video/cmdline: Introduce CONFIG_VIDEO for video= parameter

Thu, 18 Jan 2024 09:05:26 +0000

video/cmdline: Introduce CONFIG_VIDEO for video= parameterAdd CONFIG_VIDEO for common code in drivers/video/. Use the option toselect helpers for the video= parameter. Replaces CONFIG_VIDEO_CMDLINE.Other common code in drivers/video/ can be moved behind CONFIG_VIDEO,which will simplify the Kconfig rules.Signed-off-by: Thomas Zimmermann Reviewed-by: Daniel Vetter Link: https://patchwork.freedesktop.org/patch/msgid/20240118090721.7995-2-tzimmermann@suse.de List of files: /linux-6.15/drivers/video/Makefile

74708497 - video: Move HP PARISC STI core code to shared location

Mon, 17 Apr 2023 12:56:43 +0000

video: Move HP PARISC STI core code to shared locationSTI core files have been located in console and fbdev code. Movethe source code and header to the directories for video helpers.Also update the config and build rules such that the code dependson the config symbol CONFIG_STI_CORE, which STI console and STIframebuffer select automatically.Cleans up the console makefile and prepares PARISC to implementfb_is_primary_device() within the arch/ directory. No functionalchanges.Signed-off-by: Thomas Zimmermann Acked-by: Arnd Bergmann Acked-by: Helge Deller Link: https://patchwork.freedesktop.org/patch/msgid/20230417125651.25126-12-tzimmermann@suse.de List of files: /linux-6.15/drivers/video/Makefile

93604a5a - fbdev: Handle video= parameter in video/cmdline.c

Thu, 09 Feb 2023 13:55:06 +0000

fbdev: Handle video= parameter in video/cmdline.cHandle the command-line parameter video= in video/cmdline.c. Implementthe fbdev helper fb_get_options() on top. Will allows to handle thekernel parameter in DRM without fbdev dependencies.Note that __video_get_options() has the meaning of its return valueinverted compared to fb_get_options(). The new helper returns true ifthe adapter has been enabled, and false otherwise.There is the ofonly parameter, which disables output for non-OF-basedframebuffers. It is only for offb and looks like a workaround. The actualpurpose it not clear to me. Use 'video=off' or 'nomodeset' instead.Signed-off-by: Thomas Zimmermann Reviewed-by: Javier Martinez Canillas Link: https://patchwork.freedesktop.org/patch/msgid/20230209135509.7786-9-tzimmermann@suse.de List of files: /linux-6.15/drivers/video/Makefile

9a758d87 - drm: Move nomodeset kernel parameter to drivers/video

Fri, 11 Nov 2022 13:30:23 +0000

drm: Move nomodeset kernel parameter to drivers/videoMove the nomodeset kernel parameter to drivers/video to make itavailable to non-DRM drivers. Adapt the interface, but keep the DRMinterface drm_firmware_drivers_only() to avoid churn within DRM. Thefunction should later be inlined into callers.The parameter disables any DRM graphics driver that would replace adriver for firmware-provided scanout buffers. It is an option to easilyfallback to basic graphics output if the hardware's native driver isbroken. Moving it to a more prominent location wil make it availableto fbdev as well.v2: * clarify the meaning of the nomodeset parameter (Javier)Signed-off-by: Thomas Zimmermann Reviewed-by: Javier Martinez Canillas Link: https://patchwork.freedesktop.org/patch/msgid/20221111133024.9897-2-tzimmermann@suse.de List of files: /linux-6.15/drivers/video/Makefile

7283f862 - drm: Implement DRM aperture helpers under video/

Wed, 22 Jun 2022 14:01:33 +0000

drm: Implement DRM aperture helpers under video/Implement DRM's aperture helpers under video/ for sharing with othersub-systems. Remove DRM-isms from the interface. The helpers trackthe ownership of framebuffer apertures and provide hand-over fromfirmware, such as EFI and VESA, to native graphics drivers.Other subsystems, such as fbdev and vfio, also have to maintain ownershipof framebuffer apertures. Moving DRM's aperture helpers to a more publiclocation allows all subsystems to interact with each other and share acommon implementation.The aperture helpers are selected by the various firmware drivers withinDRM and fbdev, and the VGA text-console driver.The original DRM interface is kept in place for use by DRM drivers.v3: * prefix all interfaces with aperture_ (Javier) * rework and simplify documentation (Javier) * rename struct dev_aperture to struct aperture_range * rebase onto latest DRM * update MAINTAINERS entrySigned-off-by: Thomas Zimmermann Reviewed-by: Javier Martinez Canillas Tested-by: Laszlo Ersek Link: https://patchwork.freedesktop.org/patch/msgid/20220622140134.12763-3-tzimmermann@suse.de List of files: /linux-6.15/drivers/video/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/video/Makefile

34bf129a - fbdev: sti: don't select CONFIG_VT

Fri, 05 May 2017 15:25:12 +0000

fbdev: sti: don't select CONFIG_VTWhile working on another build error, I ran into several variations ofthis dependency loop:subsection "Kconfig recursive dependency limitations"drivers/input/Kconfig:8: symbol INPUT is selected by VTFor a resolution refer to Documentation/kbuild/kconfig-language.txtsubsection "Kconfig recursive dependency limitations"drivers/tty/Kconfig:12: symbol VT is selected by FB_STIFor a resolution refer to Documentation/kbuild/kconfig-language.txtsubsection "Kconfig recursive dependency limitations"drivers/video/fbdev/Kconfig:677: symbol FB_STI depends on FBFor a resolution refer to Documentation/kbuild/kconfig-language.txtsubsection "Kconfig recursive dependency limitations"drivers/video/fbdev/Kconfig:5: symbol FB is selected by DRM_KMS_FB_HELPERFor a resolution refer to Documentation/kbuild/kconfig-language.txtsubsection "Kconfig recursive dependency limitations"drivers/gpu/drm/Kconfig:72: symbol DRM_KMS_FB_HELPER is selected by DRM_KMS_CMA_HELPERFor a resolution refer to Documentation/kbuild/kconfig-language.txtsubsection "Kconfig recursive dependency limitations"drivers/gpu/drm/Kconfig:137: symbol DRM_KMS_CMA_HELPER is selected by DRM_HDLCDFor a resolution refer to Documentation/kbuild/kconfig-language.txtsubsection "Kconfig recursive dependency limitations"drivers/gpu/drm/arm/Kconfig:6: symbol DRM_HDLCD depends on OFFor a resolution refer to Documentation/kbuild/kconfig-language.txtsubsection "Kconfig recursive dependency limitations"drivers/of/Kconfig:4: symbol OF is selected by X86_INTEL_CEFor a resolution refer to Documentation/kbuild/kconfig-language.txtsubsection "Kconfig recursive dependency limitations"arch/x86/Kconfig:523: symbol X86_INTEL_CE depends on X86_IO_APICFor a resolution refer to Documentation/kbuild/kconfig-language.txtsubsection "Kconfig recursive dependency limitations"arch/x86/Kconfig:1011: symbol X86_IO_APIC depends on X86_LOCAL_APICFor a resolution refer to Documentation/kbuild/kconfig-language.txtsubsection "Kconfig recursive dependency limitations"arch/x86/Kconfig:1005: symbol X86_LOCAL_APIC depends on X86_UP_APICFor a resolution refer to Documentation/kbuild/kconfig-language.txtsubsection "Kconfig recursive dependency limitations"arch/x86/Kconfig:980: symbol X86_UP_APIC depends on PCI_MSIFor a resolution refer to Documentation/kbuild/kconfig-language.txtsubsection "Kconfig recursive dependency limitations"drivers/pci/Kconfig:11: symbol PCI_MSI is selected by AMD_IOMMUFor a resolution refer to Documentation/kbuild/kconfig-language.txtsubsection "Kconfig recursive dependency limitations"drivers/iommu/Kconfig:106: symbol AMD_IOMMU depends on IOMMU_SUPPORTFor a resolution refer to Documentation/kbuild/kconfig-language.txtsubsection "Kconfig recursive dependency limitations"drivers/iommu/Kconfig:5: symbol IOMMU_SUPPORT is selected by DRM_ETNAVIVFor a resolution refer to Documentation/kbuild/kconfig-language.txtsubsection "Kconfig recursive dependency limitations"drivers/gpu/drm/etnaviv/Kconfig:2: symbol DRM_ETNAVIV depends on THERMALFor a resolution refer to Documentation/kbuild/kconfig-language.txtsubsection "Kconfig recursive dependency limitations"drivers/thermal/Kconfig:5: symbol THERMAL is selected by ACPI_VIDEOFor a resolution refer to Documentation/kbuild/kconfig-language.txtsubsection "Kconfig recursive dependency limitations"drivers/acpi/Kconfig:183: symbol ACPI_VIDEO is selected by INPUTThis doesn't currently show up as I fixed the 'THERMAL' part of it,but I noticed that the FB_STI dependency should not be there butwas introduced by slightly incorrect bug-fix patch that tried tofix a link error.Instead of selecting 'VT' to make us enter the drivers/video/consoledirectory at compile-time, it's sufficient to build thedrivers/video/console/sticore.c file by adding its directoryto when CONFIG_FB_STI is enabled. Alternatively, we could move thesticore code to another directory that is always built when wehave at STI_CONSOLE or FB_STI enabled.Fixes: 17085a934592 ("parisc: stifb: should depend on STI_CONSOLE")Signed-off-by: Arnd Bergmann Cc: Helge Deller Cc: "James E.J. Bottomley" Cc: Alexander Beregalov Signed-off-by: Bartlomiej Zolnierkiewicz List of files: /linux-6.15/drivers/video/Makefile

f7018c21 - video: move fbdev to drivers/video/fbdev

Thu, 13 Feb 2014 13:31:38 +0000

video: move fbdev to drivers/video/fbdevThe drivers/video directory is a mess. It contains generic video relatedfiles, directories for backlight, console, linux logo, lots of fbdevdevice drivers, fbdev framework files.Make some order into the chaos by creating drivers/video/fbdevdirectory, and move all fbdev related files there.No functionality is changed, although I guess it is possible that somesubtle Makefile build order related issue could be created by thispatch.Signed-off-by: Tomi Valkeinen Acked-by: Laurent Pinchart Acked-by: Geert Uytterhoeven Acked-by: Rob Clark Acked-by: Jingoo Han Acked-by: Daniel Vetter List of files: /linux-6.15/drivers/video/Makefile

f167a64e - video / output: Drop display output class support

Mon, 17 Mar 2014 14:49:10 +0000

video / output: Drop display output class supportIt was only ever used by the ACPI video driver, and that only use casevanished over 3 years ago (see commit 677bd810, "ACPI video: removeoutput switching control".) So this is dead code and I guess we canremove it now.Signed-off-by: Jean Delvare Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/video/Makefile

c5f9ee3d - x86, platforms: Remove SGI Visual Workstation

Tue, 25 Feb 2014 20:05:34 +0000

x86, platforms: Remove SGI Visual WorkstationThe SGI Visual Workstation seems to be dead; remove support so wedon't have to continue maintaining it.Cc: Andrey Panin Cc: Michael Reed Link: http://lkml.kernel.org/r/530CFD6C.7040705@zytor.comSigned-off-by: H. Peter Anvin List of files: /linux-6.15/drivers/video/Makefile

e61d05dd - video: add OpenCores VGA/LCD framebuffer driver

Mon, 13 Jan 2014 19:38:10 +0000

video: add OpenCores VGA/LCD framebuffer driverThis adds support for the VGA/LCD core available from OpenCores:http://opencores.org/project,vga_lcdThe driver have been tested together with both OpenRISC andARM (socfpga) processors.Signed-off-by: Stefan Kristiansson Signed-off-by: Tomi Valkeinen List of files: /linux-6.15/drivers/video/Makefile

ee89bd6b - lib: Move fonts from drivers/video/console/ to lib/fonts/

Sun, 09 Jun 2013 09:46:43 +0000

lib: Move fonts from drivers/video/console/ to lib/fonts/Several drivers need font support independent of CONFIG_VT, cfr. commit9cbce8d7e1dae0744ca4f68d62aa7de18196b6f4, "console/font: Refactor fontsupport code selection logic").Hence move the fonts and their support logic from drivers/video/console/ toits own library directory lib/fonts/.This also allows to limit processing of drivers/video/console/Makefile toCONFIG_VT=y again.[Kevin Hilman : Update arch/arm/boot/compressed/Makefile]Signed-off-by: Geert Uytterhoeven List of files: /linux-6.15/drivers/video/Makefile

d1e183c8 - console/font: Refactor font support code selection logic

Wed, 15 May 2013 11:26:20 +0000

console/font: Refactor font support code selection logicThe current Makefile rules to build font support are messy and buggy.Replace them by Kconfig rules: - Introduce CONFIG_FONT_SUPPORT, which controls the building of all font code, - Select CONFIG_FONT_SUPPORT for all drivers that use fonts, - Select CONFIG_FONT_8x16 for all drivers that default to the VGA8x16 font, - Drop the bogus console dependency for CONFIG_VIDEO_VIVI, - Always process drivers/video/console/Makefile, as some drivers need fonts even if CONFIG_VT is not set.This fixes (if CONFIG_SOLO6X10=y and there are no built-in consoledrivers):drivers/built-in.o: In function `solo_osd_print':drivers/staging/media/solo6x10/solo6x10-enc.c:144: undefined reference to `.find_font'This fixes (if CONFIG_VT=n):drivers/built-in.o: In function `vivi_init':vivi.c:(.init.text+0x1a3da): undefined reference to `find_font'Signed-off-by: Geert Uytterhoeven Acked-by: Hans Verkuil [original part]Acked-by: Randy Dunlap [drivers/video/Makefile] List of files: /linux-6.15/drivers/video/Makefile

26549c8d - drivers/video: implement a simple framebuffer driver

Fri, 24 May 2013 22:55:13 +0000

drivers/video: implement a simple framebuffer driverA simple frame-buffer describes a raw memory region that may be renderedto, with the assumption that the display hardware has already been setup to scan out from that buffer.This is useful in cases where a bootloader exists and has set up thedisplay hardware, but a Linux driver doesn't yet exist for the displayhardware.Examples use-cases include:* The built-in LCD panels on the Samsung ARM chromebook, and Tegra devices, and likely many other ARM or embedded systems. These cannot yet be supported using a full graphics driver, since the panel control should be provided by the CDF (Common Display Framework), which has been stuck in design/review for quite some time. One could support these panels using custom SoC-specific code, but there is a desire to use common infra-structure rather than having each SoC vendor invent their own code, hence the desire to wait for CDF.* Hardware for which a full graphics driver is not yet available, and the path to obtain one upstream isn't yet clear. For example, the Raspberry Pi.* Any hardware in early stages of upstreaming, before a full graphics driver has been tackled. This driver can provide a graphical boot console (even full X support) much earlier in the upstreaming process, thus making new SoC or board support more generally useful earlier.[akpm@linux-foundation.org: make simplefb_formats[] static]Signed-off-by: Stephen Warren Cc: Arnd Bergmann Acked-by: Olof Johansson Cc: Rob Clark Cc: Florian Tobias Schandinat Cc: Tomasz Figa Cc: Laurent Pinchart Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/video/Makefile

68a2d20b - drivers/video: add Hyper-V Synthetic Video Frame Buffer Driver

Mon, 29 Apr 2013 22:05:42 +0000

drivers/video: add Hyper-V Synthetic Video Frame Buffer DriverThis is the driver for the Hyper-V Synthetic Video, which supportsscreen resolution up to Full HD 1920x1080 on Windows Server 2012 host,and 1600x1200 on Windows Server 2008 R2 or earlier. It also solves thedouble mouse cursor issue of the emulated video mode.Signed-off-by: Haiyang Zhang Reviewed-by: K. Y. Srinivasan Cc: Greg Kroah-Hartman ,Cc: Olaf Hering Cc: Geert Uytterhoeven Cc: Florian Tobias Schandinat Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/video/Makefile

a38884f6 - videomode: simplify videomode Kconfig and Makefile

Tue, 12 Mar 2013 08:15:43 +0000

videomode: simplify videomode Kconfig and MakefileThis patch simplifies videomode related Kconfig and Makefile. After thispatch, there's only one non-user selectable Kconfig option left,VIDEOMODE_HELPERS. The reasons for the change:* Videomode helper functions are not something that should be shown in the kernel configuration options. The related code should just be included if it's needed, i.e. selected by drivers using videomode.* There's no need to have separate Kconfig options for videomode and display_timing. First of all, the amount of code for both is quite small. Second, videomode depends on display_timing, and display_timing in itself is not really useful, so both would be included in any case.* CONFIG_VIDEOMODE is a bit vague name, and CONFIG_VIDEOMODE_HELPERS describes better what's included.Signed-off-by: Tomi Valkeinen Cc: Steffen Trumtrar Acked-by: Laurent Pinchart List of files: /linux-6.15/drivers/video/Makefile

f142d3bd - video: Add generic HDMI infoframe helpers

Wed, 21 Nov 2012 14:29:29 +0000

video: Add generic HDMI infoframe helpersAdd generic helpers to pack HDMI infoframes into binary buffers.Signed-off-by: Thierry Reding Reviewed-by: Alex Deucher List of files: /linux-6.15/drivers/video/Makefile