Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Kenneth Crudup <kenny@panix.com>
To: ilpo.jarvinen@linux.intel.com
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, Kenneth C <kenny@panix.com>
Subject: Re: Commit 4292a1e45fd4 ("PCI: Refactor distributing available memory to use loops") gives errors enumerating TBolt devices behind my TB dock
Date: Tue, 7 Oct 2025 16:02:11 -0700	[thread overview]
Message-ID: <cb5d09de-d7b6-48bb-9c2a-22094e00ee4e@panix.com> (raw)
In-Reply-To: <dd551b81-9e81-480b-aab3-7cf8b8bbc1d0@panix.com>


On 10/7/25 14:39, Kenneth Crudup wrote:

> I have a Thunderbolt dock (Amazon Basics generic thing, but it also 
> happens on my CalDigit TB4). With the above commit (and aaae2863e731 
> ("PCI: Refactor remove_dev_resources() to use pbus_select_window()), so 
> the Subject: commit would come out cleanly) if I plug in a TB device 
> past my TB Dock, they don't fully enumerate (i.e., no DP tunneling, no 
> partitions created, etc.)

I should mention for completness' sake that if I attach anything 
directly to the/another TB port it's fully recognized; the only trouble 
comes is when there's a TB dock in the middle.

-Kenny

-- 
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange 
County CA


  reply	other threads:[~2025-10-07 23:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07 21:39 Commit 4292a1e45fd4 ("PCI: Refactor distributing available memory to use loops") gives errors enumerating TBolt devices behind my TB dock Kenneth Crudup
2025-10-07 23:02 ` Kenneth Crudup [this message]
2025-10-08  8:10 ` Ilpo Järvinen
2025-10-08 14:27   ` Kenneth Crudup
2025-10-08 14:57   ` Kenneth Crudup
2025-10-08 20:14 ` Bjorn Helgaas
2025-10-08 20:30   ` Kenneth Crudup
2025-10-08 20:58     ` Bjorn Helgaas
2025-10-08 21:20       ` Kenneth Crudup
2025-10-08 21:51         ` Bjorn Helgaas
2025-10-08 21:14   ` Kenneth Crudup
2025-10-08 21:52     ` Bjorn Helgaas
2025-10-08 21:54       ` Kenneth Crudup
2025-10-08 21:53   ` Kenneth Crudup

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=cb5d09de-d7b6-48bb-9c2a-22094e00ee4e@panix.com \
    --to=kenny@panix.com \
    --cc=bhelgaas@google.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-pci@vger.kernel.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