[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZnvWTo1M_z0Am1QC@wunner.de>
Date: Wed, 26 Jun 2024 10:50:22 +0200
From: Lukas Wunner <lukas@...ner.de>
To: Esther Shimanovich <eshimanovich@...omium.org>
Cc: Mika Westerberg <mika.westerberg@...ux.intel.com>,
Mario Limonciello <mario.limonciello@....com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Bjorn Helgaas <bhelgaas@...gle.com>, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, Rajat Jain <rajatja@...gle.com>
Subject: Re: [PATCH v4] PCI: Relabel JHL6540 on Lenovo X1 Carbon 7,8
On Mon, Jun 24, 2024 at 11:58:46AM -0400, Esther Shimanovich wrote:
> On Wed, May 15, 2024 at 4:45???PM Lukas Wunner <lukas@...ner.de> wrote:
> > Could you add this to the command line:
> > thunderbolt.dyndbg ignore_loglevel log_buf_len=10M
> >
> > and this to your kernel config:
> > CONFIG_DYNAMIC_DEBUG=y
> >
> > You should see "... is associated with ..." messages in dmesg.
>
> I tried Lukas's patches again, after enabling the Thunderbolt driver
> in the config and also verbose messages, so that I can see
> "thunderbolt:" messages, but it still never reaches the
> tb_pci_notifier_call function. I don't see "associated with" in any of
> the logs. The config on the image I am testing does not have the
> thunderbolt driver enabled by default, so this patch wouldn't help my
> use case even if I did manage to get it to work.
Mika, what do you make of this? Are the ChromeBooks in question
using ICM-based tunneling instead of native tunneling? I thought
this is all native nowadays and ICM is only used on older (pre-USB4)
products.
Thanks,
Lukas
Powered by blists - more mailing lists