License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license 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 binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the 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 cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base 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 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately 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 license
identifiers 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 the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version 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 correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 15:07:57 +01:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
kbuild: use $(src) instead of $(srctree)/$(src) for source directory
Kbuild conventionally uses $(obj)/ for generated files, and $(src)/ for
checked-in source files. It is merely a convention without any functional
difference. In fact, $(obj) and $(src) are exactly the same, as defined
in scripts/Makefile.build:
src := $(obj)
When the kernel is built in a separate output directory, $(src) does
not accurately reflect the source directory location. While Kbuild
resolves this discrepancy by specifying VPATH=$(srctree) to search for
source files, it does not cover all cases. For example, when adding a
header search path for local headers, -I$(srctree)/$(src) is typically
passed to the compiler.
This introduces inconsistency between upstream and downstream Makefiles
because $(src) is used instead of $(srctree)/$(src) for the latter.
To address this inconsistency, this commit changes the semantics of
$(src) so that it always points to the directory in the source tree.
Going forward, the variables used in Makefiles will have the following
meanings:
$(obj) - directory in the object tree
$(src) - directory in the source tree (changed by this commit)
$(objtree) - the top of the kernel object tree
$(srctree) - the top of the kernel source tree
Consequently, $(srctree)/$(src) in upstream Makefiles need to be replaced
with $(src).
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Reviewed-by: Nicolas Schier <nicolas@fjasle.eu>
2024-04-27 23:55:02 +09:00
|
|
|
ccflags-y := -I $(src)
|
2024-04-01 05:42:41 +03:00
|
|
|
ccflags-y += -I $(obj)/generated
|
kbuild: use $(src) instead of $(srctree)/$(src) for source directory
Kbuild conventionally uses $(obj)/ for generated files, and $(src)/ for
checked-in source files. It is merely a convention without any functional
difference. In fact, $(obj) and $(src) are exactly the same, as defined
in scripts/Makefile.build:
src := $(obj)
When the kernel is built in a separate output directory, $(src) does
not accurately reflect the source directory location. While Kbuild
resolves this discrepancy by specifying VPATH=$(srctree) to search for
source files, it does not cover all cases. For example, when adding a
header search path for local headers, -I$(srctree)/$(src) is typically
passed to the compiler.
This introduces inconsistency between upstream and downstream Makefiles
because $(src) is used instead of $(srctree)/$(src) for the latter.
To address this inconsistency, this commit changes the semantics of
$(src) so that it always points to the directory in the source tree.
Going forward, the variables used in Makefiles will have the following
meanings:
$(obj) - directory in the object tree
$(src) - directory in the source tree (changed by this commit)
$(objtree) - the top of the kernel object tree
$(srctree) - the top of the kernel source tree
Consequently, $(srctree)/$(src) in upstream Makefiles need to be replaced
with $(src).
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Reviewed-by: Nicolas Schier <nicolas@fjasle.eu>
2024-04-27 23:55:02 +09:00
|
|
|
ccflags-y += -I $(src)/disp/dpu1
|
|
|
|
|
ccflags-$(CONFIG_DRM_MSM_DSI) += -I $(src)/dsi
|
|
|
|
|
ccflags-$(CONFIG_DRM_MSM_DP) += -I $(src)/dp
|
drm/msm: basic KMS driver for snapdragon
The snapdragon chips have multiple different display controllers,
depending on which chip variant/version. (As far as I can tell, current
devices have either MDP3 or MDP4, and upcoming devices have MDSS.) And
then external to the display controller are HDMI, DSI, etc. blocks which
may be shared across devices which have different display controller
blocks.
To more easily add support for different display controller blocks, the
display controller specific bits are split out into a "kms" module,
which provides the kms plane/crtc/encoder objects.
The external HDMI, DSI, etc. blocks are part encoder, and part connector
currently. But I think I will pull in the drm_bridge patches from
chromeos tree, and split them into a bridge+connector, with the
registers that need to be set in modeset handled by the bridge. This
would remove the 'msm_connector' base class. But some things need to be
double checked to make sure I could get the correct ON/OFF sequencing..
This patch adds support for mdp4 crtc (including hw cursor), dtv encoder
(part of MDP4 block), and hdmi.
Signed-off-by: Rob Clark <robdclark@gmail.com>
2013-06-26 12:44:06 -04:00
|
|
|
|
2024-04-01 05:42:41 +03:00
|
|
|
adreno-y := \
|
2014-09-05 13:06:37 -04:00
|
|
|
adreno/adreno_device.o \
|
2013-07-19 12:59:32 -04:00
|
|
|
adreno/adreno_gpu.o \
|
2024-06-18 09:42:48 -07:00
|
|
|
adreno/a2xx_catalog.o \
|
2018-11-21 20:52:32 -05:00
|
|
|
adreno/a2xx_gpu.o \
|
2024-04-01 05:42:34 +03:00
|
|
|
adreno/a2xx_gpummu.o \
|
2024-06-18 09:42:48 -07:00
|
|
|
adreno/a3xx_catalog.o \
|
2013-07-19 12:59:32 -04:00
|
|
|
adreno/a3xx_gpu.o \
|
2024-06-18 09:42:48 -07:00
|
|
|
adreno/a4xx_catalog.o \
|
2014-09-08 13:40:16 -06:00
|
|
|
adreno/a4xx_gpu.o \
|
2024-06-18 09:42:48 -07:00
|
|
|
adreno/a5xx_catalog.o \
|
2016-11-28 12:28:33 -07:00
|
|
|
adreno/a5xx_gpu.o \
|
2016-11-28 12:28:34 -07:00
|
|
|
adreno/a5xx_power.o \
|
2017-10-20 11:07:01 -06:00
|
|
|
adreno/a5xx_preempt.o \
|
2024-06-18 09:42:48 -07:00
|
|
|
adreno/a6xx_catalog.o \
|
2018-08-06 11:33:24 -06:00
|
|
|
adreno/a6xx_gpu.o \
|
|
|
|
|
adreno/a6xx_gmu.o \
|
|
|
|
|
adreno/a6xx_hfi.o \
|
2024-10-03 18:12:55 +02:00
|
|
|
adreno/a6xx_preempt.o \
|
2022-04-19 18:53:45 +03:00
|
|
|
|
2024-04-01 05:42:41 +03:00
|
|
|
adreno-$(CONFIG_DEBUG_FS) += adreno/a5xx_debugfs.o \
|
|
|
|
|
|
|
|
|
|
adreno-$(CONFIG_DRM_MSM_GPU_STATE) += adreno/a6xx_gpu_state.o
|
|
|
|
|
|
|
|
|
|
msm-display-$(CONFIG_DRM_MSM_HDMI) += \
|
drm/msm: basic KMS driver for snapdragon
The snapdragon chips have multiple different display controllers,
depending on which chip variant/version. (As far as I can tell, current
devices have either MDP3 or MDP4, and upcoming devices have MDSS.) And
then external to the display controller are HDMI, DSI, etc. blocks which
may be shared across devices which have different display controller
blocks.
To more easily add support for different display controller blocks, the
display controller specific bits are split out into a "kms" module,
which provides the kms plane/crtc/encoder objects.
The external HDMI, DSI, etc. blocks are part encoder, and part connector
currently. But I think I will pull in the drm_bridge patches from
chromeos tree, and split them into a bridge+connector, with the
registers that need to be set in modeset handled by the bridge. This
would remove the 'msm_connector' base class. But some things need to be
double checked to make sure I could get the correct ON/OFF sequencing..
This patch adds support for mdp4 crtc (including hw cursor), dtv encoder
(part of MDP4 block), and hdmi.
Signed-off-by: Rob Clark <robdclark@gmail.com>
2013-06-26 12:44:06 -04:00
|
|
|
hdmi/hdmi.o \
|
2013-12-11 14:44:02 -05:00
|
|
|
hdmi/hdmi_audio.o \
|
2013-08-30 13:02:15 -04:00
|
|
|
hdmi/hdmi_bridge.o \
|
2021-10-15 03:11:00 +03:00
|
|
|
hdmi/hdmi_hpd.o \
|
drm/msm: basic KMS driver for snapdragon
The snapdragon chips have multiple different display controllers,
depending on which chip variant/version. (As far as I can tell, current
devices have either MDP3 or MDP4, and upcoming devices have MDSS.) And
then external to the display controller are HDMI, DSI, etc. blocks which
may be shared across devices which have different display controller
blocks.
To more easily add support for different display controller blocks, the
display controller specific bits are split out into a "kms" module,
which provides the kms plane/crtc/encoder objects.
The external HDMI, DSI, etc. blocks are part encoder, and part connector
currently. But I think I will pull in the drm_bridge patches from
chromeos tree, and split them into a bridge+connector, with the
registers that need to be set in modeset handled by the bridge. This
would remove the 'msm_connector' base class. But some things need to be
double checked to make sure I could get the correct ON/OFF sequencing..
This patch adds support for mdp4 crtc (including hw cursor), dtv encoder
(part of MDP4 block), and hdmi.
Signed-off-by: Rob Clark <robdclark@gmail.com>
2013-06-26 12:44:06 -04:00
|
|
|
hdmi/hdmi_i2c.o \
|
2016-02-25 11:22:38 +05:30
|
|
|
hdmi/hdmi_phy.o \
|
drm/msm: basic KMS driver for snapdragon
The snapdragon chips have multiple different display controllers,
depending on which chip variant/version. (As far as I can tell, current
devices have either MDP3 or MDP4, and upcoming devices have MDSS.) And
then external to the display controller are HDMI, DSI, etc. blocks which
may be shared across devices which have different display controller
blocks.
To more easily add support for different display controller blocks, the
display controller specific bits are split out into a "kms" module,
which provides the kms plane/crtc/encoder objects.
The external HDMI, DSI, etc. blocks are part encoder, and part connector
currently. But I think I will pull in the drm_bridge patches from
chromeos tree, and split them into a bridge+connector, with the
registers that need to be set in modeset handled by the bridge. This
would remove the 'msm_connector' base class. But some things need to be
double checked to make sure I could get the correct ON/OFF sequencing..
This patch adds support for mdp4 crtc (including hw cursor), dtv encoder
(part of MDP4 block), and hdmi.
Signed-off-by: Rob Clark <robdclark@gmail.com>
2013-06-26 12:44:06 -04:00
|
|
|
hdmi/hdmi_phy_8960.o \
|
2021-10-13 16:42:56 +02:00
|
|
|
hdmi/hdmi_phy_8996.o \
|
2024-07-24 17:01:37 +02:00
|
|
|
hdmi/hdmi_phy_8998.o \
|
drm/msm: basic KMS driver for snapdragon
The snapdragon chips have multiple different display controllers,
depending on which chip variant/version. (As far as I can tell, current
devices have either MDP3 or MDP4, and upcoming devices have MDSS.) And
then external to the display controller are HDMI, DSI, etc. blocks which
may be shared across devices which have different display controller
blocks.
To more easily add support for different display controller blocks, the
display controller specific bits are split out into a "kms" module,
which provides the kms plane/crtc/encoder objects.
The external HDMI, DSI, etc. blocks are part encoder, and part connector
currently. But I think I will pull in the drm_bridge patches from
chromeos tree, and split them into a bridge+connector, with the
registers that need to be set in modeset handled by the bridge. This
would remove the 'msm_connector' base class. But some things need to be
double checked to make sure I could get the correct ON/OFF sequencing..
This patch adds support for mdp4 crtc (including hw cursor), dtv encoder
(part of MDP4 block), and hdmi.
Signed-off-by: Rob Clark <robdclark@gmail.com>
2013-06-26 12:44:06 -04:00
|
|
|
hdmi/hdmi_phy_8x60.o \
|
2013-12-01 12:12:54 -05:00
|
|
|
hdmi/hdmi_phy_8x74.o \
|
2021-10-13 16:42:56 +02:00
|
|
|
hdmi/hdmi_pll_8960.o \
|
2022-04-19 18:53:45 +03:00
|
|
|
|
2024-04-01 05:42:41 +03:00
|
|
|
msm-display-$(CONFIG_DRM_MSM_MDP4) += \
|
2018-02-12 08:18:27 -05:00
|
|
|
disp/mdp4/mdp4_crtc.o \
|
2022-04-19 18:53:45 +03:00
|
|
|
disp/mdp4/mdp4_dsi_encoder.o \
|
2018-02-12 08:18:27 -05:00
|
|
|
disp/mdp4/mdp4_dtv_encoder.o \
|
|
|
|
|
disp/mdp4/mdp4_lcdc_encoder.o \
|
2021-10-13 16:42:56 +02:00
|
|
|
disp/mdp4/mdp4_lvds_pll.o \
|
2018-02-12 08:18:27 -05:00
|
|
|
disp/mdp4/mdp4_irq.o \
|
|
|
|
|
disp/mdp4/mdp4_kms.o \
|
|
|
|
|
disp/mdp4/mdp4_plane.o \
|
2022-04-19 18:53:45 +03:00
|
|
|
|
2024-04-01 05:42:41 +03:00
|
|
|
msm-display-$(CONFIG_DRM_MSM_MDP5) += \
|
2018-02-12 08:18:27 -05:00
|
|
|
disp/mdp5/mdp5_cfg.o \
|
2022-04-19 18:53:45 +03:00
|
|
|
disp/mdp5/mdp5_cmd_encoder.o \
|
2018-02-12 08:18:27 -05:00
|
|
|
disp/mdp5/mdp5_ctl.o \
|
|
|
|
|
disp/mdp5/mdp5_crtc.o \
|
|
|
|
|
disp/mdp5/mdp5_encoder.o \
|
|
|
|
|
disp/mdp5/mdp5_irq.o \
|
|
|
|
|
disp/mdp5/mdp5_kms.o \
|
|
|
|
|
disp/mdp5/mdp5_pipe.o \
|
|
|
|
|
disp/mdp5/mdp5_mixer.o \
|
|
|
|
|
disp/mdp5/mdp5_plane.o \
|
|
|
|
|
disp/mdp5/mdp5_smp.o \
|
2022-04-19 18:53:45 +03:00
|
|
|
|
2024-04-01 05:42:41 +03:00
|
|
|
msm-display-$(CONFIG_DRM_MSM_DPU) += \
|
2018-06-27 15:26:09 -04:00
|
|
|
disp/dpu1/dpu_core_perf.o \
|
|
|
|
|
disp/dpu1/dpu_crtc.o \
|
|
|
|
|
disp/dpu1/dpu_encoder.o \
|
|
|
|
|
disp/dpu1/dpu_encoder_phys_cmd.o \
|
|
|
|
|
disp/dpu1/dpu_encoder_phys_vid.o \
|
2022-04-26 07:41:30 -07:00
|
|
|
disp/dpu1/dpu_encoder_phys_wb.o \
|
2018-06-27 15:26:09 -04:00
|
|
|
disp/dpu1/dpu_formats.o \
|
|
|
|
|
disp/dpu1/dpu_hw_catalog.o \
|
2023-12-12 12:52:45 -08:00
|
|
|
disp/dpu1/dpu_hw_cdm.o \
|
2018-06-27 15:26:09 -04:00
|
|
|
disp/dpu1/dpu_hw_ctl.o \
|
2024-12-16 16:43:23 -08:00
|
|
|
disp/dpu1/dpu_hw_cwb.o \
|
2022-04-06 15:10:20 +05:30
|
|
|
disp/dpu1/dpu_hw_dsc.o \
|
2023-05-25 10:40:54 -07:00
|
|
|
disp/dpu1/dpu_hw_dsc_1_2.o \
|
2018-06-27 15:26:09 -04:00
|
|
|
disp/dpu1/dpu_hw_interrupts.o \
|
|
|
|
|
disp/dpu1/dpu_hw_intf.o \
|
|
|
|
|
disp/dpu1/dpu_hw_lm.o \
|
|
|
|
|
disp/dpu1/dpu_hw_pingpong.o \
|
|
|
|
|
disp/dpu1/dpu_hw_sspp.o \
|
2020-03-24 15:31:18 +05:30
|
|
|
disp/dpu1/dpu_hw_dspp.o \
|
2020-10-22 16:16:55 +03:00
|
|
|
disp/dpu1/dpu_hw_merge3d.o \
|
2018-06-27 15:26:09 -04:00
|
|
|
disp/dpu1/dpu_hw_top.o \
|
|
|
|
|
disp/dpu1/dpu_hw_util.o \
|
|
|
|
|
disp/dpu1/dpu_hw_vbif.o \
|
2022-04-26 07:41:23 -07:00
|
|
|
disp/dpu1/dpu_hw_wb.o \
|
2018-06-27 15:26:09 -04:00
|
|
|
disp/dpu1/dpu_kms.o \
|
|
|
|
|
disp/dpu1/dpu_plane.o \
|
|
|
|
|
disp/dpu1/dpu_rm.o \
|
|
|
|
|
disp/dpu1/dpu_vbif.o \
|
2022-04-26 07:41:31 -07:00
|
|
|
disp/dpu1/dpu_writeback.o
|
2022-04-19 18:53:45 +03:00
|
|
|
|
2024-04-01 05:42:41 +03:00
|
|
|
msm-display-$(CONFIG_DRM_MSM_MDSS) += \
|
2022-04-19 18:53:45 +03:00
|
|
|
msm_mdss.o \
|
|
|
|
|
|
2025-07-05 13:02:31 +03:00
|
|
|
msm-display-$(CONFIG_DRM_MSM_KMS) += \
|
2022-04-19 18:53:45 +03:00
|
|
|
disp/mdp_format.o \
|
|
|
|
|
disp/mdp_kms.o \
|
2021-04-16 13:57:20 -07:00
|
|
|
disp/msm_disp_snapshot.o \
|
|
|
|
|
disp/msm_disp_snapshot_util.o \
|
2024-04-01 05:42:41 +03:00
|
|
|
|
|
|
|
|
msm-y += \
|
2016-03-16 12:56:12 -04:00
|
|
|
msm_debugfs.o \
|
drm/msm: basic KMS driver for snapdragon
The snapdragon chips have multiple different display controllers,
depending on which chip variant/version. (As far as I can tell, current
devices have either MDP3 or MDP4, and upcoming devices have MDSS.) And
then external to the display controller are HDMI, DSI, etc. blocks which
may be shared across devices which have different display controller
blocks.
To more easily add support for different display controller blocks, the
display controller specific bits are split out into a "kms" module,
which provides the kms plane/crtc/encoder objects.
The external HDMI, DSI, etc. blocks are part encoder, and part connector
currently. But I think I will pull in the drm_bridge patches from
chromeos tree, and split them into a bridge+connector, with the
registers that need to be set in modeset handled by the bridge. This
would remove the 'msm_connector' base class. But some things need to be
double checked to make sure I could get the correct ON/OFF sequencing..
This patch adds support for mdp4 crtc (including hw cursor), dtv encoder
(part of MDP4 block), and hdmi.
Signed-off-by: Rob Clark <robdclark@gmail.com>
2013-06-26 12:44:06 -04:00
|
|
|
msm_drv.o \
|
2016-03-15 15:35:08 -04:00
|
|
|
msm_fence.o \
|
2013-07-19 12:59:32 -04:00
|
|
|
msm_gem.o \
|
2013-09-28 11:28:35 -04:00
|
|
|
msm_gem_prime.o \
|
2016-05-17 16:19:32 -04:00
|
|
|
msm_gem_shrinker.o \
|
2013-07-19 12:59:32 -04:00
|
|
|
msm_gem_submit.o \
|
2016-09-28 19:58:32 -04:00
|
|
|
msm_gem_vma.o \
|
2013-07-19 12:59:32 -04:00
|
|
|
msm_gpu.o \
|
2021-07-26 07:46:48 -07:00
|
|
|
msm_gpu_devfreq.o \
|
2022-01-20 01:16:14 +03:00
|
|
|
msm_io_utils.o \
|
2013-11-16 12:56:06 -05:00
|
|
|
msm_iommu.o \
|
2014-05-30 14:49:43 -04:00
|
|
|
msm_perf.o \
|
2014-05-30 14:47:38 -04:00
|
|
|
msm_rd.o \
|
2017-10-20 11:06:55 -06:00
|
|
|
msm_ringbuffer.o \
|
2018-11-02 09:25:21 -06:00
|
|
|
msm_submitqueue.o \
|
2025-06-29 13:13:12 -07:00
|
|
|
msm_syncobj.o \
|
2018-11-14 17:08:04 -05:00
|
|
|
msm_gpu_tracepoints.o \
|
drm/msm: basic KMS driver for snapdragon
The snapdragon chips have multiple different display controllers,
depending on which chip variant/version. (As far as I can tell, current
devices have either MDP3 or MDP4, and upcoming devices have MDSS.) And
then external to the display controller are HDMI, DSI, etc. blocks which
may be shared across devices which have different display controller
blocks.
To more easily add support for different display controller blocks, the
display controller specific bits are split out into a "kms" module,
which provides the kms plane/crtc/encoder objects.
The external HDMI, DSI, etc. blocks are part encoder, and part connector
currently. But I think I will pull in the drm_bridge patches from
chromeos tree, and split them into a bridge+connector, with the
registers that need to be set in modeset handled by the bridge. This
would remove the 'msm_connector' base class. But some things need to be
double checked to make sure I could get the correct ON/OFF sequencing..
This patch adds support for mdp4 crtc (including hw cursor), dtv encoder
(part of MDP4 block), and hdmi.
Signed-off-by: Rob Clark <robdclark@gmail.com>
2013-06-26 12:44:06 -04:00
|
|
|
|
2025-07-05 13:02:31 +03:00
|
|
|
msm-$(CONFIG_DRM_MSM_KMS) += \
|
|
|
|
|
msm_atomic.o \
|
|
|
|
|
msm_atomic_tracepoints.o \
|
|
|
|
|
msm_fb.o \
|
|
|
|
|
msm_kms.o \
|
2017-12-13 15:12:56 -05:00
|
|
|
|
2025-07-05 13:02:31 +03:00
|
|
|
msm-$(CONFIG_DRM_MSM_KMS_FBDEV) += msm_fbdev.o
|
2019-04-10 10:58:16 -06:00
|
|
|
|
2024-04-01 05:42:41 +03:00
|
|
|
msm-display-$(CONFIG_DRM_MSM_DP)+= dp/dp_aux.o \
|
2020-08-27 14:16:55 -07:00
|
|
|
dp/dp_ctrl.o \
|
2025-07-05 13:02:31 +03:00
|
|
|
dp/dp_debug.o \
|
2020-08-27 14:16:55 -07:00
|
|
|
dp/dp_display.o \
|
|
|
|
|
dp/dp_drm.o \
|
|
|
|
|
dp/dp_link.o \
|
|
|
|
|
dp/dp_panel.o \
|
2024-02-22 11:39:57 -08:00
|
|
|
dp/dp_audio.o \
|
|
|
|
|
dp/dp_utils.o
|
2020-08-27 14:16:55 -07:00
|
|
|
|
2024-04-01 05:42:41 +03:00
|
|
|
msm-display-$(CONFIG_DRM_MSM_HDMI_HDCP) += hdmi/hdmi_hdcp.o
|
2016-03-20 10:16:29 -04:00
|
|
|
|
2024-04-01 05:42:41 +03:00
|
|
|
msm-display-$(CONFIG_DRM_MSM_DSI) += dsi/dsi.o \
|
2015-08-13 17:49:29 -04:00
|
|
|
dsi/dsi_cfg.o \
|
2015-03-31 14:36:33 -04:00
|
|
|
dsi/dsi_host.o \
|
|
|
|
|
dsi/dsi_manager.o \
|
2022-04-19 18:53:45 +03:00
|
|
|
dsi/phy/dsi_phy.o
|
drm/msm: basic KMS driver for snapdragon
The snapdragon chips have multiple different display controllers,
depending on which chip variant/version. (As far as I can tell, current
devices have either MDP3 or MDP4, and upcoming devices have MDSS.) And
then external to the display controller are HDMI, DSI, etc. blocks which
may be shared across devices which have different display controller
blocks.
To more easily add support for different display controller blocks, the
display controller specific bits are split out into a "kms" module,
which provides the kms plane/crtc/encoder objects.
The external HDMI, DSI, etc. blocks are part encoder, and part connector
currently. But I think I will pull in the drm_bridge patches from
chromeos tree, and split them into a bridge+connector, with the
registers that need to be set in modeset handled by the bridge. This
would remove the 'msm_connector' base class. But some things need to be
double checked to make sure I could get the correct ON/OFF sequencing..
This patch adds support for mdp4 crtc (including hw cursor), dtv encoder
(part of MDP4 block), and hdmi.
Signed-off-by: Rob Clark <robdclark@gmail.com>
2013-06-26 12:44:06 -04:00
|
|
|
|
2024-04-01 05:42:41 +03:00
|
|
|
msm-display-$(CONFIG_DRM_MSM_DSI_28NM_PHY) += dsi/phy/dsi_phy_28nm.o
|
|
|
|
|
msm-display-$(CONFIG_DRM_MSM_DSI_20NM_PHY) += dsi/phy/dsi_phy_20nm.o
|
|
|
|
|
msm-display-$(CONFIG_DRM_MSM_DSI_28NM_8960_PHY) += dsi/phy/dsi_phy_28nm_8960.o
|
|
|
|
|
msm-display-$(CONFIG_DRM_MSM_DSI_14NM_PHY) += dsi/phy/dsi_phy_14nm.o
|
|
|
|
|
msm-display-$(CONFIG_DRM_MSM_DSI_10NM_PHY) += dsi/phy/dsi_phy_10nm.o
|
|
|
|
|
msm-display-$(CONFIG_DRM_MSM_DSI_7NM_PHY) += dsi/phy/dsi_phy_7nm.o
|
|
|
|
|
|
2025-07-05 13:02:31 +03:00
|
|
|
msm-y += $(adreno-y)
|
|
|
|
|
msm-$(CONFIG_DRM_MSM_KMS) += $(msm-display-y)
|
2015-08-13 17:45:53 -04:00
|
|
|
|
drm/msm: basic KMS driver for snapdragon
The snapdragon chips have multiple different display controllers,
depending on which chip variant/version. (As far as I can tell, current
devices have either MDP3 or MDP4, and upcoming devices have MDSS.) And
then external to the display controller are HDMI, DSI, etc. blocks which
may be shared across devices which have different display controller
blocks.
To more easily add support for different display controller blocks, the
display controller specific bits are split out into a "kms" module,
which provides the kms plane/crtc/encoder objects.
The external HDMI, DSI, etc. blocks are part encoder, and part connector
currently. But I think I will pull in the drm_bridge patches from
chromeos tree, and split them into a bridge+connector, with the
registers that need to be set in modeset handled by the bridge. This
would remove the 'msm_connector' base class. But some things need to be
double checked to make sure I could get the correct ON/OFF sequencing..
This patch adds support for mdp4 crtc (including hw cursor), dtv encoder
(part of MDP4 block), and hdmi.
Signed-off-by: Rob Clark <robdclark@gmail.com>
2013-06-26 12:44:06 -04:00
|
|
|
obj-$(CONFIG_DRM_MSM) += msm.o
|
2024-04-01 05:42:41 +03:00
|
|
|
|
2024-05-03 21:15:03 +03:00
|
|
|
ifeq (y,$(CONFIG_DRM_MSM_VALIDATE_XML))
|
|
|
|
|
headergen-opts += --validate
|
|
|
|
|
else
|
|
|
|
|
headergen-opts += --no-validate
|
|
|
|
|
endif
|
|
|
|
|
|
2024-04-01 05:42:41 +03:00
|
|
|
quiet_cmd_headergen = GENHDR $@
|
Kbuild updates for v6.10
- Avoid 'constexpr', which is a keyword in C23
- Allow 'dtbs_check' and 'dt_compatible_check' run independently of
'dt_binding_check'
- Fix weak references to avoid GOT entries in position-independent
code generation
- Convert the last use of 'optional' property in arch/sh/Kconfig
- Remove support for the 'optional' property in Kconfig
- Remove support for Clang's ThinLTO caching, which does not work with
the .incbin directive
- Change the semantics of $(src) so it always points to the source
directory, which fixes Makefile inconsistencies between upstream and
downstream
- Fix 'make tar-pkg' for RISC-V to produce a consistent package
- Provide reasonable default coverage for objtool, sanitizers, and
profilers
- Remove redundant OBJECT_FILES_NON_STANDARD, KASAN_SANITIZE, etc.
- Remove the last use of tristate choice in drivers/rapidio/Kconfig
- Various cleanups and fixes in Kconfig
-----BEGIN PGP SIGNATURE-----
iQJJBAABCgAzFiEEbmPs18K1szRHjPqEPYsBB53g2wYFAmZFlGcVHG1hc2FoaXJv
eUBrZXJuZWwub3JnAAoJED2LAQed4NsG8voQALC8NtFpduWVfLRj2Qg6Ll/xf1vX
2igcTJEOFHkeqXLGoT8dTDKLEipUBUvKyguPq66CGwVTe2g6zy/nUSXeVtFrUsIa
msLTi8FqhqUo5lodNvGMRf8qqmuqcvnXoiQwIocF92jtsFy14bhiFY+n4HfcFNjj
GOKwqBZYQUwY/VVb090efc7RfS9c7uwABJSBelSoxg3AGZriwjGy7Pw5aSKGgVYi
inqL1eR6qwPP6z7CgQWM99soP+zwybFZmnQrsD9SniRBI4rtAat8Ih5jQFaSUFUQ
lk2w0NQBRFN88/uR2IJ2GWuIlQ74WeJ+QnCqVuQ59tV5zw90wqSmLzngfPD057Dv
JjNuhk0UyXVtpIg3lRtd4810ppNSTe33b9OM4O2H846W/crju5oDRNDHcflUXcwm
Rmn5ho1rb5QVzDVejJbgwidnUInSgJ9PZcvXQ/RJVZPhpgsBzAY9pQexG1G3hviw
y9UDrt6KP6bF9tHjmolmtdIes9Pj0c4dN6/Rdj4HS4hIQ/GDar0tnwvOvtfUctNL
orJlBsA6GeMmDVXKkR0ytOCWRYqWWbyt8g70RVKQJfuHX7/hGyAQPaQ2/u4mQhC2
aevYfbNJMj0VDfGz81HDBKFtkc5n+Ite8l157dHEl2LEabkOkRdNVcn7SNbOvZmd
ZCSnZ31h7woGfNho
=D5B/
-----END PGP SIGNATURE-----
Merge tag 'kbuild-v6.10' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild
Pull Kbuild updates from Masahiro Yamada:
- Avoid 'constexpr', which is a keyword in C23
- Allow 'dtbs_check' and 'dt_compatible_check' run independently of
'dt_binding_check'
- Fix weak references to avoid GOT entries in position-independent code
generation
- Convert the last use of 'optional' property in arch/sh/Kconfig
- Remove support for the 'optional' property in Kconfig
- Remove support for Clang's ThinLTO caching, which does not work with
the .incbin directive
- Change the semantics of $(src) so it always points to the source
directory, which fixes Makefile inconsistencies between upstream and
downstream
- Fix 'make tar-pkg' for RISC-V to produce a consistent package
- Provide reasonable default coverage for objtool, sanitizers, and
profilers
- Remove redundant OBJECT_FILES_NON_STANDARD, KASAN_SANITIZE, etc.
- Remove the last use of tristate choice in drivers/rapidio/Kconfig
- Various cleanups and fixes in Kconfig
* tag 'kbuild-v6.10' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild: (46 commits)
kconfig: use sym_get_choice_menu() in sym_check_prop()
rapidio: remove choice for enumeration
kconfig: lxdialog: remove initialization with A_NORMAL
kconfig: m/nconf: merge two item_add_str() calls
kconfig: m/nconf: remove dead code to display value of bool choice
kconfig: m/nconf: remove dead code to display children of choice members
kconfig: gconf: show checkbox for choice correctly
kbuild: use GCOV_PROFILE and KCSAN_SANITIZE in scripts/Makefile.modfinal
Makefile: remove redundant tool coverage variables
kbuild: provide reasonable defaults for tool coverage
modules: Drop the .export_symbol section from the final modules
kconfig: use menu_list_for_each_sym() in sym_check_choice_deps()
kconfig: use sym_get_choice_menu() in conf_write_defconfig()
kconfig: add sym_get_choice_menu() helper
kconfig: turn defaults and additional prompt for choice members into error
kconfig: turn missing prompt for choice members into error
kconfig: turn conf_choice() into void function
kconfig: use linked list in sym_set_changed()
kconfig: gconf: use MENU_CHANGED instead of SYMBOL_CHANGED
kconfig: gconf: remove debug code
...
2024-05-18 12:39:20 -07:00
|
|
|
cmd_headergen = mkdir -p $(obj)/generated && $(PYTHON3) $(src)/registers/gen_header.py \
|
|
|
|
|
$(headergen-opts) --rnn $(src)/registers --xml $< c-defines > $@
|
2024-04-01 05:42:41 +03:00
|
|
|
|
|
|
|
|
$(obj)/generated/%.xml.h: $(src)/registers/adreno/%.xml \
|
|
|
|
|
$(src)/registers/adreno/adreno_common.xml \
|
|
|
|
|
$(src)/registers/adreno/adreno_pm4.xml \
|
|
|
|
|
$(src)/registers/freedreno_copyright.xml \
|
|
|
|
|
$(src)/registers/gen_header.py \
|
|
|
|
|
$(src)/registers/rules-fd.xsd \
|
|
|
|
|
FORCE
|
|
|
|
|
$(call if_changed,headergen)
|
|
|
|
|
|
|
|
|
|
$(obj)/generated/%.xml.h: $(src)/registers/display/%.xml \
|
|
|
|
|
$(src)/registers/freedreno_copyright.xml \
|
|
|
|
|
$(src)/registers/gen_header.py \
|
|
|
|
|
$(src)/registers/rules-fd.xsd \
|
|
|
|
|
FORCE
|
|
|
|
|
$(call if_changed,headergen)
|
|
|
|
|
|
|
|
|
|
ADRENO_HEADERS = \
|
|
|
|
|
generated/a2xx.xml.h \
|
|
|
|
|
generated/a3xx.xml.h \
|
|
|
|
|
generated/a4xx.xml.h \
|
|
|
|
|
generated/a5xx.xml.h \
|
|
|
|
|
generated/a6xx.xml.h \
|
2025-07-03 10:51:19 -07:00
|
|
|
generated/a6xx_descriptors.xml.h \
|
|
|
|
|
generated/a6xx_enums.xml.h \
|
|
|
|
|
generated/a6xx_perfcntrs.xml.h \
|
|
|
|
|
generated/a7xx_enums.xml.h \
|
|
|
|
|
generated/a7xx_perfcntrs.xml.h \
|
2024-04-01 05:42:41 +03:00
|
|
|
generated/a6xx_gmu.xml.h \
|
|
|
|
|
generated/adreno_common.xml.h \
|
|
|
|
|
generated/adreno_pm4.xml.h \
|
|
|
|
|
|
|
|
|
|
DISPLAY_HEADERS = \
|
|
|
|
|
generated/dsi_phy_7nm.xml.h \
|
|
|
|
|
generated/dsi_phy_10nm.xml.h \
|
|
|
|
|
generated/dsi_phy_14nm.xml.h \
|
|
|
|
|
generated/dsi_phy_20nm.xml.h \
|
|
|
|
|
generated/dsi_phy_28nm_8960.xml.h \
|
|
|
|
|
generated/dsi_phy_28nm.xml.h \
|
|
|
|
|
generated/dsi.xml.h \
|
|
|
|
|
generated/hdmi.xml.h \
|
|
|
|
|
generated/mdp4.xml.h \
|
|
|
|
|
generated/mdp5.xml.h \
|
|
|
|
|
generated/mdp_common.xml.h \
|
2024-09-21 11:17:29 +03:00
|
|
|
generated/mdss.xml.h \
|
2024-04-01 05:42:41 +03:00
|
|
|
generated/sfpb.xml.h
|
|
|
|
|
|
|
|
|
|
$(addprefix $(obj)/,$(adreno-y)): $(addprefix $(obj)/,$(ADRENO_HEADERS))
|
|
|
|
|
$(addprefix $(obj)/,$(msm-display-y)): $(addprefix $(obj)/,$(DISPLAY_HEADERS))
|
|
|
|
|
|
|
|
|
|
targets += $(ADRENO_HEADERS) $(DISPLAY_HEADERS)
|