public inbox for linux-input@vger.kernel.org
 help / color / mirror / Atom feed
From: Neil Armstrong <neil.armstrong@linaro.org>
To: Conor Dooley <conor@kernel.org>
Cc: Support Opensource <support.opensource@diasemi.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Roy Im <roy.im.opensource@diasemi.com>,
	linux-input@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: input: convert dlg,da7280.txt to dt-schema
Date: Fri, 6 Dec 2024 09:24:35 +0100	[thread overview]
Message-ID: <5d1ba835-354b-48d3-83fa-a3e70992e57e@linaro.org> (raw)
In-Reply-To: <20241204-duplicity-throwing-42a3faca5199@spud>

Hi Conor,

On 04/12/2024 18:55, Conor Dooley wrote:
> On Wed, Dec 04, 2024 at 11:54:35AM +0100, Neil Armstrong wrote:
> 
>> +  dlg,bemf-sens-enable:
>> +    type: boolean
>> +    description:
>> +      Enable for internal loop computations
>> +
>> +  dlg,freq-track-enable:
>> +    type: boolean
>> +    description:
>> +      Enable for resonant frequency tracking
>> +
>> +  dlg,acc-enable:
>> +    type: boolean
>> +    description:
>> +      Enable for active acceleration
>> +
>> +  dlg,rapid-stop-enable:
>> +    type: boolean
>> +    description:
>> +      Enable for rapid stop
>> +
>> +  dlg,amp-pid-enable:
>> +    type: boolean
> 
> Shouldn't these ones be "flag"?

Yes, I'll switch to it

> 
>> +    description:
>> +      Enable for the amplitude PID
>> +
>> +  dlg,mem-array:
>> +    $ref: /schemas/types.yaml#/definitions/uint8-array
>> +    minItems: 100
>> +    description:
>> +      Customized waveform memory (patterns) data downloaded to the device during initialization
>> +
>> +required:
>> +  - compatible
> 
> Is this right? The text binding has: compatible, reg, interrupt-parent,
> and a handful of vendor properties required. I don't see a mention for
> the drop in the commit message.

Damn I focused on all the other parts and forgot about the required...

Thanks,
Will fix this in v2.

Neil

> 
> Cheers,
> Conor.
> 
> 


      reply	other threads:[~2024-12-06  8:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04 10:54 [PATCH] dt-bindings: input: convert dlg,da7280.txt to dt-schema Neil Armstrong
2024-12-04 17:55 ` Conor Dooley
2024-12-06  8:24   ` Neil Armstrong [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=5d1ba835-354b-48d3-83fa-a3e70992e57e@linaro.org \
    --to=neil.armstrong@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=roy.im.opensource@diasemi.com \
    --cc=support.opensource@diasemi.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