[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <59cd3694-c6e5-42c4-a757-594b11b69525@amd.com>
Date: Wed, 6 Aug 2025 11:46:04 +0530
From: "Rangoju, Raju" <raju.rangoju@....com>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc: linux-usb@...r.kernel.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, andreas.noever@...il.com,
michael.jamet@...el.com, westeri@...nel.org, YehezkelShB@...il.com,
bhelgaas@...gle.com, Sanath.S@....com
Subject: Re: [PATCH 0/3] thunderbolt: Update XDomain vendor properties
dynamically
On 7/28/2025 12:17 PM, Mika Westerberg wrote:
> Hi,
>
> On Tue, Jul 22, 2025 at 11:20:23PM +0530, Raju Rangoju wrote:
>> This patch series aims to update vendor properties for XDomain
>> dynamically for vendors like AMD, Intel and ASMedia.
>
> The XDomain properties pretty much describe "software" not the underlying
> hardware so I don't understand why this is needed? We could have some USB
> IF registered Linux specific ID there but I don't see why this matters at
> all.
Currently, it is showing up as "Intel" on AMD host controllers during
inter-domain connection. I suppose an alternative is to just call it
"Linux" or "Linux Connection Manager" to ensure we accurately represent
the connections across different systems.
I appreciate your guidance on this and suggestions you might have.
>
>> Raju Rangoju (3):
>> thunderbolt: Dynamically populate vendor properties for XDomain
>> PCI: Add PCI vendor ID for ASMedia USB4 devices
>> thunderbolt: Add vendor ASMedia in update_property_block for XDomain
>>
>> drivers/thunderbolt/nvm.c | 2 +-
>> drivers/thunderbolt/xdomain.c | 32 +++++++++++++++++++++-----------
>> include/linux/pci_ids.h | 1 +
>> 3 files changed, 23 insertions(+), 12 deletions(-)
>>
>> --
>> 2.34.1
Powered by blists - more mailing lists