From: Atharva Tiwari <atharvatiwarilinuxdev@gmail.com>
Cc: Atharva Tiwari <atharvatiwarilinuxdev@gmail.com>,
Andreas Noever <andreas.noever@gmail.com>,
Mika Westerberg <westeri@kernel.org>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v8 0/3] Add Apple T2 NHI Device links
Date: Mon, 17 Aug 2026 06:13:21 -0400 [thread overview]
Message-ID: <20260817101329.1517-1-atharvatiwarilinuxdev@gmail.com> (raw)
This series adds support for Device linking on Titan ridge, and
Icelake, which are used exclusively on Apple T2 machines.
Changes in v8:
- Shifted tb_apple_add_links to pci.c
Changes in v7:
- Used pci_lock_rescan_remove to prevent race conditons.
- Fixed patch format.
Changes in v6:
- Used for_each_pci_bridge in Icelake section
- Removed has_apple_t2_chip as its not required now
Changes in v5:
- Used Icelake root PCI IDs for detection of root ports instead of TRP
Changes in v4:
- Limited TRP check to T2 Icelake systems only
- Optimized has_apple_t2_chip check
- Included pci.h to drivers/thunderbolt/tb.c
- Used __free(pci_dev_put) to avoid label
Changes in v3:
- Fix build errors with non-x86 machines
- Used __initconst for apple_t2_devices
- Removed UEFI_QUIRK_SKIP_CERT as its unused now
- Used IS_ENABLED(CONFIG_ACPI) in tb_apple_add_links for the T2 part
- Removed !bid check to remove warning with -Waddress
Changes in v2:
- Used a less generic name for has_t2_chip
- Used DMI instead of PCI for has_apple_t2_chip to avoid PCI problems
- Initialized ret in tb_apple_add_links
Link to v7:
https://lore.kernel.org/all/20260812153717.1345-1-atharvatiwarilinuxdev@gmail.com/
Link to v6:
https://lore.kernel.org/all/20260730223435.2874-1-atharvatiwarilinuxdev@gmail.com/
Link to v5:
https://lore.kernel.org/all/20260727211807.1223-1-atharvatiwarilinuxdev@gmail.com/
Link to v4:
https://lore.kernel.org/all/20260724164641.2239-1-atharvatiwarilinuxdev@gmail.com/
Link to v3:
https://lore.kernel.org/all/20260721063412.11588-1-atharvatiwarilinuxdev@gmail.com/
Link to v2:
https://lore.kernel.org/all/20260721054506.11871-1-atharvatiwarilinuxdev@gmail.com/
Link to v1:
https://lore.kernel.org/all/20260719180308.1398-1-atharvatiwarilinuxdev@gmail.com/
Atharva Tiwari (3):
thunderbolt: Shift tb_apple_add_links to pci.c
thunderbolt: Add device links for Apple machines with Titan Ridge
thunderbolt: Add device links for Apple systems with Icelake
thunderbolt
drivers/thunderbolt/pci.c | 119 ++++++++++++++++++++++++++++++++++++++
drivers/thunderbolt/tb.c | 72 +----------------------
drivers/thunderbolt/tb.h | 1 +
3 files changed, 121 insertions(+), 71 deletions(-)
--
2.43.0
next reply other threads:[~2026-08-17 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 10:13 Atharva Tiwari [this message]
2026-08-17 10:13 ` [PATCH v8 1/3] thunderbolt: Shift tb_apple_add_links to pci.c Atharva Tiwari
2026-08-17 10:13 ` [PATCH v8 2/3] thunderbolt: Add device links for Apple machines with Titan Ridge Atharva Tiwari
2026-08-17 10:13 ` [PATCH v8 3/3] thunderbolt: Add device links for Apple systems with Icelake thunderbolt Atharva Tiwari
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=20260817101329.1517-1-atharvatiwarilinuxdev@gmail.com \
--to=atharvatiwarilinuxdev@gmail.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=westeri@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