Message-ID: <Z5Ze4l3kpYTPAQDJ@ccdjLinux26>
Date: Sun, 26 Jan 2025 18:12:18 +0200
From: Gil Fine <gil.fine@...ux.intel.com>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc: Aaron Rainbolt <arainbolt@...cus.org>, 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>,
	Novitzky Oren <oren.novitzky@...el.com>
Subject: Re: USB-C DisplayPort display failing to stay active with Intel
 Barlow Ridge USB4 controller, power-management related issue?

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@...ux.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

Powered by blists - more mailing lists