Re: Firmware Support for USB-HID Devices and CP2112

[Andy Shevchenko <andriy.shevchenko@intel.com>]

On Tue, Nov 10, 2026 at 12:56:03PM -0600, Danny Kaehn wrote:
> On Wed, Nov 04, 2026 at 07:19:46PM +0200, Andy Shevchenko wrote:
> > In lieu of this discussion [1] I just realised that CP2112 misses the
> > documentation piece under Documentation/firmware-guide/acpi/ on how
> > it's supposed to be enumerated. Danny, can you add a such, please?
> > 
> > [1]: 20261003095924.1370238-1-thierry.reding@kernel.org

> Apologies about the delay here -- getting an environment set up to send
> kernel email always takes some time :)
> 
> I will target getting something sent out for this by the end of the
> week.
> 
> This can wait for the review of course, but since it seems like
> this is a relatively unblazed trail (ACPI "binding" documents for
> specific drivers), do you have opinions on whether a directory tree
> should be started for driver documents like this? (i.e. an i2c
> subdirectory?), or would you prefer it just be added to the top-level
> directory? It seems like there also isn't yet a naming convention for
> these -- presumably the "silabs,cp2112.rst" name would be too
> "DeviceTree-ish"... maybe "i2c-silabs-cp2112.rst" if kept at the
> top-level...

Hmm... Since you rose this topic, I think we can move i2c-mux ACPI
documentation to i2c folder and create there the support for that specific
hardware in DTish naming schema.

-- 
With Best Regards,
Andy Shevchenko