| /linux/drivers/gpu/drm/i915/display/ |
| A D | intel_dp.c | 1184 intel_dp->compliance.test_link_rate; in intel_dp_adjust_compliance_config()
1186 intel_dp->compliance.test_lane_count; in intel_dp_adjust_compliance_config()
3247 intel_dp->compliance.test_data.bpc = 6; in intel_dp_autotest_video_pattern()
3250 intel_dp->compliance.test_data.bpc = 8; in intel_dp_autotest_video_pattern()
3260 intel_dp->compliance.test_active = true; in intel_dp_autotest_video_pattern()
3307 intel_dp->compliance.test_active = true; in intel_dp_autotest_edid()
3437 &intel_dp->compliance.test_data.phytest; in intel_dp_process_phy_request()
3468 &intel_dp->compliance.test_data.phytest; in intel_dp_autotest_phy_pattern()
3476 intel_dp->compliance.test_active = true; in intel_dp_autotest_phy_pattern()
4010 memset(&intel_dp->compliance, 0, sizeof(intel_dp->compliance)); in intel_dp_short_pulse()
[all …]
|
| A D | intel_display_debugfs.c | 1442 intel_dp->compliance.test_active = true; in i915_displayport_test_active_write()
1444 intel_dp->compliance.test_active = false; in i915_displayport_test_active_write()
1478 if (intel_dp->compliance.test_active) in i915_displayport_test_active_show()
1528 if (intel_dp->compliance.test_type == in i915_displayport_test_data_show()
1531 intel_dp->compliance.test_data.edid); in i915_displayport_test_data_show()
1532 else if (intel_dp->compliance.test_type == in i915_displayport_test_data_show()
1535 intel_dp->compliance.test_data.hdisplay); in i915_displayport_test_data_show()
1537 intel_dp->compliance.test_data.vdisplay); in i915_displayport_test_data_show()
1539 intel_dp->compliance.test_data.bpc); in i915_displayport_test_data_show()
1540 } else if (intel_dp->compliance.test_type == in i915_displayport_test_data_show()
[all …]
|
| A D | g4x_dp.c | 1159 if (intel_dp->compliance.test_active && in intel_dp_hotplug()
1160 intel_dp->compliance.test_type == DP_TEST_LINK_PHY_TEST_PATTERN) { in intel_dp_hotplug()
|
| /linux/Documentation/userspace-api/media/cec/ |
| A D | cec-intro.rst | 39 - cec-compliance: does a CEC compliance test of a remote CEC device to
|
| /linux/Documentation/ABI/testing/ |
| A D | sysfs-bus-usb-lvstest | 52 Write to this node to set the port to compliance mode to test
60 compliance mode needed to be explicitly enabled.
|
| /linux/drivers/staging/media/tegra-video/ |
| A D | TODO | 5 * Make sure v4l2-compliance tests pass with all of the above implementations.
|
| /linux/Documentation/features/debug/debug-vm-pgtable/ |
| A D | arch-support.txt | 4 # description: arch supports pgtable tests for semantics compliance
|
| /linux/drivers/staging/media/meson/vdec/ |
| A D | TODO | 2 decoders is finalized, as well as the corresponding compliance tests.
|
| /linux/Documentation/driver-api/media/ |
| A D | maintainer-entry-profile.rst | 104 There is a set of compliance tools at https://git.linuxtv.org/v4l-utils.git/
111 V4L2 drivers\ [3]_ ``v4l2-compliance``
113 CEC drivers ``cec-compliance``
116 .. [3] The ``v4l2-compliance`` also covers the media controller usage inside
|
| /linux/drivers/staging/media/zoran/ |
| A D | TODO | 18 - fix the v4l compliance "TRY_FMT cannot handle an invalid pixelformat"
|
| /linux/Documentation/networking/device_drivers/wifi/intel/ |
| A D | ipw2100.rst | 46 provide test data to prove regional and local compliance to regional and
50 radio operation and to ensure electromagnetic compliance (EMC). These
61 ensuring the regulatory compliance of the products, (ii) Intel will bear
64 the warranty and/or issues arising from regulatory non-compliance, and
|
| A D | ipw2200.rst | 60 provide test data to prove regional and local compliance to regional and
64 radio operation and to ensure electromagnetic compliance (EMC). These
75 ensuring the regulatory compliance of the products, (ii) Intel will bear
78 the warranty and/or issues arising from regulatory non-compliance, and
|
| /linux/Documentation/process/ |
| A D | kernel-enforcement-statement.rst | 43 eliminate any uncertainty about our expectations regarding compliance or
48 Finally, once a non-compliance issue is resolved, we hope the user will feel
|
| /linux/Documentation/devicetree/bindings/display/bridge/ |
| A D | ite,it6505.yaml | 26 in compliance with the HDCP 1.3 standard so as to provide secure
|
| /linux/Documentation/admin-guide/cifs/ |
| A D | introduction.rst | 27 POSIX compliance, secure per-user session establishment, encryption,
|
| /linux/Documentation/devicetree/bindings/iio/dac/ |
| A D | adi,ad5758.yaml | 29 dynamically regulates the supply voltage, VDPC+, to meet compliance
|
| /linux/LICENSES/dual/ |
| A D | CDDL-1.0 | 88 Conditioned upon Your compliance with Section 3.1 below and subject
119 Conditioned upon Your compliance with Section 3.1 below and subject
209 provided that You are in compliance with the terms of this License
356 agree that You alone are responsible for compliance with the United
|
| /linux/Documentation/devicetree/bindings/net/ |
| A D | ti,k3-am654-cpts.yaml | 27 Depending on integration it enables compliance with the IEEE 1588-2008
|
| /linux/drivers/gpu/drm/amd/display/ |
| A D | TODO | 106 retimer that we need to program to pass PHY compliance. Currently that's
|
| /linux/drivers/net/ethernet/ti/ |
| A D | Kconfig | 126 Depending on integration CPTS blocks enable compliance with
|
| /linux/Documentation/usb/ |
| A D | acm.rst | 57 thus won't work with this drivers. Check for ACM compliance before buying.
|
| A D | CREDITS | 50 for compliance with the latest USB specification. USAR
|
| /linux/Documentation/networking/ |
| A D | statistics.rst | 194 Drivers must ensure best possible compliance with
|
| A D | regulatory.rst | 90 check that can be used to ensure compliance based on custom EEPROM
|
| /linux/net/wireless/ |
| A D | Kconfig | 80 for whatever reason regulatory compliance has not or
|