13th Intel U-core displayport MST feature

Yulin_ADS · ‎09-03-2024

Hi

The type C port 1 to 4 support DP alternate mode, DP over thunderbolt, native/legacy DP and native/legacy HDMI. We refer to PDG table 241 TCSS port allocation recommendations for TBT4 that has group limitation for daisy chain connection.

If we connect TCP0, TCP1 and use DP alternate mode, is it has same limitation?

Currently we use TCP0 to 2, TCP 0/1 for DP alternate mode (need support daisy chain DP) and TCP2 for USB3.2, does the port allocation has any problem?

RandyT_Intel · ‎12-08-2024

Hi Yulin_ADS,

Thank you for reaching out to us regarding the issue you’re experiencing with your set-up. To better assist you, I need to gather some additional information. Could you please answer the following questions?

What is the make and model of the display/monitor you are using with the daisy chain setup, as well as the cables and adapters you have?
Can you please run the System Support Utility (SSU) and share the logs with me?
Have you tested the daisy chain connection with different devices? This can help determine if the issue is device-specific.
Are you using certified cables and adapters for DP alternate mode? Non-certified accessories can sometimes cause compatibility issues.
Have you checked the bandwidth requirements for your setup? Ensure that the combined bandwidth of your devices does not exceed the port's capabilities.
Is there any noticeable performance difference when using TCP0 and TCP1 separately versus together in a daisy chain? This can help identify if the limitation is specific to daisy chaining.
Have you updated the firmware for your devices and docking stations? Firmware updates can sometimes resolve compatibility issues.
Are there any error messages or logs that indicate a problem when using DP alternate mode? Checking system logs can provide more details about the issue.
Have you tried different port allocations, such as using TCP1 and TCP2 for DP alternate mode and TCP0 for USB3.2? This can help determine if the issue is related to specific port combinations.

PDG table 241 TCSS port allocation recommendations for TBT4 indicate that there are group limitations for daisy chain connections. When using TCP0 and TCP1 for DP alternate mode, these limitations might still apply, potentially affecting performance and compatibility. Given your current setup, using TCP0 and TCP1 for DP alternate mode and TCP2 for USB3.2 should generally work, but it's essential to ensure that the total bandwidth requirements do not exceed the capabilities of the ports. If you encounter issues, consider testing different port allocations to see if performance improves. Additionally, using certified cables and adapters, keeping firmware up to date, and checking for any system logs or error messages can help identify and resolve the problem.

Providing this information will help me diagnose the system more accurately and check for available solutions. Thank you for your cooperation, and I look forward to your response.

Best regards,

Randy T.

Intel Customer Support Technician

RandyT_Intel · ‎12-11-2024

Hi Yulin_ADS,

I wanted to follow up regarding the questions and information we shared with you recently. Have you had a chance to review them? Your feedback is invaluable in helping us determine the next best course of action.

Please let me know if you have any thoughts or if there's anything else you need from us.

Looking forward to your response!

Best regards,

Randy T.

Intel Customer Support Technician

Yulin_ADS · ‎12-11-2024

Hi Randy T.

Please refer to bold word for my answer

What is the make and model of the display/monitor you are using with the daisy, chain setup, as well as the cables and adapters you have?
Ans. Our customer plan to use Fujitsu and Philips display such as following model. Fujitsu Display B24W-7 LED, Fujitsu Display P27-9 TS QHD, Fujitsu Display P34-9 UE,Fujitsu Display P2410 WE, Fujitsu Display P2711 TS QHD, Philips-27B1U5601H, Philips-34B1U5600CH,Philips-243B1JH.
Can you please run the System Support Utility (SSU) and share the logs with me?
Ans. The PCB under design we don't have board to run SSU.
Have you tested the daisy chain connection with different devices? This can help determine if the issue is device-specific.

Ans. No, PCB under design we don't have board to test.

Are you using certified cables and adapters for DP alternate mode? Non-certified accessories can sometimes cause compatibility issues.
Ans. Yes. we will use certified cables.
Have you checked the bandwidth requirements for your setup? Ensure that the combined bandwidth of your devices does not exceed the port's capabilities.
Ans. Could you help to check TCP0 and TPC1 use separate channel or sharing the same channel ? We want to know the reasons for port allocation limitation.
Is there any noticeable performance difference when using TCP0 and TCP1 separately versus together in a daisy chain? This can help identify if the limitation is specific to daisy chaining.
Ans. The system needs to support at least 2 monitors at the same time.
Have you updated the firmware for your devices and docking stations? Firmware updates can sometimes resolve compatibility issues.
Ans. No, PCB under design
Are there any error messages or logs that indicate a problem when using DP alternate mode? Checking system logs can provide more details about the issue.
Ans. No, PCB under design
Have you tried different port allocations, such as using TCP1 and TCP2 for DP alternate mode and TCP0 for USB3.2? This can help determine if the issue is related to specific port combinations.
Ans. No, the PCB under design. Currently the port connection on schematic is TCP0

RandyT_Intel · ‎12-14-2024

Hi Yulin_ADS,

TCP0 and TCP1 typically use separate channels. This separation is crucial for managing bandwidth and ensuring optimal performance. When multiple ports share the same channel, it can lead to congestion and reduced performance, which is likely the reason for port allocation limitations.

Using TCP0 and TCP1 separately versus together in a daisy chain can impact performance. When used separately, each channel can handle its own data stream, reducing the risk of congestion and ensuring smoother performance. In a daisy chain setup, the combined bandwidth of the devices must not exceed the port's capabilities, which can sometimes lead to performance bottlenecks.

In a daisy chain, multiple monitors are connected in a sequence. Ensuring that each monitor has enough bandwidth is crucial for smooth performance.

By using TCP0 and TCP1 separately, you can ensure that each monitor gets enough data without overloading a single channel, which helps in maintaining good performance and avoiding issues like screen flickering or crashes.

Why TCP0 and TCP1 cannot be used on the same channel:

Data Congestion: If TCP0 and TCP1 share the same channel, it can lead to data congestion. This congestion can cause performance issues such as screen flickering, crashes, and reduced data transmission speeds.
Port Allocation Limitations: Sharing the same channel can exceed the bandwidth capabilities of the port, leading to limitations in port allocation. This can prevent the system from supporting multiple high-resolution monitors simultaneously.

Using separate channels for TCP0 and TCP1 ensures that each port can operate efficiently without interfering with each other, providing a smoother and more reliable performance for your setup.

Given the nature of your concerns. You might benefit more from a forum focused on hardware design, PCB development, or display technologies. These forums are likely to have experts who can provide more targeted advice on PCB design, daisy chaining, and port allocation issues. However, I hope the basic information I provided answers some of your questions.

I also highly advised to check your system's original specifications or contact your equipment manufacturer.

For detailed information on MST, see this third-party article.

Note: Intel is supplying content from third-party sites for your convenience and may supply links to additional third-party site(s). Providing such content and/or links only constitutes suggestions and should not be mistaken as an endorsement or recommendation for any specific action. Performing actions recommended by third-party vendors can result in improper operation, damage to the board or processor, or reduced product life. Intel assumes no liability whatsoever in connection with your use of third-party sites or material and disclaims any express or implied warranty relating to the third-party sites or materials. Intel does not control or audit third-party materials or the third party websites referenced. You should visit the referenced website and confirm whether referenced data is accurate

Best regards,

Randy T.

Intel Customer Support Technician