Home
last modified time | relevance | path

Searched refs:EDID (Results 1 – 25 of 63) sorted by relevance

123

/OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/
H A Dvidioc-g-edid.rst13 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 …]
H A Dext-ctrls-dv.rst22 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
/OK3568_Linux_fs/kernel/Documentation/admin-guide/
H A Dedid.rst4 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 …]
/OK3568_Linux_fs/kernel/Documentation/fb/
H A Dudlfb.rst22 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,
H A Dintel810.rst54 - 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
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-support/colord/colord-native/
H A D0001-Move-the-function-cd_icc_create_from_edid-to-avoid-u.patch32 + * @edid: EDID data
35 + * Creates an ICC profile from EDID data.
102 - * @edid: EDID data
105 - * Creates an ICC profile from EDID data.
/OK3568_Linux_fs/buildroot/package/read-edid/
H A DConfig.in4 Read-edid is a pair of tools for reading the EDID from a
6 (except for newer ones with 256-byte EDID's - WiP), assuming
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-support/read-edid/
H A Dread-edid_3.0.2.bb1 SUMMARY = "A pair of tools for reading the EDID from a monitor"
3 EDID information from the monitor, and parse-edid, which turns \
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/display/bridge/
H A Danx6345.txt18 - edid : verbatim EDID data block describing attached
19 panel, only used when the panel has no EDID info.
H A Dptn3460.txt8 - edid-emulation: The EDID emulation entry to use
/OK3568_Linux_fs/u-boot/doc/device-tree-bindings/gpu/
H A Dnvidia,tegra20-host1x.txt128 - 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
214 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
216 - nvidia,edid: supplies a binary EDID blob
/OK3568_Linux_fs/u-boot/doc/
H A DREADME.video65 - edid=[0|1] - Enable use of DDC + EDID to get monitor info
67 1: Enabled. If valid EDID info was read from the monitor the EDID info will
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/display/tegra/
H A Dnvidia,tegra20-host1x.txt196 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
198 - nvidia,edid: supplies a binary EDID blob
222 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
224 - nvidia,edid: supplies a binary EDID blob
258 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
260 - nvidia,edid: supplies a binary EDID blob
301 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
303 - nvidia,edid: supplies a binary EDID blob
/OK3568_Linux_fs/buildroot/package/edid-decode/
H A DConfig.in6 Decode EDID data in human-readable format.
/OK3568_Linux_fs/kernel/Documentation/userspace-api/media/cec/
H A Dcec-ioc-adap-g-phys-addr.rst70 EDID of the sink.
72 For example, the EDID for each HDMI input of the TV will have a
/OK3568_Linux_fs/kernel/drivers/gpu/drm/
H A DKconfig36 bool "EDID function for DRM"
41 DRM EDID read and parse function.
180 bool "Allow to specify an EDID data set instead of probing for it"
183 Say Y here, if you want to use EDID data to be loaded from the
186 monitor are unable to provide appropriate EDID data. Since this
189 EDID data are given in Documentation/admin-guide/edid.rst.
/OK3568_Linux_fs/external/xserver/hw/xfree86/doc/
H A DREADME.modes49 generally comes from the EDID data in the monitor. Otherwise, the server
208 This returns the EDID data structure for the 'output' using the I2C bus
214 Once the EDID data has been fetched, this call applies the EDID data to the
217 RandR 1.2 EDID output properties.
222 Given an EDID data structure, this function computes a list of suitable
225 the EDID data.
/OK3568_Linux_fs/kernel/drivers/video/fbdev/riva/
H A Drivafb.h58 unsigned char *EDID; member
H A Dfbdev.c1749 par->EDID = (unsigned char *)pedid; in riva_get_EDID_OF()
1772 riva_probe_i2c_connector(par, i, &par->EDID); in riva_get_EDID_i2c()
1773 if (par->EDID && !fb_parse_edid(par->EDID, &var)) { in riva_get_EDID_i2c()
1780 return (par->EDID) ? 1 : 0; in riva_get_EDID_i2c()
1839 fb_edid_to_monspecs(par->EDID, &info->monspecs); in riva_get_edidinfo()
2086 kfree(par->EDID); in rivafb_remove()
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/powerpc/fsl/
H A Ddiu.txt13 - edid : verbatim EDID data block describing attached display.
/OK3568_Linux_fs/kernel/Documentation/gpu/
H A Dvkms.rst38 - Change output configuration: Plug/unplug screens, change EDID, allow changing
91 testing. Also needs support to specify the EDID.
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/display/
H A Dsm501fb.txt16 - edid : verbatim EDID data block describing attached display.
/OK3568_Linux_fs/u-boot/board/bachmann/ot1200/
H A DREADME20 are making use of EDID data stored in an i2c EEPROM.
/OK3568_Linux_fs/kernel/Documentation/admin-guide/media/
H A Dvivid.rst422 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 …]
/OK3568_Linux_fs/u-boot/arch/arm/dts/
H A Dtegra30-colibri.dts43 /* DDC_CLOCK/DATA on X3 pin 15/16 (e.g. display EDID) */

123