devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willie Thai <wthai@nvidia.com>
To: <danny.kaehn@plexus.com>
Cc: <andriy.shevchenko@linux.intel.com>, <arundp@nvidia.com>,
	<bartosz.golaszewski@linaro.org>, <bentiss@kernel.org>,
	<devicetree@vger.kernel.org>, <dkodihalli@nvidia.com>,
	<dmitry.torokhov@gmail.com>, <ethan.twardy@plexus.com>,
	<jikos@kernel.org>, <krzk+dt@kernel.org>,
	<linux-input@vger.kernel.org>, <mhn@nvidia.com>,
	<rastekar@nvidia.com>, <robh@kernel.org>, <tingkaic@nvidia.com>,
	<wthai@nvidia.com>
Subject: Re: Re [PATCH v11 0/4] Firmware Support for USB-HID Devices and CP2112
Date: Wed, 6 Aug 2025 11:07:20 +0000	[thread overview]
Message-ID: <20250806110720.680587-1-wthai@nvidia.com> (raw)
In-Reply-To: <20250729174951.GB4111945@LNDCL34533.neenah.na.plexus.com>

>> Hi Danny,
>> 
>> I hope this message finds you well.
>> Thank you for the patch set — it’s exactly what we need for the I2C-over-USB feature in our new products.
>> Could you please let us know when we can expect the next version of the patch set?
>> If you've paused work on it, we're happy to take over and continue from where you left off.
>> 
>> Thanks!
>
> Thanks for reaching out!
>
> Apologies, I haven't been working on this in a while, and have only been able
> to intermittently return to attempt to bring it forward.
>
> Feel free to take over and move this forward! I'm not sure what the protocol
> is for that, as far as changelogs and versions and whatnot. If your product's
> timeline for needing this mainlined is not urgent; however, I can prioritize
> coming back to this and having a v12 submitted, likely by the end of next
> week, to remove the overhead needed for you to assume ownership of the
> patchset.
>
> The last several versions of this patchset have all revolved around trying
> to get this change working for ACPI as well as DeviceTree in such a way which
> make the ACPI and DeviceTree interface/binding acceptable to their respective
> maintainers. With this latest version, it seemed that there was not going to
> be any consensus between the two firmware languages, so it seemed an entirely
> different binding/interface and corresponding logic in the device driver
> would be needed. This seems unfortunate, as it seemed the whole purpose of
> the fwnode / device_*() functions was to unify the driver interface to the
> firmware language used... but this is presumably a special case, being almost
> exclusively a device composed of different generic device functions...
>
> Let me know if you plan to take this over and if there's any
> documentation/context/test procedures you would need from me; else I would be
> happy to start moving this forward again now that there is someone waiting
> on it.
>
> Thanks
> 
> Danny Kaehn

Hi Danny,

Thanks for your response !
Currently, your patch is working fine with our feature without ACPI.
We can use it downstream first.
Please let me know if you need any support !

Thanks !

      parent reply	other threads:[~2025-08-06 11:07 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
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 [this message]

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=20250806110720.680587-1-wthai@nvidia.com \
    --to=wthai@nvidia.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arundp@nvidia.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=bentiss@kernel.org \
    --cc=danny.kaehn@plexus.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dkodihalli@nvidia.com \
    --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=mhn@nvidia.com \
    --cc=rastekar@nvidia.com \
    --cc=robh@kernel.org \
    --cc=tingkaic@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).