linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Aaron Rainbolt <arainbolt@kfocus.org>
Cc: YehezkelShB@gmail.com, michael.jamet@intel.com,
	andreas.noever@gmail.com, linux-usb@vger.kernel.org,
	mmikowski@kfocus.org, linux-kernel@vger.kernel.org,
	Gil Fine <gil.fine@linux.intel.com>
Subject: Re: USB-C DisplayPort display failing to stay active with Intel Barlow Ridge USB4 controller, power-management related issue?
Date: Thu, 7 Nov 2024 11:45:43 +0200	[thread overview]
Message-ID: <20241107094543.GL275077@black.fi.intel.com> (raw)
In-Reply-To: <20241106110134.1871a7f6@kf-ir16>

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.

  reply	other threads:[~2024-11-07  9:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10  3:01 USB-C DisplayPort display failing to stay active with Intel Barlow Ridge USB4 controller, power-management related issue? Aaron Rainbolt
2024-10-10  4:49 ` Mika Westerberg
2024-10-11  4:26   ` Aaron Rainbolt
2024-10-11 16:38     ` Mika Westerberg
2024-10-11 18:02       ` Aaron Rainbolt
2024-10-11 23:37       ` Aaron Rainbolt
2024-10-23  6:27         ` Mika Westerberg
2024-10-23  7:39           ` Mika Westerberg
2024-10-23 22:44             ` Aaron Rainbolt
2024-10-24 15:43               ` Mika Westerberg
2024-10-31 14:55                 ` Aaron Rainbolt
2024-11-01  7:21                   ` Mika Westerberg
2024-11-01 23:13                     ` Aaron Rainbolt
2024-11-04  6:01                       ` Mika Westerberg
2024-11-05 20:16                         ` Aaron Rainbolt
2024-11-06  6:06                           ` Mika Westerberg
2024-11-06 17:01                             ` Aaron Rainbolt
2024-11-07  9:45                               ` Mika Westerberg [this message]
2024-11-11  8:22                                 ` Mika Westerberg
2024-11-12 21:44                                   ` Aaron Rainbolt
2024-11-14 11:51                                     ` Mika Westerberg
2024-11-14 16:41                                       ` Aaron Rainbolt
2024-11-15 13:20                                         ` Mika Westerberg
2024-12-12 22:12                                           ` Aaron Rainbolt
2024-12-13 12:03                                             ` Mika Westerberg
2025-01-24 23:05                                           ` Aaron Rainbolt
2025-01-26  5:53                                             ` Mika Westerberg
2025-01-26 16:12                                               ` Gil Fine
2025-01-28  8:29                                                 ` Gil Fine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241107094543.GL275077@black.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=arainbolt@kfocus.org \
    --cc=gil.fine@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=michael.jamet@intel.com \
    --cc=mmikowski@kfocus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).