linux-kernel - Re: USB-C DisplayPort display failing to stay active with Intel Barlow Ridge USB4 controller, power-management related issue?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20241107094543.GL275077@black.fi.intel.com>
Date: Thu, 7 Nov 2024 11:45:43 +0200
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Aaron Rainbolt <arainbolt@...cus.org>
Cc: YehezkelShB@...il.com, michael.jamet@...el.com,
	andreas.noever@...il.com, linux-usb@...r.kernel.org,
	mmikowski@...cus.org, linux-kernel@...r.kernel.org,
	Gil Fine <gil.fine@...ux.intel.com>
Subject: Re: USB-C DisplayPort display failing to stay active with Intel
 Barlow Ridge USB4 controller, power-management related issue?

Hi,

On Wed, Nov 06, 2024 at 11:01:34AM -0600, Aaron Rainbolt wrote:
> > Unfortunately that does not help here. I need to figure something else
> > how to detect the redrive case with this firmware but first, does this
> > work in Windows? I mean if you install Windows to this same system
> > does it work as expected?
> 
> It does work as expected under Windows 11, with one major caveat. We
> used a Windows 11 ISO with a setup.exe created on April 05 2023 for
> installing the test system, and after initial installation it behaved
> exactly the same way as Linux behaves now (displays going blank soon
> after being plugged in). However, after installing all available
> Windows updates, the issue resolved, and the displays worked exactly as
> intended (the screens are recognized when attached and do not end up
> disconnecting after a timeout).
> 
> Would it be helpful to test on Windows 11, and provide a report and
> system logs?

Unfortunately, I don't know anything about Windows ;-)

However, I asked our Thunderbolt hardware/firmware team about this, if
they have any idea how it was solved in Windows side. Might take a
couple of days though.