| /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``,
60 ``start_block``, ``blocks`` and ``edid`` fields, zero the ``reserved``
61 array and call :ref:`VIDIOC_G_EDID <VIDIOC_G_EDID>`. The current EDID from block
63 ``edid`` points to. The ``edid`` pointer must point to memory at least
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
[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
|
| /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
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | adv7604.yaml | 36 - enum: [ avlink, cec, infoframe, esdp, dpp, afe, rep, edid, hdmi, test, cp, vdp ]
37 - enum: [ avlink, cec, infoframe, esdp, dpp, afe, rep, edid, hdmi, test, cp, vdp ]
38 - enum: [ avlink, cec, infoframe, esdp, dpp, afe, rep, edid, hdmi, test, cp, vdp ]
39 - enum: [ avlink, cec, infoframe, esdp, dpp, afe, rep, edid, hdmi, test, cp, vdp ]
40 - enum: [ avlink, cec, infoframe, esdp, dpp, afe, rep, edid, hdmi, test, cp, vdp ]
41 - enum: [ avlink, cec, infoframe, esdp, dpp, afe, rep, edid, hdmi, test, cp, vdp ]
42 - enum: [ avlink, cec, infoframe, esdp, dpp, afe, rep, edid, hdmi, test, cp, vdp ]
43 - enum: [ avlink, cec, infoframe, esdp, dpp, afe, rep, edid, hdmi, test, cp, vdp ]
44 - enum: [ avlink, cec, infoframe, esdp, dpp, afe, rep, edid, hdmi, test, cp, vdp ]
45 - enum: [ avlink, cec, infoframe, esdp, dpp, afe, rep, edid, hdmi, test, cp, vdp ]
[all …]
|
| D | adv748x.yaml | 38 - enum: [ dpll, cp, hdmi, edid, repeater, infoframe, cbus, cec, sdp, txa, txb ]
39 - enum: [ dpll, cp, hdmi, edid, repeater, infoframe, cbus, cec, sdp, txa, txb ]
40 - enum: [ dpll, cp, hdmi, edid, repeater, infoframe, cbus, cec, sdp, txa, txb ]
41 - enum: [ dpll, cp, hdmi, edid, repeater, infoframe, cbus, cec, sdp, txa, txb ]
42 - enum: [ dpll, cp, hdmi, edid, repeater, infoframe, cbus, cec, sdp, txa, txb ]
43 - enum: [ dpll, cp, hdmi, edid, repeater, infoframe, cbus, cec, sdp, txa, txb ]
44 - enum: [ dpll, cp, hdmi, edid, repeater, infoframe, cbus, cec, sdp, txa, txb ]
45 - enum: [ dpll, cp, hdmi, edid, repeater, infoframe, cbus, cec, sdp, txa, txb ]
46 - enum: [ dpll, cp, hdmi, edid, repeater, infoframe, cbus, cec, sdp, txa, txb ]
47 - enum: [ dpll, cp, hdmi, edid, repeater, infoframe, cbus, cec, sdp, txa, txb ]
[all …]
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | diu.txt | 13 - edid : verbatim EDID data block describing attached display.
31 edid = [edid-data];
|
| /Documentation/devicetree/bindings/display/ |
| D | sm501fb.txt | 16 - edid : verbatim EDID data block describing attached display.
31 edid = [edid-data];
|
| /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
139 edid If a valid EDID blob is written to this file (typically
140 by a udev rule), then udlfb will use this EDID as a
141 backup in case reading the actual EDID of the monitor
144 communicate their capabilities via EDID. Reading
145 this file returns the current EDID of the attached
147 useful to get the EDID of the attached monitor,
148 which can be passed to utilities like parse-edid.
|
| 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
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | nxp,ptn3460.yaml | 20 edid-emulation:
23 The EDID emulation entry to use
63 - edid-emulation
81 edid-emulation = <5>;
|
| D | adi,adv7533.yaml | 45 - const: edid
144 * The EDID page will be accessible on address 0x66 on the I2C
148 reg-names = "main", "edid";
|
| D | adi,adv7511.yaml | 44 - const: edid
188 * The EDID page will be accessible on address 0x66 on the I2C
192 reg-names = "main", "edid";
|
| /Documentation/devicetree/bindings/display/tegra/ |
| D | nvidia,tegra20-hdmi.yaml | 69 description: phandle of an I2C controller used for DDC EDID
77 nvidia,edid:
78 description: supplies a binary EDID blob
|
| D | nvidia,tegra20-dsi.yaml | 65 description: phandle of an I2C controller used for DDC EDID
73 nvidia,edid:
74 description: supplies a binary EDID blob
|
| D | nvidia,tegra20-dc.yaml | 116 description: phandle of an I2C controller used for DDC EDID probing
122 nvidia,edid:
124 description: supplies a binary EDID blob
|
| D | nvidia,tegra124-sor.yaml | 75 description: phandle of an I2C controller used for DDC EDID
83 nvidia,edid:
84 description: supplies a binary EDID blob
|
| /Documentation/admin-guide/media/ |
| D | cec.rst | 207 EDID changes, you can use ``cec-ctl`` with the ``-E`` option::
209 cec-ctl -E /sys/class/drm/card0-DP-1/edid
212 you which output is used) and it will poll for changes to the EDID and update
218 @reboot /usr/local/bin/cec-ctl -E /sys/class/drm/card0-DP-1/edid
220 This only works for display drivers that expose the EDID in ``/sys/class/drm``,
414 read the EDIDs and (for the HDMI Input port) to set the EDID.
416 By default userspace is responsible to set the EDID for the HDMI Input
418 module option is set, then the driver will take care of setting the EDID
422 it will fall back to an EDID that just reports 1080p60.
453 A three character manufacturer name that is used in the EDID for the HDMI
[all …]
|
| D | vivid.rst | 431 For HDMI inputs it is possible to set the EDID. By default a simple EDID
432 is provided. You can only set the EDID for HDMI inputs. Internally, however,
433 the EDID is shared between all HDMI inputs.
435 No interpretation is done of the EDID data with the exception of the
439 reduced to 15) since that's the limitation of the EDID physical address.
482 An HDMI output has a valid EDID which can be obtained through VIDIOC_G_EDID.
485 reduced to 15) since that's the limitation of the EDID physical address. See
847 - Maximum EDID Blocks:
849 determines how many EDID blocks the driver supports.
850 Note that the vivid driver does not actually interpret new EDID
[all …]
|
| /Documentation/devicetree/bindings/display/imx/ |
| D | fsl-imx-drm.txt | 122 - edid: verbatim EDID data block describing attached display.
134 edid = [edid-data];
|
| /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
|
| /Documentation/devicetree/bindings/display/connector/ |
| D | vga-connector.yaml | 19 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
|
| D | hdmi-connector.yaml | 32 description: phandle link to the I2C controller used for DDC EDID probing
|
| /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
|
| /Documentation/translations/zh_CN/admin-guide/ |
| D | index.rst | 91 * edid
|