linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gil Fine <gil.fine@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Aaron Rainbolt <arainbolt@kfocus.org>,
	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>,
	Novitzky Oren <oren.novitzky@intel.com>,
	gil.fine@intel.com
Subject: Re: USB-C DisplayPort display failing to stay active with Intel Barlow Ridge USB4 controller, power-management related issue?
Date: Tue, 28 Jan 2025 10:29:32 +0200	[thread overview]
Message-ID: <Z5iVbOeNYmMeLMj8@ccdjLinux26> (raw)
In-Reply-To: <Z5Ze4l3kpYTPAQDJ@ccdjLinux26>

Hi,
Got reponse from Oren that B0 BarlowRidge controller is not longer supported,
and the last thunderbolt firmware we released for B0 is 16.3 , from here:
https://www.intel.com/content/www/us/en/secure/design/confidential/software-kits/kit-details.html?kitId=821065&wapkw=barlow%20ridge%20nvm%20b0

So @Aaron, please try with that one.

Thanks !

On Sun, Jan 26, 2025 at 06:12:18PM +0200, Gil Fine wrote:
> Hi,
> 
> + Oren
> 
> On Sun, Jan 26, 2025 at 07:53:47AM +0200, Mika Westerberg wrote:
> > On Fri, Jan 24, 2025 at 05:05:40PM -0600, Aaron Rainbolt wrote:
> > > On Fri, 15 Nov 2024 15:20:22 +0200
> > > Mika Westerberg <mika.westerberg@linux.intel.com> wrote:
> > > 
> > > > Hi,
> > > > 
> > > > On Thu, Nov 14, 2024 at 10:41:25AM -0600, Aaron Rainbolt wrote:
> > > > > This is production hardware (specifically Clevo's X370SNW1-G and
> > > > > X370SNV1-G laptops), available for purchase from Sager, XOTICPC,
> > > > > Schenker, likely many other resellers, and our own website
> > > > > at https://kfocus.org/spec/spec-m2.html (with a tool that allows users
> > > > > to work around the bug). The firmware is baked into the hardware
> > > > > provided to us by our ODM, and for the sake of stability we do not
> > > > > modify any firmware on the machines with the exception of applying
> > > > > BIOS updates provided to us directly by the ODM. They appear to get
> > > > > their firmware directly from Clevo.  
> > > > 
> > > > Okay thanks.
> > > > 
> > > > > We have requested an updated BIOS from the ODM. If one is
> > > > > available, we will upgrade and run the tests again.  
> > > > 
> > > > Yes, I hope you can get the firmwares. The one you have now is not
> > > > "production quality" firmare so you should not really have that there
> > > > in the first place and Clevo should definitely provide you an
> > > > upgrade. Note this is separate from the BIOS. But your BIOS has issue
> > > > too regarding the USB4 power contract that is required by Microsoft
> > > > so I would expect that you should get that one upgraded too.
> > > > 
> > > > The patch I shared earlier should deal with all the other cases except
> > > > that weird one where we do not seem to get unplugs (and the resource
> > > > is available) which is not how the firmware is expected to work. I was
> > > > planning to submit it upstream after some more validation on our end,
> > > > probably afer v6.13-rc1 is released. I'll CC you.
> > > > 
> > > > If/when you get the new firmare I would definitely appreciate if your
> > > > folks could give it a try.
> > > 
> > > Hi Mika, sorry for the very late follow-up, been busy with other work
> > > stuff.
> > 
> > No worries.
> > 
> > > We contacted the ODM to get newer firmware. They contacted Clevo, who
> > > told them that the Barlow Ridge chip in these machines is the B0
> > > revision. According to them, the latest firmware available for the B0
> > > revision is 14.6; they also state that the 56.x firmware is for the B1
> > > revision and is incompatible.
> > > 
> > > Is it possible that the problem is that the driver is written
> > > specifically for the B1 revision and only partially works with the B0
> > > revision?
> > 
> > The driver support is written for USB4 v2 not specifically for certain
> > Barlow Ridge silicon stepping. B0 has issues that B1 fixes but I'm not sure
> > if they are related to this one. My reference host controller is actually
> > B0 and it is running the 56.x firmware IIRC so not incompatible.
> > 
> > @Gil, can you verify this?
> 
> Actually we didn't try use latest BR firmware on old HW like B0 so can't tell
> if all BR features expected to work on B0, but let me add Oren, the contact
> person for these.
> 
> @Oren, Is B0 BarlowRidge is still officially supported?
> I mean do we release newer NVM versions to Clevo for B0 BR?
> 
> -- 
> Thanks,
> Gil

-- 
Thanks,
Gil

      reply	other threads:[~2025-01-28  8:29 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
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 [this message]

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=Z5iVbOeNYmMeLMj8@ccdjLinux26 \
    --to=gil.fine@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=arainbolt@kfocus.org \
    --cc=gil.fine@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=michael.jamet@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=mmikowski@kfocus.org \
    --cc=oren.novitzky@intel.com \
    /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).