Added a PID for Sentient Computing

[Rubeanie]

Description: We are primarily a software company. However, on occasion clients do require boutique hardware solutions. When working with these we quite often interact with industry/proprietary hardware and cannot guarantee the hardware that will be used along side it. Since we currently use ESP32-S3 in situations like these having a dedicated PID ensures reliable enumeration and prevents driver or PID conflicts across deployments.

Chip: ESP32-S3

Why: Because when delivering to a client we can't risk a already populated PID interfering with our software solutions.

Company: Sentient Computing (https://sencom.com.au/)

[Spritetm]

Just to understand the use case here: you want this PID as a shared PID for any boutique solution you deploy, meaning you'll be free from conflicts as long as your customers do not exchange non-compatible hardware along themselves? Or is this specific PID for one specific (boutique) product?

[Rubeanie]

Hi @Spritetm, thank you for your reply. What you've said there is 100% correct, our currently the goal is to reserve this PID as a shared identifier for all our boutique ESP32-S3 solutions. That way, each deployment to a client enumerates consistently and we avoid driver/PID conflicts. As we’re relatively new to hardware development, one PID covers our current needs.

[Rubeanie]

I've just rebased against upstream and bumped the PID following recent merges.

[Spritetm]

Thank you. As long as you can make sure the various non-compatible applications using this PID don't 'escape into the wild' in a situation where people get confused by it, I will allow this. If you ever have a non-boutique product (as in: a product sold to the general public), please request a separate PID for that.