From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Danny Kaehn <danny.kaehn@plexus.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
Andi Shyti <andi.shyti@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jiri Kosina <jikos@kernel.org>,
devicetree@vger.kernel.org, linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Ethan Twardy <ethan.twardy@plexus.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Leo Huang <leohu@nvidia.com>, Arun D Patil <arundp@nvidia.com>,
Willie Thai <wthai@nvidia.com>,
Ting-Kai Chen <tingkaic@nvidia.com>
Subject: Re: [PATCH v12 0/3] Firmware Support for USB-HID Devices and CP2112
Date: Wed, 26 Nov 2025 20:29:18 +0200 [thread overview]
Message-ID: <aSdG_mXJXgsQ5VUG@smile.fi.intel.com> (raw)
In-Reply-To: <20251126-cp2112-dt-v12-0-2cdba6481db3@plexus.com>
On Wed, Nov 26, 2025 at 11:05:23AM -0600, Danny Kaehn wrote:
> This patchset allows USB-HID devices to have Firmware bindings through sharing
> the USB fwnode with the HID driver, and adds such a binding and driver
> implementation for the CP2112 USB to SMBus Bridge (which necessitated the
> USB-HID change). This change allows a CP2112 permanently attached in hardware to
> be described in DT and ACPI and interoperate with other drivers.
>
> Changes in v12:
> - dt-binding changes:
> - Drop "on the host controller" from top-level description based on
> comment from Rob H.
> - Correct "Properties must precede subnodes" dt_binding_check error by
> moving gpio_chip-related properties above the i2c subnode in the
> binding and in the example.
> - Include `interrupt-controller` property in the example
> - Modify hid-cp2112.c to support separate schemas for DT vs. ACPI - DT
> combines gpio subnode with the CP2112's node, but will have an I2C
> subnode; while ACPI will maintain separate child nodes for the GPIO
> I2C devices
Thanks for pursuing this! I have a few comments, but in general I'm fine with
the design.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-11-26 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 17:05 [PATCH v12 0/3] Firmware Support for USB-HID Devices and CP2112 Danny Kaehn
2025-11-26 17:05 ` [PATCH v12 1/3] dt-bindings: i2c: Add CP2112 HID USB to SMBus Bridge Danny Kaehn
2025-11-27 7:24 ` Krzysztof Kozlowski
2025-11-26 17:05 ` [PATCH v12 2/3] HID: cp2112: Fwnode Support Danny Kaehn
2025-11-26 18:27 ` Andy Shevchenko
2025-11-26 19:32 ` Danny Kaehn
2025-11-26 21:23 ` Andy Shevchenko
2025-11-26 17:05 ` [PATCH v12 3/3] HID: cp2112: Configure I2C Bus Speed from Firmware Danny Kaehn
2025-11-26 18:28 ` Andy Shevchenko
2025-11-26 18:29 ` Andy Shevchenko [this message]
2025-11-27 7:20 ` [PATCH v12 0/3] Firmware Support for USB-HID Devices and CP2112 Krzysztof Kozlowski
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=aSdG_mXJXgsQ5VUG@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=arundp@nvidia.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=bentiss@kernel.org \
--cc=conor+dt@kernel.org \
--cc=danny.kaehn@plexus.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=ethan.twardy@plexus.com \
--cc=jikos@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=leohu@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tingkaic@nvidia.com \
--cc=wthai@nvidia.com \
/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;
as well as URLs for NNTP newsgroup(s).