linux-kernel - Re: [PATCH v6 2/3] dt-bindings: input: Add TouchNetix axiom touchscreen

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f07d7557-c190-4154-8fc7-6a3850b1d162@linaro.org>
Date: Wed, 31 Jan 2024 08:28:43 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Rob Herring <robh@...nel.org>
Cc: Kamel Bouhara <kamel.bouhara@...tlin.com>,
 Dmitry Torokhov <dmitry.torokhov@...il.com>,
 Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
 Conor Dooley <conor+dt@...nel.org>, Henrik Rydberg <rydberg@...math.org>,
 linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
 devicetree@...r.kernel.org, Marco Felsch <m.felsch@...gutronix.de>,
 Jeff LaBundy <jeff@...undy.com>, catalin.popescu@...ca-geosystems.com,
 mark.satterthwaite@...chnetix.com,
 Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
 Gregory Clement <gregory.clement@...tlin.com>,
 bsp-development.geo@...ca-geosystems.com
Subject: Re: [PATCH v6 2/3] dt-bindings: input: Add TouchNetix axiom
 touchscreen

On 30/01/2024 23:28, Rob Herring wrote:
> On Fri, Jan 26, 2024 at 12:46:16PM +0100, Krzysztof Kozlowski wrote:
>> On 25/01/2024 17:58, Kamel Bouhara wrote:
>>> +  reset-gpios:
>>> +    maxItems: 1
>>> +
>>> +  vdda-supply:
>>> +    description: Analog power supply regulator on VDDA pin
>>> +
>>> +  vddi-supply:
>>> +    description: I/O power supply regulator on VDDI pin
>>> +
>>> +  startup-time-ms:
>>> +    description: delay after power supply regulator is applied in ms
>>
>> That's a regulator property - ramp up time.
> 
> I'm sure there's an existing property name that could be used.
> 
> But why is it needed? Is it variable per board with the same device? If 
> not, it should be implied by the compatible.

I meant, that regulators have such property. Unless this is coming from
the device needs, not from the regulator?

Best regards,
Krzysztof