leandrof/linux
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
3816139c8a
linux/drivers/gpu/drm/nouveau/include/nvif/cl5070.h

101 lines
2.2 KiB
C
Raw Normal View History

drm/nouveau: fix bogus GPL-2 license header The bulk SPDX addition made all these files into GPL-2.0 licensed files. However the remainder of the project is MIT-licensed, these files (primarily header files) were simply missing the boiler plate and got caught up in the global update. Fixes: b24413180f5 (License cleanup: add SPDX GPL-2.0 license identifier to files with no license) Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu> Acked-by: Emil Velikov <emil.l.velikov@gmail.com> Acked-by: Karol Herbst <kherbst@redhat.com> Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2019-06-20 00:13:43 +00:00
/* SPDX-License-Identifier: MIT */
drm/nouveau/nvif: split out display interface definitions Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2015-11-08 00:44:19 +00:00
#ifndef __NVIF_CL5070_H__
#define __NVIF_CL5070_H__
#define NV50_DISP_MTHD 0x00
struct nv50_disp_mthd_v0 {
__u8 version;
#define NV50_DISP_SCANOUTPOS 0x00
__u8 method;
__u8 head;
__u8 pad03[5];
};
struct nv50_disp_scanoutpos_v0 {
__u8 version;
__u8 pad01[7];
__s64 time[2];
__u16 vblanks;
__u16 vblanke;
__u16 vtotal;
__u16 vline;
__u16 hblanks;
__u16 hblanke;
__u16 htotal;
__u16 hline;
};
struct nv50_disp_mthd_v1 {
__u8 version;
drm/nouveau/disp: introduce acquire/release display path methods These exist to give NVKM information on the set of display paths that the DD needs to be active at any given time. Previously, the supervisor attempted to determine this solely from OR state, but there's a few configurations where this information on its own isn't enough to determine the specific display paths in question: - ANX9805, where the PIOR protocol for both DP and TMDS is TMDS. - On a device using DCB Switched Outputs. - On GM20x and newer, with a crossbar between the SOR and macro links. After this commit, the DD tells NVKM *exactly* which display path it's attempting a modeset on. Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2017-05-19 13:59:35 +00:00
#define NV50_DISP_MTHD_V1_ACQUIRE 0x01
#define NV50_DISP_MTHD_V1_RELEASE 0x02
drm/nouveau/nvif: split out display interface definitions Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2015-11-08 00:44:19 +00:00
#define NV50_DISP_MTHD_V1_DAC_LOAD 0x11
#define NV50_DISP_MTHD_V1_SOR_HDA_ELD 0x21
#define NV50_DISP_MTHD_V1_SOR_HDMI_PWR 0x22
#define NV50_DISP_MTHD_V1_SOR_LVDS_SCRIPT 0x23
drm/nouveau/disp/sor/gf119-: add method to control mst enable Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2016-11-04 07:20:35 +00:00
#define NV50_DISP_MTHD_V1_SOR_DP_MST_LINK 0x25
drm/nouveau/disp/sor/gf119-: add method to program mst payload information Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2016-11-04 07:20:35 +00:00
#define NV50_DISP_MTHD_V1_SOR_DP_MST_VCPI 0x26
drm/nouveau/nvif: split out display interface definitions Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2015-11-08 00:44:19 +00:00
__u8 method;
__u16 hasht;
__u16 hashm;
__u8 pad06[2];
};
drm/nouveau/disp: introduce acquire/release display path methods These exist to give NVKM information on the set of display paths that the DD needs to be active at any given time. Previously, the supervisor attempted to determine this solely from OR state, but there's a few configurations where this information on its own isn't enough to determine the specific display paths in question: - ANX9805, where the PIOR protocol for both DP and TMDS is TMDS. - On a device using DCB Switched Outputs. - On GM20x and newer, with a crossbar between the SOR and macro links. After this commit, the DD tells NVKM *exactly* which display path it's attempting a modeset on. Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2017-05-19 13:59:35 +00:00
struct nv50_disp_acquire_v0 {
__u8 version;
__u8 or;
__u8 link;
drm/nouveau/disp: provide hint to OR allocation about HDA requirements Will be used by a subsequent commit to influence SOR allocation policy. Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2020-06-03 01:37:56 +00:00
__u8 hda;
__u8 pad04[4];
drm/nouveau/disp: introduce acquire/release display path methods These exist to give NVKM information on the set of display paths that the DD needs to be active at any given time. Previously, the supervisor attempted to determine this solely from OR state, but there's a few configurations where this information on its own isn't enough to determine the specific display paths in question: - ANX9805, where the PIOR protocol for both DP and TMDS is TMDS. - On a device using DCB Switched Outputs. - On GM20x and newer, with a crossbar between the SOR and macro links. After this commit, the DD tells NVKM *exactly* which display path it's attempting a modeset on. Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2017-05-19 13:59:35 +00:00
};
drm/nouveau/nvif: split out display interface definitions Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2015-11-08 00:44:19 +00:00
struct nv50_disp_dac_load_v0 {
__u8 version;
__u8 load;
__u8 pad02[2];
__u32 data;
};
struct nv50_disp_sor_hda_eld_v0 {
__u8 version;
__u8 pad01[7];
__u8 data[];
};
struct nv50_disp_sor_hdmi_pwr_v0 {
__u8 version;
__u8 state;
__u8 max_ac_packet;
__u8 rekey;
drm/nouveau/disp/g84-: Extend NVKM HDMI power control method to set InfoFrames The nouveau driver, in the Linux 3.7 days, used to try and set the AVI InfoFrame based on the selected display mode. These days, it uses a fixed set of InfoFrames. Start to correct that, by providing a mechanism whereby InfoFrame data may be passed to the NVKM functions that do the actual configuration. At this point, only establish the new parameters and their parsing, don't actually use the data anywhere yet (since it's not supplied anywhere). Signed-off-by: Alastair Bridgewater <alastair.bridgewater@gmail.com> Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2017-04-11 17:11:17 +00:00
__u8 avi_infoframe_length;
__u8 vendor_infoframe_length;
drm/nouveau/disp: add a way to configure scrambling/tmds for hdmi 2.0 High pixel clocks are required to use a 40 TMDS divider instead of 10, and even low ones may optionally use scrambling depending on device support. Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu> Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2018-09-04 00:57:33 +00:00
#define NV50_DISP_SOR_HDMI_PWR_V0_SCDC_SCRAMBLE (1 << 0)
#define NV50_DISP_SOR_HDMI_PWR_V0_SCDC_DIV_BY_4 (1 << 1)
__u8 scdc;
__u8 pad07[1];
drm/nouveau/nvif: split out display interface definitions Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2015-11-08 00:44:19 +00:00
};
struct nv50_disp_sor_lvds_script_v0 {
__u8 version;
__u8 pad01[1];
__u16 script;
__u8 pad04[4];
};
drm/nouveau/disp/sor/gf119-: add method to control mst enable Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2016-11-04 07:20:35 +00:00
struct nv50_disp_sor_dp_mst_link_v0 {
__u8 version;
__u8 state;
__u8 pad02[6];
};
drm/nouveau/disp/sor/gf119-: add method to program mst payload information Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2016-11-04 07:20:35 +00:00
struct nv50_disp_sor_dp_mst_vcpi_v0 {
__u8 version;
__u8 pad01[1];
__u8 start_slot;
__u8 num_slots;
__u16 pbn;
__u16 aligned_pbn;
};
drm/nouveau/nvif: split out display interface definitions Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
2015-11-08 00:44:19 +00:00
#endif
Reference in New Issue Copy Permalink