From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Danny Kaehn <kaehndan@gmail.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
jikos@kernel.org, benjamin.tissoires@redhat.com
Cc: devicetree@vger.kernel.org, linux-input@vger.kernel.org,
ethan.twardy@plexus.com
Subject: Re: [PATCH 2/4] Share USB device devicetree node with child HID device
Date: Sun, 29 Jan 2023 12:05:25 +0100 [thread overview]
Message-ID: <07e44a94-70e3-fcb7-a2b7-086775ebc560@linaro.org> (raw)
In-Reply-To: <20230128202622.12676-3-kaehndan@gmail.com>
On 28/01/2023 21:26, Danny Kaehn wrote:
> USB HID core now shares its devicetree of_node with its child HID device.
> Since there can only be one HID device on a USB interface, it is redundant
> to specify a hid node under the USB device (and further, binding this way
> isn't currently possible, as hid_driver does not support of_match_table).
>
Here and in other patches:
Use subject prefixes matching the subsystem (which you can get for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching).
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-01-29 11:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 20:26 [PATCH 0/4] DeviceTree Support for USB-HID Devices and CP2112 Danny Kaehn
2023-01-28 20:26 ` [PATCH 1/4] dt-bindings: hid: Add CP2112 HID USB to SMBus Bridge Danny Kaehn
2023-01-29 11:05 ` Krzysztof Kozlowski
2023-01-29 11:33 ` Krzysztof Kozlowski
2023-01-31 0:25 ` Daniel Kaehn
2023-01-28 20:26 ` [PATCH 2/4] Share USB device devicetree node with child HID device Danny Kaehn
2023-01-29 11:05 ` Krzysztof Kozlowski [this message]
2023-01-28 20:26 ` [PATCH 3/4] Fix CP2112 driver not registering GPIO IRQ chip as threaded Danny Kaehn
2023-01-28 20:26 ` [PATCH 4/4] CP2112 Devicetree Support Danny Kaehn
2023-01-29 11:06 ` Krzysztof Kozlowski
2023-01-31 1:06 ` Daniel Kaehn
2023-01-31 16:45 ` Krzysztof Kozlowski
2023-01-30 16:29 ` [PATCH 0/4] DeviceTree Support for USB-HID Devices and CP2112 Benjamin Tissoires
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=07e44a94-70e3-fcb7-a2b7-086775ebc560@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=benjamin.tissoires@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=ethan.twardy@plexus.com \
--cc=jikos@kernel.org \
--cc=kaehndan@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=robh+dt@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).