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 21:07:57 +07:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0 */
|
2012-07-31 13:16:21 +07:00
|
|
|
#ifndef __NOUVEAU_DISPLAY_H__
|
|
|
|
|
#define __NOUVEAU_DISPLAY_H__
|
2016-05-20 06:22:55 +07:00
|
|
|
#include "nouveau_drv.h"
|
2018-05-08 17:39:47 +07:00
|
|
|
#include <nvif/disp.h>
|
2012-07-31 13:16:21 +07:00
|
|
|
|
|
|
|
|
struct nouveau_framebuffer {
|
|
|
|
|
struct drm_framebuffer base;
|
|
|
|
|
struct nouveau_bo *nvbo;
|
2017-11-01 00:56:19 +07:00
|
|
|
struct nouveau_vma *vma;
|
2014-08-10 01:10:19 +07:00
|
|
|
u32 r_handle;
|
2012-07-31 13:16:21 +07:00
|
|
|
u32 r_format;
|
|
|
|
|
u32 r_pitch;
|
2014-08-10 01:10:22 +07:00
|
|
|
struct nvif_object h_base[4];
|
|
|
|
|
struct nvif_object h_core;
|
2012-07-31 13:16:21 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static inline struct nouveau_framebuffer *
|
|
|
|
|
nouveau_framebuffer(struct drm_framebuffer *fb)
|
|
|
|
|
{
|
|
|
|
|
return container_of(fb, struct nouveau_framebuffer, base);
|
|
|
|
|
}
|
|
|
|
|
|
2016-11-04 14:20:35 +07:00
|
|
|
int nouveau_framebuffer_new(struct drm_device *,
|
|
|
|
|
const struct drm_mode_fb_cmd2 *,
|
|
|
|
|
struct nouveau_bo *, struct nouveau_framebuffer **);
|
2012-07-31 13:16:21 +07:00
|
|
|
|
|
|
|
|
struct nouveau_page_flip_state {
|
|
|
|
|
struct list_head head;
|
|
|
|
|
struct drm_pending_vblank_event *event;
|
2016-06-07 21:07:53 +07:00
|
|
|
struct drm_crtc *crtc;
|
|
|
|
|
int bpp, pitch;
|
2012-07-31 13:16:21 +07:00
|
|
|
u64 offset;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct nouveau_display {
|
|
|
|
|
void *priv;
|
|
|
|
|
void (*dtor)(struct drm_device *);
|
|
|
|
|
int (*init)(struct drm_device *);
|
|
|
|
|
void (*fini)(struct drm_device *);
|
|
|
|
|
|
2018-05-08 17:39:47 +07:00
|
|
|
struct nvif_disp disp;
|
2014-08-10 01:10:19 +07:00
|
|
|
|
2012-07-31 13:16:21 +07:00
|
|
|
struct drm_property *dithering_mode;
|
|
|
|
|
struct drm_property *dithering_depth;
|
|
|
|
|
struct drm_property *underscan_property;
|
|
|
|
|
struct drm_property *underscan_hborder_property;
|
|
|
|
|
struct drm_property *underscan_vborder_property;
|
|
|
|
|
/* not really hue and saturation: */
|
|
|
|
|
struct drm_property *vibrant_hue_property;
|
|
|
|
|
struct drm_property *color_vibrance_property;
|
2016-11-04 14:20:36 +07:00
|
|
|
|
|
|
|
|
struct drm_atomic_state *suspend;
|
2012-07-31 13:16:21 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static inline struct nouveau_display *
|
|
|
|
|
nouveau_display(struct drm_device *dev)
|
|
|
|
|
{
|
|
|
|
|
return nouveau_drm(dev)->display;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
int nouveau_display_create(struct drm_device *dev);
|
|
|
|
|
void nouveau_display_destroy(struct drm_device *dev);
|
|
|
|
|
int nouveau_display_init(struct drm_device *dev);
|
2016-11-04 14:20:35 +07:00
|
|
|
void nouveau_display_fini(struct drm_device *dev, bool suspend);
|
2014-10-02 10:22:27 +07:00
|
|
|
int nouveau_display_suspend(struct drm_device *dev, bool runtime);
|
|
|
|
|
void nouveau_display_resume(struct drm_device *dev, bool runtime);
|
2015-09-24 23:35:31 +07:00
|
|
|
int nouveau_display_vblank_enable(struct drm_device *, unsigned int);
|
|
|
|
|
void nouveau_display_vblank_disable(struct drm_device *, unsigned int);
|
drm/vblank: drop the mode argument from drm_calc_vbltimestamp_from_scanoutpos
If we restrict this helper to only kms drivers (which is the case) we
can look up the correct mode easily ourselves. But it's a bit tricky:
- All legacy drivers look at crtc->hwmode. But that is updated already
at the beginning of the modeset helper, which means when we disable
a pipe. Hence the final timestamps might be a bit off. But since
this is an existing bug I'm not going to change it, but just try to
be bug-for-bug compatible with the current code. This only applies
to radeon&amdgpu.
- i915 tries to get it perfect by updating crtc->hwmode when the pipe
is off (i.e. vblank->enabled = false).
- All other atomic drivers look at crtc->state->adjusted_mode. Those
that look at state->requested_mode simply don't adjust their mode,
so it's the same. That has two problems: Accessing crtc->state from
interrupt handling code is unsafe, and it's updated before we shut
down the pipe. For nonblocking modesets it's even worse.
For atomic drivers try to implement what i915 does. To do that we add
a new hwmode field to the vblank structure, and update it from
drm_calc_timestamping_constants(). For atomic drivers that's called
from the right spot by the helper library already, so all fine. But
for safety let's enforce that.
For legacy driver this function is only called at the end (oh the
fun), which is broken, so again let's not bother and just stay
bug-for-bug compatible.
The benefit is that we can use drm_calc_vbltimestamp_from_scanoutpos
directly to implement ->get_vblank_timestamp in every driver, deleting
a lot of code.
v2: Completely new approach, trying to mimick the i915 solution.
v3: Fixup kerneldoc.
v4: Drop the WARN_ON to check that the vblank is off, atomic helpers
currently unconditionally call this. Recomputing the same stuff should
be harmless.
v5: Fix typos and move misplaced hunks to the right patches (Neil).
v6: Undo hunk movement (kbuild).
Cc: Mario Kleiner <mario.kleiner@tuebingen.mpg.de>
Cc: Eric Anholt <eric@anholt.net>
Cc: Rob Clark <robdclark@gmail.com>
Cc: linux-arm-msm@vger.kernel.org
Cc: freedreno@lists.freedesktop.org
Cc: Alex Deucher <alexander.deucher@amd.com>
Cc: Christian König <christian.koenig@amd.com>
Cc: Ben Skeggs <bskeggs@redhat.com>
Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
Acked-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20170509140329.24114-4-daniel.vetter@ffwll.ch
2017-05-09 21:03:28 +07:00
|
|
|
bool nouveau_display_scanoutpos(struct drm_device *, unsigned int,
|
|
|
|
|
bool, int *, int *, ktime_t *,
|
|
|
|
|
ktime_t *, const struct drm_display_mode *);
|
2012-07-31 13:16:21 +07:00
|
|
|
|
|
|
|
|
int nouveau_crtc_page_flip(struct drm_crtc *crtc, struct drm_framebuffer *fb,
|
2013-07-23 08:49:58 +07:00
|
|
|
struct drm_pending_vblank_event *event,
|
2017-03-23 04:50:50 +07:00
|
|
|
uint32_t page_flip_flags,
|
|
|
|
|
struct drm_modeset_acquire_ctx *ctx);
|
2012-07-31 13:16:21 +07:00
|
|
|
int nouveau_finish_page_flip(struct nouveau_channel *,
|
|
|
|
|
struct nouveau_page_flip_state *);
|
|
|
|
|
|
|
|
|
|
int nouveau_display_dumb_create(struct drm_file *, struct drm_device *,
|
|
|
|
|
struct drm_mode_create_dumb *args);
|
|
|
|
|
int nouveau_display_dumb_map_offset(struct drm_file *, struct drm_device *,
|
|
|
|
|
u32 handle, u64 *offset);
|
|
|
|
|
|
|
|
|
|
void nouveau_hdmi_mode_set(struct drm_encoder *, struct drm_display_mode *);
|
|
|
|
|
|
|
|
|
|
#ifdef CONFIG_DRM_NOUVEAU_BACKLIGHT
|
|
|
|
|
extern int nouveau_backlight_init(struct drm_device *);
|
|
|
|
|
extern void nouveau_backlight_exit(struct drm_device *);
|
drm/nouveau/bl: Assign different names to interfaces
Currently, every backlight interface created by Nouveau uses the same name,
nv_backlight. This leads to a sysfs warning as it tries to create an already
existing folder. This patch adds a incremented number to the name, but keeps
the initial name as nv_backlight, to avoid possibly breaking userspace; the
second interface will be named nv_backlight1, and so on.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=86539
v2:
* Switch to using ida for generating unique IDs, as suggested by Ilia Mirkin;
* Allocate backlight name on the stack, as suggested by Ilia Mirkin;
* Move `nouveau_get_backlight_name()` to avoid forward declaration, as
suggested by Ilia Mirkin;
* Fix reference to bug report formatting, as reported by Nick Tenney.
v3:
* Define a macro for the size of the backlight name, to avoid defining
it multiple times;
* Use snprintf in place of sprintf.
v4:
* Do not create similarly named interfaces when reaching the maximum
amount of unique names, but fail instead, as pointed out by Lukas Wunner
Signed-off-by: Pierre Moreau <pierre.morrow@free.fr>
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2016-12-08 06:57:08 +07:00
|
|
|
extern void nouveau_backlight_ctor(void);
|
|
|
|
|
extern void nouveau_backlight_dtor(void);
|
2012-07-31 13:16:21 +07:00
|
|
|
#else
|
|
|
|
|
static inline int
|
|
|
|
|
nouveau_backlight_init(struct drm_device *dev)
|
|
|
|
|
{
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static inline void
|
|
|
|
|
nouveau_backlight_exit(struct drm_device *dev) {
|
|
|
|
|
}
|
drm/nouveau/bl: Assign different names to interfaces
Currently, every backlight interface created by Nouveau uses the same name,
nv_backlight. This leads to a sysfs warning as it tries to create an already
existing folder. This patch adds a incremented number to the name, but keeps
the initial name as nv_backlight, to avoid possibly breaking userspace; the
second interface will be named nv_backlight1, and so on.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=86539
v2:
* Switch to using ida for generating unique IDs, as suggested by Ilia Mirkin;
* Allocate backlight name on the stack, as suggested by Ilia Mirkin;
* Move `nouveau_get_backlight_name()` to avoid forward declaration, as
suggested by Ilia Mirkin;
* Fix reference to bug report formatting, as reported by Nick Tenney.
v3:
* Define a macro for the size of the backlight name, to avoid defining
it multiple times;
* Use snprintf in place of sprintf.
v4:
* Do not create similarly named interfaces when reaching the maximum
amount of unique names, but fail instead, as pointed out by Lukas Wunner
Signed-off-by: Pierre Moreau <pierre.morrow@free.fr>
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2016-12-08 06:57:08 +07:00
|
|
|
|
|
|
|
|
static inline void
|
|
|
|
|
nouveau_backlight_ctor(void) {
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static inline void
|
|
|
|
|
nouveau_backlight_dtor(void) {
|
|
|
|
|
}
|
2012-07-31 13:16:21 +07:00
|
|
|
#endif
|
|
|
|
|
|
2016-11-04 14:20:36 +07:00
|
|
|
struct drm_framebuffer *
|
|
|
|
|
nouveau_user_framebuffer_create(struct drm_device *, struct drm_file *,
|
|
|
|
|
const struct drm_mode_fb_cmd2 *);
|
2012-07-31 13:16:21 +07:00
|
|
|
#endif
|