devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Danny Kaehn <danny.kaehn@plexus.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Benjamin Tissoires <bentiss@kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: 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>
Subject: Re: [PATCH v11 1/4] dt-bindings: i2c: Add CP2112 HID USB to SMBus Bridge
Date: Thu, 6 Jun 2024 08:28:34 +0200	[thread overview]
Message-ID: <e183c4ab-e48e-4c9f-be31-13b16ad466b6@kernel.org> (raw)
In-Reply-To: <20240605-cp2112-dt-v11-1-d55f0f945a62@plexus.com>

On 06/06/2024 01:12, Danny Kaehn wrote:
> This is a USB HID device which includes an I2C controller and 8 GPIO pins.
> 
> The binding allows describing the chip's gpio and i2c controller in DT
> using the subnodes named "gpio" and "i2c", respectively. This is
> intended to be used in configurations where the CP2112 is permanently
> connected in hardware.
> 
> Signed-off-by: Danny Kaehn <danny.kaehn@plexus.com>
> ---
>  .../devicetree/bindings/i2c/silabs,cp2112.yaml     | 105 +++++++++++++++++++++
>  1 file changed, 105 insertions(+)

So this is v11 but was never tested?

Changelog does not help me understanding what happened with this binding...

Best regards,
Krzysztof


  parent reply	other threads:[~2024-06-06  6:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 23:12 [PATCH v11 0/4] Firmware Support for USB-HID Devices and CP2112 Danny Kaehn
2024-06-05 23:12 ` [PATCH v11 1/4] dt-bindings: i2c: Add CP2112 HID USB to SMBus Bridge Danny Kaehn
2024-06-06  0:18   ` Rob Herring (Arm)
2024-06-06  6:28   ` Krzysztof Kozlowski [this message]
2024-06-06 15:12     ` Danny Kaehn
2024-06-06 15:18   ` Rob Herring
2024-06-06 16:24     ` Danny Kaehn
2024-06-06 19:49       ` Andy Shevchenko
2024-06-07 18:38         ` Danny Kaehn
2024-06-05 23:12 ` [PATCH v11 2/4] HID: usbhid: Share USB device firmware node with child HID device Danny Kaehn
2024-06-05 23:43   ` Andy Shevchenko
2024-06-06  7:31     ` Benjamin Tissoires
2024-06-05 23:12 ` [PATCH v11 3/4] HID: cp2112: Fwnode Support Danny Kaehn
2024-06-05 23:39   ` Andy Shevchenko
2024-06-05 23:12 ` [PATCH v11 4/4] HID: cp2112: Configure I2C Bus Speed from Firmware Danny Kaehn
2024-06-05 23:42 ` [PATCH v11 0/4] Firmware Support for USB-HID Devices and CP2112 Andy Shevchenko
2024-06-06 15:54   ` Danny Kaehn
2024-06-06 19:47     ` Andy Shevchenko
2024-06-07 17:20       ` Danny Kaehn
2024-06-06  7:30 ` (subset) " Benjamin Tissoires
2025-07-29 14:53 ` Re " Willie Thai
2025-07-29 17:49   ` Danny Kaehn
2025-08-05 21:32     ` Andy Shevchenko
2025-08-06 11:07     ` Willie Thai

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=e183c4ab-e48e-4c9f-be31-13b16ad466b6@kernel.org \
    --to=krzk@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=bentiss@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=linux-input@vger.kernel.org \
    --cc=robh@kernel.org \
    /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).