Re: [Intel-gfx] Tracing a "drm_mode_prune_invalid"

2021-08-26 Thread Adam Chasen
L309 There are mention of a small number of "external converter chips" which are used in the above conditional: https://elixir.bootlin.com/linux/latest/source/drivers/gpu/drm/amd/display/include/ddc_service_types.h#L30 Thanks, Adam On Fri, Jun 4, 2021, at 1:13 PM, Ville Syrjälä wrot

Re: [Intel-gfx] Tracing a "drm_mode_prune_invalid"

2021-06-04 Thread Adam Chasen
x_tmds_clock; int max_dotclock; u8 max_bpc; bool ycbcr_444_to_420; } dfp; On Mon, May 31, 2021, at 10:28 AM, Adam Chasen wrote: > Ville, > Thanks for the additional detail! > > I looked up HPD and understand it is hot plug detection, but I didn

Re: [Intel-gfx] Tracing a "drm_mode_prune_invalid"

2021-05-31 Thread Adam Chasen
do you have an example of a "manual override" (i.e. module argument) for another situation I can use as a guide? Still curious what DPCD DFP stands for. Thanks, Adam On Mon, May 31, 2021, at 10:15 AM, Ville Syrjälä wrote: > On Fri, May 28, 2021 at 02:15:46PM -0400, Adam Chasen w

Re: [Intel-gfx] Tracing a "drm_mode_prune_invalid"

2021-05-28 Thread Adam Chasen
e's request: DPCD DFP: 0a What is the DPCD DFP? Thanks, Adam On Wed, May 12, 2021, at 5:07 PM, Adam Chasen wrote: > Ville, > DPCD DFP: 0a > > What is the DPCD DFP? > > Additional info, this is the first time there has been an issue with > this adapter not working (i.e. it m

Re: [Intel-gfx] Tracing a "drm_mode_prune_invalid"

2021-05-12 Thread Adam Chasen
00 00 00 00 00 00 00 00 00 00 00 00 00 || * On Wed, May 12, 2021, at 4:04 PM, Ville Syrjälä wrote: > On Wed, May 12, 2021 at 12:31:14PM -0400, Adam Chasen wrote: > > Hoping I can (help) craft a patch to address what appears to be an issue > > with overaggressive mode pruning.

[Intel-gfx] Tracing a "drm_mode_prune_invalid"

2021-05-12 Thread Adam Chasen
Hoping I can (help) craft a patch to address what appears to be an issue with overaggressive mode pruning. I am having trouble with rejection of a Dual-DVI compatible mode out of the DisplayPort specific to i915 in Fedora 33. It seems that drm_mode_validate_pipeline is the wall I hit when diggi