From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: Esther Shimanovich <eshimanovich@chromium.org>,
Mario Limonciello <mario.limonciello@amd.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Rajat Jain <rajatja@google.com>
Subject: Re: [PATCH v4] PCI: Relabel JHL6540 on Lenovo X1 Carbon 7,8
Date: Mon, 29 Jul 2024 11:04:41 +0300 [thread overview]
Message-ID: <20240729080441.GG1532424@black.fi.intel.com> (raw)
In-Reply-To: <ZqZmleIHv1q3WvsO@wunner.de>
On Sun, Jul 28, 2024 at 05:41:09PM +0200, Lukas Wunner wrote:
> On Wed, Jun 26, 2024 at 11:59:45AM +0300, Mika Westerberg wrote:
> > On Wed, Jun 26, 2024 at 10:50:22AM +0200, Lukas Wunner wrote:
> > > 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@wunner.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.
> >
> > I think these are not Chromebooks. They are "regular" PCs with
> > Thunderbolt 3 host controller which is ICM as you suggest.
> >
> > There is still Maple Ridge and Tiger Lake (non-Chrome) that are ICM
> > (firmware based connection manager) that are USB4 but everything after
> > that is software based connection manager.
>
> Even with ICM, the DROM of the root switch seems to be retrieved:
>
> icm_start()
> tb_switch_add()
> tb_drom_read()
>
> Assuming the DROM contains proper PCIe Upstream and Downstream Adapter
> Entries, all the data needed to at least associate the PCIe Adapters
> on the root switch should be there. So I'm surprised Esther is not
> seeing *any* messages.
>
> Do the DROMs on ICM root switches generally lack PCIe Upstream and
> Downstream Adapter Entries?
> What am I missing?
My guess is that they are not populated for ICM host router DROM
entries. These are pretty much Apple stuff and USB4 dropped them
completely in favour of the router operations.
next prev parent reply other threads:[~2024-07-29 8:04 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 20:53 [PATCH v4] PCI: Relabel JHL6540 on Lenovo X1 Carbon 7,8 Esther Shimanovich
2023-12-21 23:15 ` Dmitry Torokhov
2023-12-27 0:15 ` Bjorn Helgaas
2023-12-28 13:25 ` Lukas Wunner
2023-12-28 13:39 ` Mika Westerberg
2024-01-17 21:21 ` Esther Shimanovich
2024-01-18 6:00 ` Mika Westerberg
2024-01-18 15:47 ` Mario Limonciello
2024-01-18 16:12 ` Dmitry Torokhov
2024-01-18 16:21 ` Dmitry Torokhov
2024-01-19 5:37 ` Mika Westerberg
2024-01-19 7:48 ` Mika Westerberg
2024-01-19 10:22 ` Mika Westerberg
2024-01-19 16:03 ` Esther Shimanovich
2024-01-22 6:10 ` Mika Westerberg
2024-01-22 23:50 ` Mario Limonciello
2024-01-23 6:18 ` Mika Westerberg
2024-01-25 23:45 ` Esther Shimanovich
2024-04-15 22:34 ` Esther Shimanovich
2024-04-16 5:03 ` Mika Westerberg
2024-04-18 19:43 ` Esther Shimanovich
2024-04-19 4:49 ` Mika Westerberg
2024-04-22 19:17 ` Esther Shimanovich
2024-04-22 19:21 ` Mario Limonciello
2024-04-23 5:33 ` Mika Westerberg
2024-04-23 8:31 ` Lukas Wunner
2024-04-23 8:40 ` Mika Westerberg
2024-04-23 16:59 ` Mario Limonciello
2024-04-24 8:56 ` Mika Westerberg
2024-04-25 21:16 ` Esther Shimanovich
2024-04-26 4:52 ` Mika Westerberg
2024-04-26 15:58 ` Esther Shimanovich
2024-04-27 5:35 ` Lukas Wunner
2024-04-27 7:41 ` Mika Westerberg
2024-04-27 7:08 ` Lukas Wunner
2024-04-27 15:09 ` Lukas Wunner
2024-05-01 22:23 ` Esther Shimanovich
2024-05-02 4:38 ` Mika Westerberg
2024-05-02 9:54 ` Mario Limonciello
2024-05-02 10:07 ` Mika Westerberg
2024-05-08 5:14 ` Lukas Wunner
2024-05-10 5:26 ` Mika Westerberg
2024-05-10 15:44 ` Esther Shimanovich
2024-05-11 4:38 ` Mika Westerberg
2024-05-11 5:43 ` Mika Westerberg
2024-05-15 18:53 ` Esther Shimanovich
2024-05-15 20:35 ` Lukas Wunner
2024-05-15 20:51 ` Lukas Wunner
2024-05-15 21:44 ` Esther Shimanovich
2024-05-16 8:30 ` Mika Westerberg
2024-05-16 10:03 ` Mika Westerberg
2024-06-24 15:58 ` Esther Shimanovich
2024-06-26 8:05 ` Mika Westerberg
2024-07-26 18:17 ` Esther Shimanovich
2024-07-29 8:16 ` Mika Westerberg
2024-06-26 8:50 ` Lukas Wunner
2024-06-26 8:59 ` Mika Westerberg
2024-07-28 15:41 ` Lukas Wunner
2024-07-29 8:04 ` Mika Westerberg [this message]
2024-08-25 14:29 ` Lukas Wunner
2024-08-26 5:41 ` Mika Westerberg
2024-08-28 20:12 ` Esther Shimanovich
2024-05-16 9:16 ` Mika Westerberg
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=20240729080441.GG1532424@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=eshimanovich@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mario.limonciello@amd.com \
--cc=rajatja@google.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