On Fri, Jul 04, 2025 at 08:40:35PM -0400, Damien Riégel wrote:
When matching a device, only the vendor ID and product ID are used.
It shouldn't be that way. That was not the intention.
As all bundles in an interface share the same VID and PID, there is no way to differentiate between two bundles, and they are forced to use the same driver.
To allow using several vendor bundles in the same device, include the bundle ID when matching. The assumption here is that bundle IDs are stable across the lifespan of a product and never change.
The goal of this change is to open the discussion. Greybus standardizes a bunch of protocols like GPIO, SPI, etc. but also has provisioning for vendor bundle and protocol. There is only one ID reserved for vendor, 0xFF, so the question is did Greybus ever envision supporting several vendor bundles, or one vendor bundle with several vendor cports in it? Or the assumption always was that there could be at most only vendor cport?
The goal was to emulate what USB does here. If you have a vendor-specific protocol, then set the vendor protocol id (0xff) and then trigger off of the VID and PID. Then you can do whatever you want here in your driver as it's a vendor-specific one.
So you are wanting multiple devices with the same vid/pid yet do different things? Why not just change the PID?
Like with USB, a bundle id is not guaranteed to be "static", BUT if you want to make that distinction in your driver that is a vendor-specific one, go ahead. Again, that should be like USB interface numbers, right?
thanks,
greg k-h