Changes in Makefile

7fb6afa9 - drm/sti: remove duplicate object names

Wed, 15 Jan 2025 08:58:59 +0000

drm/sti: remove duplicate object namesWhen merging 2 drivers common object files were not deduplicated.Fixes: dcec16efd677 ("drm/sti: Build monolithic driver")Cc: stable@kernel.orgSigned-off-by: Rolf Eike Beer Reviewed-by: Dmitry Baryshkov Link: https://lore.kernel.org/r/1920148.tdWV9SEqCh@devpool47.emlix.comSigned-off-by: Raphael Gallais-Pou List of files: /linux-6.15/drivers/gpu/drm/sti/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/gpu/drm/sti/Makefile

6d10c54a - drm/sti: remove deprecated sti_vtac.c file

Tue, 03 Jan 2017 15:06:48 +0000

drm/sti: remove deprecated sti_vtac.c filestih416 chip family is no more supported in Linux v4.9.It is then useless to keep sti_vtac.c file since it not used at all forthe stih407/10 chip family supported by sti driver.Signed-off-by: Vincent Abriou List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile

b4bba92d - drm/sti: remove stih415-416 platform support

Tue, 20 Sep 2016 13:03:33 +0000

drm/sti: remove stih415-416 platform supportstih415 and stih416 platform are obsolete and no more supported.Only stih407 and stih410 platform are maintained.Signed-off-by: Vincent Abriou Acked-by: Benjamin Gaignard Acked-by: Peter Griffin List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile

dcec16ef - drm/sti: Build monolithic driver

Thu, 24 Sep 2015 17:02:40 +0000

drm/sti: Build monolithic driverThere's no use building the individual drivers as separate modulesbecause they are all only useful if combined into a single DRM/KMSdevice.Cc: Benjamin Gaignard Cc: Vincent Abriou Signed-off-by: Thierry Reding Reviewed-by: Vincent Abriou List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile

9e1f05b2 - drm/sti: rename files and functions

Fri, 31 Jul 2015 09:32:34 +0000

drm/sti: rename files and functionsreplace all "sti_drm_" occurences by "sti_"Signed-off-by: Vincent Abriou Reviewed-by: Benjamin Gaignard List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile

871bcdfe - drm/sti: code clean up

Fri, 31 Jul 2015 09:32:13 +0000

drm/sti: code clean upPurpose is to simplify the STI driver:- remove layer structure- consider video subdev as part of the compositor (like mixer subdev)- remove useless STI_VID0 and STI_VID1 enumSigned-off-by: Vincent Abriou Reviewed-by: Benjamin Gaignard List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile

f32c4c50 - drm: sti: add DVO output connector

Tue, 30 Dec 2014 14:08:16 +0000

drm: sti: add DVO output connectorDigital Video Out connector driver LCD panels.Like HDMI and HDA it create bridge, encoder and connectordrm object.Add binding description.Signed-off-by: Benjamin Gaignard List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile

4fdbc678 - drm: sti: add HQVDP plane

Thu, 11 Dec 2014 10:38:59 +0000

drm: sti: add HQVDP planeHigh Quality Video Data Plane is hardware IP dedicatedto video rendering. Compare to GPD (graphic planes) ithave better scaler capabilities.HQVDP use VID layer to push data into hardware compositorwithout going into DDR. From data flow point of view HQVDPand VID are nested so HQVPD update/disable VID.Signed-off-by: Benjamin Gaignard List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile

96006a77 - drm: sti: add cursor plane

Thu, 11 Dec 2014 12:34:42 +0000

drm: sti: add cursor planestih407 SoC have a dedicated hardware cursor plane,this patch enable it.The hardware have a color look up table, fix it tobe able to use ARGB8888.Signed-off-by: Benjamin Gaignard List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile

9bbf86fe - drm: sti: Add DRM driver itself

Thu, 31 Jul 2014 07:39:11 +0000

drm: sti: Add DRM driver itselfMake the link between all the hardware drivers and DRM/KMS interface.Create the driver itself and make it register all the sub-components.Use GEM CMA helpers for buffer allocation.Signed-off-by: Benjamin Gaignard Reviewed-by: Rob Clark List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile

