From: Fabio Estevam <festevam@denx.de>
To: Conor Dooley <conor@kernel.org>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: trivial-devices: Remove the OV5642 entry
Date: Tue, 01 Aug 2023 18:18:29 -0300 [thread overview]
Message-ID: <f9ab7525f048f3ce814d89f106947c34@denx.de> (raw)
In-Reply-To: <20230801-dividers-chooser-bd0df9b72d91@spud>
On 01/08/2023 18:13, Conor Dooley wrote:
> On Tue, Aug 01, 2023 at 06:10:52PM -0300, Fabio Estevam wrote:
>> On 01/08/2023 17:47, Conor Dooley wrote:
>>
>> > Removing it without re-adding it elsewhere does not seem right, since
>> > there'll now be some undocumented compatibles in the tree, no?
>>
>> Currently, there is no ov5642 support in the kernel.
>
> It is present in devicetrees.
Yes, and none of them have the ov5642 camera functional:
arch/arm/boot/dts/nxp/imx/imx53-smd.dts
arch/arm/boot/dts/nxp/imx/imx6qdl-sabrelite.dtsi
arch/arm/boot/dts/nxp/imx/imx6qdl-sabresd.dtsi
>> If someone adds the support for the ov5642 camera, then a specific
>> binding
>> will have to be created.
>>
>> I prefer to remove it from trivial-devices to avoid confusion.
>>
>> As is, it gives a false impression that ov5642 is supported and that
>> it
>> is a trivial device.
>
> The latter only do I agree with.
Care to explain how ov5642 is supported by the current mainline kernel?
next prev parent reply other threads:[~2023-08-01 21:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 17:00 [PATCH] dt-bindings: trivial-devices: Remove the OV5642 entry Fabio Estevam
2023-08-01 20:47 ` Conor Dooley
2023-08-01 21:10 ` Fabio Estevam
2023-08-01 21:13 ` Conor Dooley
2023-08-01 21:18 ` Fabio Estevam [this message]
2023-08-01 21:28 ` Conor Dooley
2023-08-01 21:43 ` Fabio Estevam
2023-08-01 21:57 ` Conor Dooley
2023-08-20 8:14 ` Krzysztof Kozlowski
2023-08-20 13:45 ` Fabio Estevam
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=f9ab7525f048f3ce814d89f106947c34@denx.de \
--to=festevam@denx.de \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).