2014-10-20 10:13:19 +04:00
/*
* Copyright © 2014 Red Hat Inc .
*
* Permission is hereby granted , free of charge , to any person obtaining a
* copy of this software and associated documentation files ( the " Software " ) ,
* to deal in the Software without restriction , including without limitation
* the rights to use , copy , modify , merge , publish , distribute , sublicense ,
* and / or sell copies of the Software , and to permit persons to whom the
* Software is furnished to do so , subject to the following conditions :
*
* The above copyright notice and this permission notice shall be included in
* all copies or substantial portions of the Software .
*
* THE SOFTWARE IS PROVIDED " AS IS " , WITHOUT WARRANTY OF ANY KIND , EXPRESS OR
* IMPLIED , INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY ,
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT . IN NO EVENT SHALL
* THE COPYRIGHT HOLDER ( S ) OR AUTHOR ( S ) BE LIABLE FOR ANY CLAIM , DAMAGES OR
* OTHER LIABILITY , WHETHER IN AN ACTION OF CONTRACT , TORT OR OTHERWISE ,
* ARISING FROM , OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
* OTHER DEALINGS IN THE SOFTWARE .
*/
# ifndef DRM_DISPLAYID_H
# define DRM_DISPLAYID_H
2021-03-29 16:37:16 +03:00
# include <linux/types.h>
drm/edid: parse the DisplayID v2.0 VESA vendor block for MSO
The VESA Organization Vendor-Specific Data Block, defined in VESA
DisplayID Standard v2.0, specifies the eDP Multi-SST Operation (MSO)
stream count and segment pixel overlap.
DisplayID v1.3 has Appendix B: DisplayID as an EDID Extension,
describing how DisplayID sections may be embedded in EDID extension
blocks. DisplayID v2.0 does not have such a section, perhaps implying
that DisplayID v2.0 data should not be included in EDID extensions, but
rather in a "pure" DisplayID structure at its own DDC address pair
A4h/A5h, as described in VESA E-DDC Standard v1.3 chapter 3.
However, in practice, displays out in the field have embedded DisplayID
v2.0 data blocks in EDID extensions, including, in particular, some eDP
MSO displays, where a pure DisplayID structure is not available at all.
Parse the MSO data from the DisplayID data block. Do it as part of
drm_add_display_info(), extending it to parse also DisplayID data to
avoid requiring extra calls to update the information.
v2: Check for VESA OUI (Ville)
Reviewed-by: Uma Shankar <uma.shankar@intel.com>
Acked-by: Maxime Ripard <maxime@cerno.tech>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/73ca2887e7b37880690f5c9ba4594c9cd1170669.1630419362.git.jani.nikula@intel.com
2021-08-31 17:17:33 +03:00
# include <linux/bits.h>
2021-03-29 16:37:16 +03:00
2022-05-09 15:03:23 +03:00
struct drm_edid ;
2021-03-29 16:37:16 +03:00
drm/edid: parse the DisplayID v2.0 VESA vendor block for MSO
The VESA Organization Vendor-Specific Data Block, defined in VESA
DisplayID Standard v2.0, specifies the eDP Multi-SST Operation (MSO)
stream count and segment pixel overlap.
DisplayID v1.3 has Appendix B: DisplayID as an EDID Extension,
describing how DisplayID sections may be embedded in EDID extension
blocks. DisplayID v2.0 does not have such a section, perhaps implying
that DisplayID v2.0 data should not be included in EDID extensions, but
rather in a "pure" DisplayID structure at its own DDC address pair
A4h/A5h, as described in VESA E-DDC Standard v1.3 chapter 3.
However, in practice, displays out in the field have embedded DisplayID
v2.0 data blocks in EDID extensions, including, in particular, some eDP
MSO displays, where a pure DisplayID structure is not available at all.
Parse the MSO data from the DisplayID data block. Do it as part of
drm_add_display_info(), extending it to parse also DisplayID data to
avoid requiring extra calls to update the information.
v2: Check for VESA OUI (Ville)
Reviewed-by: Uma Shankar <uma.shankar@intel.com>
Acked-by: Maxime Ripard <maxime@cerno.tech>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/73ca2887e7b37880690f5c9ba4594c9cd1170669.1630419362.git.jani.nikula@intel.com
2021-08-31 17:17:33 +03:00
# define VESA_IEEE_OUI 0x3a0292
2021-08-31 17:17:31 +03:00
/* DisplayID Structure versions */
# define DISPLAY_ID_STRUCTURE_VER_12 0x12
# define DISPLAY_ID_STRUCTURE_VER_20 0x20
2021-08-31 17:17:30 +03:00
/* DisplayID Structure v1r2 Data Blocks */
# define DATA_BLOCK_PRODUCT_ID 0x00
# define DATA_BLOCK_DISPLAY_PARAMETERS 0x01
# define DATA_BLOCK_COLOR_CHARACTERISTICS 0x02
# define DATA_BLOCK_TYPE_1_DETAILED_TIMING 0x03
# define DATA_BLOCK_TYPE_2_DETAILED_TIMING 0x04
# define DATA_BLOCK_TYPE_3_SHORT_TIMING 0x05
# define DATA_BLOCK_TYPE_4_DMT_TIMING 0x06
# define DATA_BLOCK_VESA_TIMING 0x07
# define DATA_BLOCK_CEA_TIMING 0x08
# define DATA_BLOCK_VIDEO_TIMING_RANGE 0x09
# define DATA_BLOCK_PRODUCT_SERIAL_NUMBER 0x0a
# define DATA_BLOCK_GP_ASCII_STRING 0x0b
# define DATA_BLOCK_DISPLAY_DEVICE_DATA 0x0c
# define DATA_BLOCK_INTERFACE_POWER_SEQUENCING 0x0d
# define DATA_BLOCK_TRANSFER_CHARACTERISTICS 0x0e
# define DATA_BLOCK_DISPLAY_INTERFACE 0x0f
# define DATA_BLOCK_STEREO_DISPLAY_INTERFACE 0x10
# define DATA_BLOCK_TILED_DISPLAY 0x12
# define DATA_BLOCK_VENDOR_SPECIFIC 0x7f
# define DATA_BLOCK_CTA 0x81
2014-10-20 10:13:19 +04:00
2021-08-31 17:17:31 +03:00
/* DisplayID Structure v2r0 Data Blocks */
# define DATA_BLOCK_2_PRODUCT_ID 0x20
# define DATA_BLOCK_2_DISPLAY_PARAMETERS 0x21
# define DATA_BLOCK_2_TYPE_7_DETAILED_TIMING 0x22
# define DATA_BLOCK_2_TYPE_8_ENUMERATED_TIMING 0x23
# define DATA_BLOCK_2_TYPE_9_FORMULA_TIMING 0x24
# define DATA_BLOCK_2_DYNAMIC_VIDEO_TIMING 0x25
# define DATA_BLOCK_2_DISPLAY_INTERFACE_FEATURES 0x26
# define DATA_BLOCK_2_STEREO_DISPLAY_INTERFACE 0x27
# define DATA_BLOCK_2_TILED_DISPLAY_TOPOLOGY 0x28
# define DATA_BLOCK_2_CONTAINER_ID 0x29
# define DATA_BLOCK_2_VENDOR_SPECIFIC 0x7e
# define DATA_BLOCK_2_CTA_DISPLAY_ID 0x81
2021-08-31 17:17:30 +03:00
/* DisplayID Structure v1r2 Product Type */
# define PRODUCT_TYPE_EXTENSION 0
# define PRODUCT_TYPE_TEST 1
# define PRODUCT_TYPE_PANEL 2
# define PRODUCT_TYPE_MONITOR 3
# define PRODUCT_TYPE_TV 4
# define PRODUCT_TYPE_REPEATER 5
# define PRODUCT_TYPE_DIRECT_DRIVE 6
2014-10-20 10:13:19 +04:00
2021-08-31 17:17:31 +03:00
/* DisplayID Structure v2r0 Display Product Primary Use Case (~Product Type) */
# define PRIMARY_USE_EXTENSION 0
# define PRIMARY_USE_TEST 1
# define PRIMARY_USE_GENERIC 2
# define PRIMARY_USE_TV 3
# define PRIMARY_USE_DESKTOP_PRODUCTIVITY 4
# define PRIMARY_USE_DESKTOP_GAMING 5
# define PRIMARY_USE_PRESENTATION 6
# define PRIMARY_USE_HEAD_MOUNTED_VR 7
# define PRIMARY_USE_HEAD_MOUNTED_AR 8
2021-03-29 16:37:22 +03:00
struct displayid_header {
2014-10-20 10:13:19 +04:00
u8 rev ;
u8 bytes ;
u8 prod_id ;
u8 ext_count ;
} __packed ;
struct displayid_block {
u8 tag ;
u8 rev ;
u8 num_bytes ;
} __packed ;
struct displayid_tiled_block {
struct displayid_block base ;
u8 tile_cap ;
u8 topo [ 3 ] ;
u8 tile_size [ 4 ] ;
u8 tile_pixel_bezel [ 5 ] ;
u8 topology_id [ 8 ] ;
} __packed ;
2016-05-02 01:35:05 +03:00
struct displayid_detailed_timings_1 {
u8 pixel_clock [ 3 ] ;
u8 flags ;
u8 hactive [ 2 ] ;
u8 hblank [ 2 ] ;
u8 hsync [ 2 ] ;
u8 hsw [ 2 ] ;
u8 vactive [ 2 ] ;
u8 vblank [ 2 ] ;
u8 vsync [ 2 ] ;
u8 vsw [ 2 ] ;
} __packed ;
struct displayid_detailed_timing_block {
struct displayid_block base ;
2020-05-28 17:35:11 +03:00
struct displayid_detailed_timings_1 timings [ ] ;
2016-05-02 01:35:05 +03:00
} ;
2019-06-19 21:09:01 +03:00
drm/edid: parse the DisplayID v2.0 VESA vendor block for MSO
The VESA Organization Vendor-Specific Data Block, defined in VESA
DisplayID Standard v2.0, specifies the eDP Multi-SST Operation (MSO)
stream count and segment pixel overlap.
DisplayID v1.3 has Appendix B: DisplayID as an EDID Extension,
describing how DisplayID sections may be embedded in EDID extension
blocks. DisplayID v2.0 does not have such a section, perhaps implying
that DisplayID v2.0 data should not be included in EDID extensions, but
rather in a "pure" DisplayID structure at its own DDC address pair
A4h/A5h, as described in VESA E-DDC Standard v1.3 chapter 3.
However, in practice, displays out in the field have embedded DisplayID
v2.0 data blocks in EDID extensions, including, in particular, some eDP
MSO displays, where a pure DisplayID structure is not available at all.
Parse the MSO data from the DisplayID data block. Do it as part of
drm_add_display_info(), extending it to parse also DisplayID data to
avoid requiring extra calls to update the information.
v2: Check for VESA OUI (Ville)
Reviewed-by: Uma Shankar <uma.shankar@intel.com>
Acked-by: Maxime Ripard <maxime@cerno.tech>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/73ca2887e7b37880690f5c9ba4594c9cd1170669.1630419362.git.jani.nikula@intel.com
2021-08-31 17:17:33 +03:00
# define DISPLAYID_VESA_MSO_OVERLAP GENMASK(3, 0)
# define DISPLAYID_VESA_MSO_MODE GENMASK(6, 5)
struct displayid_vesa_vendor_specific_block {
struct displayid_block base ;
u8 oui [ 3 ] ;
u8 data_structure_type ;
u8 mso ;
} __packed ;
2023-02-16 23:45:00 +03:00
/*
* DisplayID iteration .
*
* Do not access directly , this is private .
*/
drm/displayid: add new displayid section/block iterators
Iterating DisplayID blocks across sections (in EDID extensions) is
unnecessarily complicated for the caller. Implement DisplayID iterators
to go through all blocks in all sections.
Usage example:
const struct displayid_block *block;
struct displayid_iter iter;
displayid_iter_edid_begin(edid, &iter);
displayid_iter_for_each(block, &iter) {
/* operate on block */
}
displayid_iter_end(&iter);
When DisplayID is stored in EDID extensions, the DisplayID sections map
to extensions as described in VESA DisplayID v1.3 Appendix B: DisplayID
as an EDID Extension. This is implemented here.
When DisplayID is stored in its dedicated DDC device 0xA4, according to
VESA E-DDC v1.3, different rules apply for the structure. This is not
implemented here, as we don't currently use it, but the idea is you'd
have a different call for beginning the iteration, for example simply:
displayid_iter_begin(displayid, &iter);
instead of displayid_iter_edid_begin(), and everything else would be
hidden away in the iterator functions.
v2:
- sizeof(struct displayid_block) -> sizeof(*block) (Ville)
- remove __ prefix from displayid_iter_block
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/da3dead1752ab16c061f7bd248ac1a4268f7fefb.1617024940.git.jani.nikula@intel.com
2021-03-29 16:37:17 +03:00
struct displayid_iter {
2022-05-09 15:03:23 +03:00
const struct drm_edid * drm_edid ;
drm/displayid: add new displayid section/block iterators
Iterating DisplayID blocks across sections (in EDID extensions) is
unnecessarily complicated for the caller. Implement DisplayID iterators
to go through all blocks in all sections.
Usage example:
const struct displayid_block *block;
struct displayid_iter iter;
displayid_iter_edid_begin(edid, &iter);
displayid_iter_for_each(block, &iter) {
/* operate on block */
}
displayid_iter_end(&iter);
When DisplayID is stored in EDID extensions, the DisplayID sections map
to extensions as described in VESA DisplayID v1.3 Appendix B: DisplayID
as an EDID Extension. This is implemented here.
When DisplayID is stored in its dedicated DDC device 0xA4, according to
VESA E-DDC v1.3, different rules apply for the structure. This is not
implemented here, as we don't currently use it, but the idea is you'd
have a different call for beginning the iteration, for example simply:
displayid_iter_begin(displayid, &iter);
instead of displayid_iter_edid_begin(), and everything else would be
hidden away in the iterator functions.
v2:
- sizeof(struct displayid_block) -> sizeof(*block) (Ville)
- remove __ prefix from displayid_iter_block
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/da3dead1752ab16c061f7bd248ac1a4268f7fefb.1617024940.git.jani.nikula@intel.com
2021-03-29 16:37:17 +03:00
const u8 * section ;
int length ;
int idx ;
int ext_index ;
2023-02-16 23:45:00 +03:00
u8 version ;
u8 primary_use ;
drm/displayid: add new displayid section/block iterators
Iterating DisplayID blocks across sections (in EDID extensions) is
unnecessarily complicated for the caller. Implement DisplayID iterators
to go through all blocks in all sections.
Usage example:
const struct displayid_block *block;
struct displayid_iter iter;
displayid_iter_edid_begin(edid, &iter);
displayid_iter_for_each(block, &iter) {
/* operate on block */
}
displayid_iter_end(&iter);
When DisplayID is stored in EDID extensions, the DisplayID sections map
to extensions as described in VESA DisplayID v1.3 Appendix B: DisplayID
as an EDID Extension. This is implemented here.
When DisplayID is stored in its dedicated DDC device 0xA4, according to
VESA E-DDC v1.3, different rules apply for the structure. This is not
implemented here, as we don't currently use it, but the idea is you'd
have a different call for beginning the iteration, for example simply:
displayid_iter_begin(displayid, &iter);
instead of displayid_iter_edid_begin(), and everything else would be
hidden away in the iterator functions.
v2:
- sizeof(struct displayid_block) -> sizeof(*block) (Ville)
- remove __ prefix from displayid_iter_block
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/da3dead1752ab16c061f7bd248ac1a4268f7fefb.1617024940.git.jani.nikula@intel.com
2021-03-29 16:37:17 +03:00
} ;
2022-05-09 15:03:23 +03:00
void displayid_iter_edid_begin ( const struct drm_edid * drm_edid ,
drm/displayid: add new displayid section/block iterators
Iterating DisplayID blocks across sections (in EDID extensions) is
unnecessarily complicated for the caller. Implement DisplayID iterators
to go through all blocks in all sections.
Usage example:
const struct displayid_block *block;
struct displayid_iter iter;
displayid_iter_edid_begin(edid, &iter);
displayid_iter_for_each(block, &iter) {
/* operate on block */
}
displayid_iter_end(&iter);
When DisplayID is stored in EDID extensions, the DisplayID sections map
to extensions as described in VESA DisplayID v1.3 Appendix B: DisplayID
as an EDID Extension. This is implemented here.
When DisplayID is stored in its dedicated DDC device 0xA4, according to
VESA E-DDC v1.3, different rules apply for the structure. This is not
implemented here, as we don't currently use it, but the idea is you'd
have a different call for beginning the iteration, for example simply:
displayid_iter_begin(displayid, &iter);
instead of displayid_iter_edid_begin(), and everything else would be
hidden away in the iterator functions.
v2:
- sizeof(struct displayid_block) -> sizeof(*block) (Ville)
- remove __ prefix from displayid_iter_block
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/da3dead1752ab16c061f7bd248ac1a4268f7fefb.1617024940.git.jani.nikula@intel.com
2021-03-29 16:37:17 +03:00
struct displayid_iter * iter ) ;
const struct displayid_block *
__displayid_iter_next ( struct displayid_iter * iter ) ;
# define displayid_iter_for_each(__block, __iter) \
while ( ( ( __block ) = __displayid_iter_next ( __iter ) ) )
void displayid_iter_end ( struct displayid_iter * iter ) ;
2023-02-16 23:45:00 +03:00
u8 displayid_version ( const struct displayid_iter * iter ) ;
u8 displayid_primary_use ( const struct displayid_iter * iter ) ;
2014-10-20 10:13:19 +04:00
# endif