On 11.06.2015 00:12, James Feeney wrote:
>> Yes, DP needs its own clock source. However, you only need one clock source
>> for all DP ports so you can drive multiple DP displays from a single clock
>> source. The clock source used for DP cannot be shared with non-DP displays.
>> ...
>> There are
On Wed, Jun 10, 2015 at 6:12 PM, James Feeney wrote:
>> Yes, DP needs its own clock source. However, you only need one clock source
>> for all DP ports so you can drive multiple DP displays from a single clock
>> source. The clock source used for DP cannot be shared with non-DP displays.
>> ...
> Yes, DP needs its own clock source. However, you only need one clock source
> for all DP ports so you can drive multiple DP displays from a single clock
> source. The clock source used for DP cannot be shared with non-DP displays.
> ...
> There are additional caveats however. For example, you
> -Original Message-
> From: James Feeney [mailto:james at nurealm.net]
> Sent: Monday, June 08, 2015 3:43 PM
> To: Deucher, Alexander; Koenig, Christian
> Cc: dri-devel at lists.freedesktop.org
> Subject: Re: atombios_crtc.c - make error messages distinguishable "
On 08.06.2015 18:26, James Feeney wrote:
> atombios_crtc.c
>
> In multi-display configurations, especially with three or more displays,
> PLL/clock source allocations can fail when there are more crtc's than PLLs.
> When attempting to debug these PLL allocation failures in the source code, the
> er
> -Original Message-
> From: James Feeney [mailto:james at nurealm.net]
> Sent: Monday, June 08, 2015 1:10 PM
> To: Koenig, Christian; Deucher, Alexander
> Cc: dri-devel at lists.freedesktop.org
> Subject: Re: atombios_crtc.c - make error messages distinguishable "
> DCE4 parts (like the 5570) only have an external clock if the OEM supplied
> it, hence not all boards have it. Also, the external clock source can only
> be used to drive native DP (DisplayPort), not non-DP outputs like DVI or HDMI
> or VGA or a passive DP to DVI/HDMI convertor. If you are usin
> Actually it's always the same error. The message just appears in that file
> multiple times for different hardware generations.
Which is fine, presupposing that the user already knows what hardware generation
they are using _and_ how the video card manufacturer actually implemented the
display i
atombios_crtc.c
In multi-display configurations, especially with three or more displays,
PLL/clock source allocations can fail when there are more crtc's than PLLs.
When attempting to debug these PLL allocation failures in the source code, the
error message displayed in the log, DRM_ERROR("unable
