linux-kernel - Re: [PATCH] dt-bindings: trivial-devices: Remove the OV5642 entry

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: <c9758ac5-489e-3fda-9ad2-020a9cc15a04@linaro.org>
Date:   Sun, 20 Aug 2023 10:14:20 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Conor Dooley <conor@...nel.org>, Fabio Estevam <festevam@...x.de>
Cc:     robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
        conor+dt@...nel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: trivial-devices: Remove the OV5642 entry

On 01/08/2023 23:57, Conor Dooley wrote:
> On Tue, Aug 01, 2023 at 06:43:58PM -0300, Fabio Estevam wrote:
>> Hi Conor,
>>
>> On 01/08/2023 18:28, Conor Dooley wrote:
>>
>>> I never said it was chief. Please re-read the quoted text.
>>
>> trivial-devices.yaml throws the following warning:
>>
>> imx6q-sabrelite.dtb: camera@42: 'clock-names', 'clocks', 'gp-gpios', 'port',
>> 'powerdown-gpios', 'reset-gpios' do not match any of the regexes:
>> 'pinctrl-[0-9]+'
>> 	from schema $id: http://devicetree.org/schemas/trivial-devices.yaml#
>>
>> Would it make sense to remove ovti,ov5642 from the trivial-devices bindings
>> as well as from the
>> following devicetrees?
> 
> I would rather that you documented it, rather than removed it, please.

Removal from DTS is rather discouraged, because DTS and these nodes
could be used in other systems. The best is to fully document the
device, regardless whether Linux supports it or not.

Dropping from trivial-devices could work, because it does not change
much for our schema - one warning goes to other warning...

Best regards,
Krzysztof