| /linux-4.1.27/Documentation/EDID/ |
| D | HOWTO.txt | 9 - The graphics board is unable to detect any EDID data.
10 - The graphics board incorrectly forwards EDID data to the driver.
11 - The monitor sends no or bogus EDID data.
12 - A KVM sends its own EDID data instead of querying the connected monitor.
18 individually prepared or corrected EDID data set in the /lib/firmware
24 of the built-in binary EDID blobs and to facilitate the creation of
28 To create binary EDID and C source code files from the existing data
31 If you want to create your own EDID file, copy the file 1024x768.S,
33 Makefile. Please note that the EDID data structure expects the timing
40 EDID:
[all …]
|
| /linux-4.1.27/Documentation/fb/ |
| D | udlfb.txt | 22 Mode setting, EDID read, etc are other bulk or control transfers. Mode
59 DisplayLink chips (Alex and Ollie family). It will then attempt to read the EDID
129 edid If a valid EDID blob is written to this file (typically
130 by a udev rule), then udlfb will use this EDID as a
131 backup in case reading the actual EDID of the monitor
134 communicate their capabilities via EDID. Reading
135 this file returns the current EDID of the attached
137 useful to get the EDID of the attached monitor,
|
| D | intel810.txt | 49 - Supports EDID probing either by DDC/I2C or through the BIOS
96 be equal to hsync2. If EDID probing is successful, these will be
97 ignored and values will be taken from the EDID block.
105 rate. If EDID probing is successful, these will be ignored and values
106 will be taken from the EDID block.
194 supports I2C and has an EDID block, you can safely exclude hsync1, hsync2,
195 vsync1 and vsync2 parameters. These parameters will be taken from the EDID
|
| D | uvesafb.txt | 121 noedid Do not try to fetch and use EDID-provided modes.
132 EDID-provided values and BIOS defaults. Refer to your monitor's specs to get
|
| D | modedb.txt | 89 determined from its EDID. The version 1.3 of the EDID has extra 128-byte
|
| /linux-4.1.27/drivers/gpu/drm/ |
| D | Kconfig | 44 bool "Allow to specify an EDID data set instead of probing for it"
47 Say Y here, if you want to use EDID data to be loaded from the
50 monitor are unable to provide appropriate EDID data. Since this
53 EDID data are given in Documentation/EDID/HOWTO.txt.
|
| /linux-4.1.27/Documentation/devicetree/bindings/gpu/ |
| D | nvidia,tegra20-host1x.txt | 128 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
130 - nvidia,edid: supplies a binary EDID blob
154 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
156 - nvidia,edid: supplies a binary EDID blob
190 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
192 - nvidia,edid: supplies a binary EDID blob
218 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
220 - nvidia,edid: supplies a binary EDID blob
|
| D | st,stih4xx.txt | 71 - ddc: phandle of an I2C controller used for DDC EDID probing
|
| /linux-4.1.27/Documentation/devicetree/bindings/panel/ |
| D | simple-panel.txt | 7 - ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
|
| /linux-4.1.27/drivers/video/fbdev/riva/ |
| D | rivafb.h | 57 unsigned char *EDID; member
|
| D | fbdev.c | 1755 par->EDID = (unsigned char *)pedid; in riva_get_EDID_OF()
1777 riva_probe_i2c_connector(par, i, &par->EDID); in riva_get_EDID_i2c()
1778 if (par->EDID && !fb_parse_edid(par->EDID, &var)) { in riva_get_EDID_i2c()
1785 return (par->EDID) ? 1 : 0; in riva_get_EDID_i2c()
1844 fb_edid_to_monspecs(par->EDID, &info->monspecs); in riva_get_edidinfo()
2102 kfree(par->EDID); in rivafb_remove()
|
| /linux-4.1.27/Documentation/devicetree/bindings/video/bridge/ |
| D | ptn3460.txt | 8 - edid-emulation: The EDID emulation entry to use
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | diu.txt | 15 - edid : verbatim EDID data block describing attached display.
|
| /linux-4.1.27/Documentation/devicetree/bindings/fb/ |
| D | sm501fb.txt | 18 - edid : verbatim EDID data block describing attached display.
|
| /linux-4.1.27/Documentation/devicetree/bindings/drm/imx/ |
| D | hdmi.txt | 24 - ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
|
| D | fsl-imx-drm.txt | 65 - edid: verbatim EDID data block describing attached display.
|
| /linux-4.1.27/Documentation/devicetree/bindings/video/ |
| D | dw_hdmi-rockchip.txt | 18 - ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
|
| /linux-4.1.27/Documentation/devicetree/bindings/drm/bridge/ |
| D | dw_hdmi.txt | 22 - ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
|
| /linux-4.1.27/arch/arm/boot/dts/ |
| D | tegra30-colibri-eval-v3.dts | 63 /* DDC_CLOCK/DATA on X3 pin 15/16 (e.g. display EDID) */
|
| D | tegra30-apalis-eval.dts | 102 /* DDC: I2C2_SDA/SCL on MXM3 pin 205/207 (e.g. display EDID) */
|
| D | omap3-igep0020-common.dtsi | 198 * as EDID data.
|
| D | omap4-panda-common.dtsi | 411 * Display monitor features are burnt in their EEPROM as EDID data.
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | vivid.txt | 363 For HDMI inputs it is possible to set the EDID. By default a simple EDID
364 is provided. You can only set the EDID for HDMI inputs. Internally, however,
365 the EDID is shared between all HDMI inputs.
367 No interpretation is done of the EDID data.
410 An HDMI output has a valid EDID which can be obtained through VIDIOC_G_EDID.
680 Maximum EDID Blocks: determines how many EDID blocks the driver supports.
681 Note that the vivid driver does not actually interpret new EDID
682 data, it just stores it. It allows for up to 256 EDID blocks
|
| /linux-4.1.27/Documentation/acpi/ |
| D | video_extension.txt | 7 defining the video POST device, retrieving EDID information or to
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | Procfile.txt | 175 Shows ELD(EDID Like Data) info retrieved from the attached HDMI sink,
|
| /linux-4.1.27/Documentation/ |
| D | 00-INDEX | 34 EDID/
35 - directory with info on customizing EDID for broken gfx/displays.
|
| D | kernel-parameters.txt | 920 send no or incorrect EDID data sets. This parameter
921 allows to specify an EDID data set in the
923 Generic built-in EDID data sets are used, if one of
927 instructions how to build your own EDID data are
928 available in Documentation/EDID/HOWTO.txt. An EDID
930 if its name and a colon are prepended to the EDID
|
| /linux-4.1.27/drivers/video/fbdev/ |
| D | Kconfig | 41 bool "Enable firmware EDID"
45 This enables access to the EDID transferred from the firmware.
201 Generalized Timing Formula and the EDID parser. A few drivers rely
381 card. This is only I2C bus support, driver does not use EDID.
1027 only for getting EDID information from the attached display
1074 only for getting EDID information from the attached display
1486 only for getting EDID information from the attached display
|
| /linux-4.1.27/drivers/acpi/ |
| D | Kconfig | 146 such as defining the video POST device, retrieving EDID information,
|