d219673d - drm: sti: add Compositor

Wed, 30 Jul 2014 17:28:27 +0000

drm: sti: add CompositorCompositor control all the input sub-device (VID, GDP)and the mixer(s).It is the main entry point for composition.Layer interface is used to control the abstracted layers.Add debug in mixer and GDP.Signed-off-by: Benjamin Gaignard Reviewed-by: Rob Clark List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile

e21e2193 - drm: sti: add Mixer

Mon, 28 Jul 2014 08:30:18 +0000

drm: sti: add MixerMixer hardware IP is responsible of mixing the different inputs layers.Z-order is managed by the mixer.We could 2 mixers: one for main path and one for auxillary pathMixers are part of Compositor hardware blockSigned-off-by: Benjamin Gaignard Reviewed-by: Rob Clark List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile

cfd8d744 - drm: sti: add VID layer

Mon, 28 Jul 2014 08:30:02 +0000

drm: sti: add VID layerVIDeo plug are one of the compositor input sub-devices.VID are dedicated to video inputs like YUV plans.Like GDP, VID are part of Compositor hardware blockand use sti_layer structure to provide an abstraction forCompositor calls.Signed-off-by: Benjamin Gaignard Reviewed-by: Rob Clark List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile

ba2d53fb - drm: sti: add GDP layer

Wed, 30 Jul 2014 16:48:35 +0000

drm: sti: add GDP layerGeneric Display Pipeline are one of the compositor input sub-devices.GDP are dedicated to graphic input like RGB plans.GDP is part of Compositor hardware block which will be introduce later.A sti_layer structure is used to abstract GDP calls from Compositor.Signed-off-by: Benjamin Gaignard Reviewed-by: Rob Clark List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile

cdfbff78 - drm: sti: add TVOut driver

Wed, 30 Jul 2014 17:26:17 +0000

drm: sti: add TVOut driverTVout hardware block is responsible to dispatch the data flow comingfrom compositor block to any of the output (HDMI or Analog TV).It control when output are start/stop and configure according therequire flow path.TVout is the parent of HDMI and HDA drivers and bind them at runtime.Tvout is mapped on drm_encoder structure.One encoder is created for each of the sub-devices and link to theirconnector/bridgeSigned-off-by: Benjamin Gaignard Reviewed-by: Rob Clark List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile

c86a5f6e - drm: sti: add HDA driver

Wed, 30 Jul 2014 17:25:30 +0000

drm: sti: add HDA driverAdd driver to support analog TV ouput.HDA driver is mapped on drm_bridge and drm_connector structures.Signed-off-by: Benjamin Gaignard Reviewed-by: Rob Clark List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile

5402626c - drm: sti: add HDMI driver

Wed, 30 Jul 2014 17:24:55 +0000

drm: sti: add HDMI driverAdd driver for HDMI output.HDMI PHY registers are mixed into HDMI device registersand their is only one IRQ for all this hardware block.That is why PHYs aren't using phy framework but only athin hdmi_phy_ops structure with start and stop functions.HDMI driver is mapped on drm_bridge and drm_connector structures.Signed-off-by: Benjamin Gaignard Reviewed-by: Rob Clark List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile

9ed68fa7 - drm: sti: add VTAC drivers

Wed, 30 Jul 2014 17:23:49 +0000

drm: sti: add VTAC driversVideo Traffic Advance Communication Rx and Tx drivers are designedfor inter-die communication.Signed-off-by: Benjamin Gaignard Reviewed-by: Rob Clark List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile

f2cb3148 - drm: sti: add VTG driver

Wed, 30 Jul 2014 16:20:56 +0000

drm: sti: add VTG driverVideo Time Generator drivers are used to synchronize the compositorand tvout hardware IPs by providing line count, sample count,synchronization signals (HSYNC, VSYNC) and top and bottom fieldsindication.VTG are used by pair for each data path (main or auxiliary)one for master and one for slave.Signed-off-by: Benjamin Gaignard Reviewed-by: Rob Clark List of files: /linux-6.15/drivers/gpu/drm/sti/Makefile