From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Tobita, Tatsunosuke" <tatsunosuke.tobita@wacom.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Cheng, Ping" <Ping.Cheng@wacom.com>,
"Chen, Martin" <martin.chen@wacom.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Linux Input <linux-input@vger.kernel.org>
Subject: Re: Question for submitting a dt-binding besides an existing one covering enough for our device
Date: Wed, 4 Sep 2024 11:40:36 -0700 [thread overview]
Message-ID: <ZtippHCTtiz29IVq@google.com> (raw)
In-Reply-To: <PA4PR07MB7407FF98C5EA3F2E1CFA5D8E879C2@PA4PR07MB7407.eurprd07.prod.outlook.com>
Hi Tatsunosuke,
On Wed, Sep 04, 2024 at 06:26:40AM +0000, Tobita, Tatsunosuke wrote:
> Hi,
>
> Wacom is currently working on to add our dt-binding at
> /Documentation/devicetree/bindings/input/touchscreen. While doing
> that, we found another dt-binding which was already sufficient to
> detect our device and load the driver for it[1].
You pointed to a whole directory of bindings, based on the context
below I assume you are talking about this:
Documentation/devicetree/bindings/input/hid-over-i2c.yaml
>
> In this case, what can we do? hid-over-i2c dt-binding([1]) covers
> information enough for our device to be used under I2C interface.
> Therefore, the difference is seemingly going to be at "description".
> Do we just provide a yaml file containing only the some of the
> headers, such as id, schema, tiltle, and description items to submit
> our dt-binding?
If your controller is fully covered by hid-over-i2c.yaml binding then
I think you just need to add a new compatible to it. We already have
"wacom,w9013" there.
Otherwise follow examples such as:
Documentation/devicetree/bindings/input/elan,ekth6915.yaml
Documentation/devicetree/bindings/input/goodix,gt7375p.yaml
that are also hid-over-i2c devices but require special power up/down
handling.
Thanks.
--
Dmitry
parent reply other threads:[~2024-09-04 18:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <PA4PR07MB7407FF98C5EA3F2E1CFA5D8E879C2@PA4PR07MB7407.eurprd07.prod.outlook.com>]
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=ZtippHCTtiz29IVq@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=Ping.Cheng@wacom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=martin.chen@wacom.com \
--cc=robh@kernel.org \
--cc=tatsunosuke.tobita@wacom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.