| /linux-5.19.10/Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-edid.rst | 13 VIDIOC_G_EDID - VIDIOC_S_EDID - VIDIOC_SUBDEV_G_EDID - VIDIOC_SUBDEV_S_EDID - Get or set the EDID o…
46 These ioctls can be used to get or set an EDID associated with an input
56 pad of the subdevice. If there is no EDID support for the given ``pad``
59 To get the EDID data the application has to fill in the ``pad``,
61 array and call :ref:`VIDIOC_G_EDID <VIDIOC_G_EDID>`. The current EDID from block
67 ``blocks`` to the actual number of blocks. If there are no EDID blocks
75 total number of available EDID blocks and it will return 0 without
76 copying any data. This is an easy way to discover how many EDID blocks
81 If there are no EDID blocks available at all, then
84 To set the EDID blocks of a receiver the application has to fill in the
[all …]
|
| D | ext-ctrls-dv.rst | 22 can still be active when it comes to EDID (Extended Display
25 device to do the fairly slow EDID/HDCP handling in advance. This allows
42 Many connectors have a hotplug pin which is high if EDID information
61 will attempt to read the EDID. If set, then the transmitter has read
128 eeprom which contains EDID information, such that the source can
129 read the EDID even if the sink is in standby/power off. Each bit
|
| /linux-5.19.10/Documentation/admin-guide/ |
| D | edid.rst | 4 EDID title
16 - The graphics board is unable to detect any EDID data.
17 - The graphics board incorrectly forwards EDID data to the driver.
18 - The monitor sends no or bogus EDID data.
19 - A KVM sends its own EDID data instead of querying the connected monitor.
26 individually prepared or corrected EDID data set in the /lib/firmware
32 of the built-in binary EDID blobs and to facilitate the creation of
36 To create binary EDID and C source code files from the existing data
39 If you want to create your own EDID file, copy the file 1024x768.S,
41 Makefile. Please note that the EDID data structure expects the timing
[all …]
|
| /linux-5.19.10/Documentation/fb/ |
| D | udlfb.rst | 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
132 edid If a valid EDID blob is written to this file (typically
133 by a udev rule), then udlfb will use this EDID as a
134 backup in case reading the actual EDID of the monitor
137 communicate their capabilities via EDID. Reading
138 this file returns the current EDID of the attached
140 useful to get the EDID of the attached monitor,
|
| D | intel810.rst | 54 - Supports EDID probing either by DDC/I2C or through the BIOS
102 be equal to hsync2. If EDID probing is successful, these will be
103 ignored and values will be taken from the EDID block.
111 rate. If EDID probing is successful, these will be ignored and values
112 will be taken from the EDID block.
201 supports I2C and has an EDID block, you can safely exclude hsync1, hsync2,
202 vsync1 and vsync2 parameters. These parameters will be taken from the EDID
|
| D | uvesafb.rst | 125 noedid Do not try to fetch and use EDID-provided modes.
136 EDID-provided values and BIOS defaults. Refer to your monitor's specs to get
|
| /linux-5.19.10/drivers/video/fbdev/riva/ |
| D | rivafb.h | 58 unsigned char *EDID; member
|
| D | fbdev.c | 1748 par->EDID = (unsigned char *)pedid; in riva_get_EDID_OF()
1771 riva_probe_i2c_connector(par, i, &par->EDID); in riva_get_EDID_i2c()
1772 if (par->EDID && !fb_parse_edid(par->EDID, &var)) { in riva_get_EDID_i2c()
1779 return (par->EDID) ? 1 : 0; in riva_get_EDID_i2c()
1838 fb_edid_to_monspecs(par->EDID, &info->monspecs); in riva_get_edidinfo()
2085 kfree(par->EDID); in rivafb_remove()
|
| /linux-5.19.10/Documentation/devicetree/bindings/display/connector/ |
| D | vga-connector.yaml | 19 description: phandle link to the I2C controller used for DDC EDID probing
|
| D | hdmi-connector.yaml | 32 description: phandle link to the I2C controller used for DDC EDID probing
|
| D | dvi-connector.yaml | 23 description: phandle link to the I2C controller used for DDC EDID probing
|
| /linux-5.19.10/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | diu.txt | 13 - edid : verbatim EDID data block describing attached display.
|
| /linux-5.19.10/Documentation/userspace-api/media/cec/ |
| D | cec-ioc-adap-g-phys-addr.rst | 70 EDID of the sink.
72 For example, the EDID for each HDMI input of the TV will have a
|
| /linux-5.19.10/Documentation/devicetree/bindings/display/panel/ |
| D | panel-edp.yaml | 7 title: Probeable (via DP AUX / EDID) eDP Panels with simple poweron sequences
22 information provided by the DP AUX bus (including the EDID) to identify
32 the operating system will lookup the panel in a table (based on EDID
|
| /linux-5.19.10/Documentation/devicetree/bindings/display/ |
| D | sm501fb.txt | 16 - edid : verbatim EDID data block describing attached display.
|
| D | brcm,bcm2835-hdmi.yaml | 37 Phandle of the I2C controller used for DDC EDID probing
|
| D | brcm,bcm2711-hdmi.yaml | 77 Phandle of the I2C controller used for DDC EDID probing
|
| /linux-5.19.10/Documentation/devicetree/bindings/display/tegra/ |
| D | nvidia,tegra20-host1x.txt | 263 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
265 - nvidia,edid: supplies a binary EDID blob
295 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
297 - nvidia,edid: supplies a binary EDID blob
336 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
338 - nvidia,edid: supplies a binary EDID blob
380 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
382 - nvidia,edid: supplies a binary EDID blob
|
| /linux-5.19.10/Documentation/devicetree/bindings/display/bridge/ |
| D | anx6345.yaml | 47 May be omitted if EDID works reliably.
|
| D | nxp,ptn3460.yaml | 23 The EDID emulation entry to use
|
| D | megachips-stdpxxxx-ge-b850v3-fw.txt | 17 hardware are EDID, HPD, and interrupts.
|
| /linux-5.19.10/Documentation/admin-guide/media/ |
| D | vivid.rst | 422 For HDMI inputs it is possible to set the EDID. By default a simple EDID
423 is provided. You can only set the EDID for HDMI inputs. Internally, however,
424 the EDID is shared between all HDMI inputs.
426 No interpretation is done of the EDID data with the exception of the
430 reduced to 15) since that's the limitation of the EDID physical address.
473 An HDMI output has a valid EDID which can be obtained through VIDIOC_G_EDID.
476 reduced to 15) since that's the limitation of the EDID physical address. See
824 - Maximum EDID Blocks:
826 determines how many EDID blocks the driver supports.
827 Note that the vivid driver does not actually interpret new EDID
[all …]
|
| /linux-5.19.10/drivers/gpu/drm/ |
| D | Kconfig | 161 bool "Allow to specify an EDID data set instead of probing for it"
164 Say Y here, if you want to use EDID data to be loaded from the
167 monitor are unable to provide appropriate EDID data. Since this
170 EDID data are given in Documentation/admin-guide/edid.rst.
|
| /linux-5.19.10/arch/arm/boot/dts/ |
| D | tegra30-colibri-eval-v3.dts | 77 /* DDC_CLOCK/DATA on X3 pin 15/16 (e.g. display EDID) */
|
| D | tegra20-colibri-iris.dts | 141 /* DDC_CLOCK/DATA on X3 pin 15/16 (e.g. display EDID) */
|