public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Valek - 2N <jiriv@axis.com>
To: Rob Herring <robh@kernel.org>
Cc: <krzysztof.kozlowski+dt@linaro.org>, <dmitry.torokhov@gmail.com>,
	<devicetree@vger.kernel.org>, <linux-input@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH v4 1/2] dt-bindings: input: microchip,cap11xx: add advanced sensitivity settings
Date: Tue, 11 Jul 2023 15:22:31 +0200	[thread overview]
Message-ID: <3b02a7f4-4598-93cd-757d-27bbfdae5182@axis.com> (raw)
In-Reply-To: <20230629151635.GA3003066-robh@kernel.org>

On 6/29/23 17:16, Rob Herring wrote:
> On Tue, Jun 27, 2023 at 08:53:15AM +0200, Jiri Valek - 2N wrote:
>> Add support for advanced sensitivity settings and signal guard feature.
>>
>> Signed-off-by: Jiri Valek - 2N <jiriv@axis.com>
>> ---
>>  .../bindings/input/microchip,cap11xx.yaml     | 77 +++++++++++++++++--
>>  1 file changed, 72 insertions(+), 5 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/input/microchip,cap11xx.yaml b/Documentation/devicetree/bindings/input/microchip,cap11xx.yaml
>> index 5fa625b5c5fb..b69dac1fba0e 100644
>> --- a/Documentation/devicetree/bindings/input/microchip,cap11xx.yaml
>> +++ b/Documentation/devicetree/bindings/input/microchip,cap11xx.yaml
>> @@ -45,13 +45,13 @@ properties:
>>        Enables the Linux input system's autorepeat feature on the input device.
>>  
>>    linux,keycodes:
>> -    minItems: 6
>> -    maxItems: 6
>> +    minItems: 3
>> +    maxItems: 8
>>      description: |
>>        Specifies an array of numeric keycode values to
>>        be used for the channels. If this property is
>>        omitted, KEY_A, KEY_B, etc are used as defaults.
>> -      The array must have exactly six entries.
>> +      The number of entries must correspond to the number of channels.
> 
> This change seems unrelated? Or maybe advanced sensitivity means more 
> channels? If so, explain this in the commit msg.

This driver is already used for more CAPxxxx types.
The smallest have only 3 inputs and the biggest one have 8 inputs.
So keycode definition array length can be from 3 to 8 items long.

> 
>>  
>>    microchip,sensor-gain:
>>      $ref: /schemas/types.yaml#/definitions/uint32
>> @@ -70,6 +70,55 @@ properties:
>>        open drain. This property allows using the active
>>        high push-pull output.
>>  
>> +  microchip,sensitivity-delta-sense:
>> +    $ref: /schemas/types.yaml#/definitions/uint32
>> +    default: 32
>> +    enum: [1, 2, 4, 8, 16, 32, 64, 128]
>> +    description:
>> +      Optional parameter. Controls the sensitivity multiplier of a touch detection.
>> +      At the more sensitive settings, touches are detected for a smaller delta
>> +      capacitance corresponding to a “lighter” touch.
>> +
>> +  microchip,signal-guard:
>> +    $ref: /schemas/types.yaml#/definitions/uint32-array
>> +    minItems: 3
>> +    maxItems: 8
>> +    items:
>> +      minimum: 0
>> +      maximum: 1
>> +    description: |
>> +      Optional parameter supported only for CAP129x.
>> +      0 - off
>> +      1 - on
>> +      The signal guard isolates the signal from virtual grounds.
>> +      If enabled then the behavior of the channel is changed to signal guard.
>> +      The number of entries must correspond to the number of channels.
>> +
>> +  microchip,input-treshold:
>> +    $ref: /schemas/types.yaml#/definitions/uint32-array
>> +    minItems: 3
>> +    maxItems: 8
>> +    items:
>> +      minimum: 0
>> +      maximum: 127
>> +    description:
>> +      Optional parameter. Specifies the delta threshold that is used to
>> +      determine if a touch has been detected.
>> +      The number of entries must correspond to the number of channels.
>> +
>> +  microchip,calib-sensitivity:
>> +    $ref: /schemas/types.yaml#/definitions/uint32-array
>> +    minItems: 3
>> +    maxItems: 8
>> +    items:
>> +      minimum: 1
>> +      maximum: 4
>> +    description:
>> +      Optional parameter supported only for CAP129x. Specifies an array of
>> +      numeric values that controls the gain used by the calibration routine to
>> +      enable sensor inputs to be more sensitive for proximity detection.
>> +      The number of entries must correspond to the number of channels.
>> +
>>  patternProperties:
>>    "^led@[0-7]$":
>>      type: object
>> @@ -98,10 +147,23 @@ allOf:
>>          compatible:
>>            contains:
>>              enum:
>> -              - microchip,cap1106
>> +              - microchip,cap1188
>>      then:
>>        patternProperties:
>> -        "^led@[0-7]$": false
>> +        "^led@[0-7]$": true
>> +
>> +  - if:
>> +      properties:
>> +        compatible:
>> +          contains:
>> +            enum:
>> +              - microchip,cap1293
>> +              - microchip,cap1298
>> +
>> +    then:
>> +      properties:
>> +        microchip,signal-guard: true
>> +        microchip,calib-sensitivity: true
> 
> This 'if' doesn't do anything. These properties are already allowed. You 
> need an if for the cases they aren't allowed.

Oh, thanks for the explanation. I will fix it.

> 
>>  
>>  required:
>>    - compatible
>> @@ -122,6 +184,11 @@ examples:
>>          reg = <0x28>;
>>          autorepeat;
>>          microchip,sensor-gain = <2>;
>> +        microchip,sensitivity-delta-sense = <16>;
>> +
>> +        microchip,signal-guard = <0>, <0>, <0>, <0>, <0>, <0>;
>> +        microchip,input-treshold = <21>, <18>, <46>, <46>, <46>, <21>;
>> +        microchip,calib-sensitivity = <1>, <2>, <2>, <1>, <1>, <2>;
>>  
>>          linux,keycodes = <103>,	/* KEY_UP */
>>                           <106>,	/* KEY_RIGHT */
>> -- 
>> 2.25.1
>>

BR
Jiri


  reply	other threads:[~2023-07-11 13:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27  6:53 [PATCH v4 0/2] Input: cap11xx add advanced sensitivity settings Jiri Valek - 2N
2023-06-27  6:53 ` [PATCH v4 1/2] dt-bindings: input: microchip,cap11xx: " Jiri Valek - 2N
2023-06-29 15:16   ` Rob Herring
2023-07-11 13:22     ` Jiri Valek - 2N [this message]
2023-06-27  6:53 ` [PATCH v4 2/2] Input: cap11xx - " Jiri Valek - 2N
2023-06-28 19:06   ` Dmitry Torokhov
2023-07-11 13:05     ` Jiri Valek - 2N

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=3b02a7f4-4598-93cd-757d-27bbfdae5182@axis.com \
    --to=jiriv@axis.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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