Re: [PATCH v2 3/6] dt-bindings: connector: Add Toradex camera connector

[Conor Dooley]

On Fri, Oct 02, 2026 at 06:05:24PM +0100, Conor Dooley wrote:
> On Thu, Oct 01, 2026 at 01:44:11PM +0200, Ernest Van Hoecke wrote:
> > From: Ernest Van Hoecke <ernest.vanhoecke@xxxxxxxxxxx>
> > 
> > Toradex boards route the sideband signals of their 24-pin camera
> > connectors to different GPIO controllers. Camera overlays which name
> > those controllers directly must therefore be duplicated for each host
> > board.
> > 
> > Describe reset, power-down, detection and power-control as
> > connector-local GPIO functions. This lets an accessory overlay remain
> > independent of the host wiring. MIPI CSI-2, I2C, clocks and supplies
> > remain described separately because the GPIO nexus does not abstract
> > them.
> > 
> > Signed-off-by: Ernest Van Hoecke <ernest.vanhoecke@xxxxxxxxxxx>
> > ---
> >  .../connector/toradex,camera-connector.yaml        | 81 ++++++++++++++++++++++
> >  1 file changed, 81 insertions(+)
> > 
> > diff --git a/Documentation/devicetree/bindings/connector/toradex,camera-connector.yaml b/Documentation/devicetree/bindings/connector/toradex,camera-connector.yaml
> > new file mode 100644
> > index 000000000000..27fee3defde7
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/connector/toradex,camera-connector.yaml
> > @@ -0,0 +1,81 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/connector/toradex,camera-connector.yaml#
> > +$schema: http://devicetree.org/meta-schemas/base.yaml#
> > +
> > +title: Toradex camera connector GPIO nexus
> > +
> > +maintainers:
> > +  - Ernest Van Hoecke <ernest.vanhoecke@xxxxxxxxxxx>
> > +  - Toradex Linux BSP Team <linux-bsp@xxxxxxxxxxx>
> > +
> > +description: |
> > +  Toradex carrier boards share a common 24-pin, 0.5 mm pitch FFC/FPC camera
> > +  connector carrying MIPI CSI-2, I2C, clock, power, and sideband GPIO signals.
> > +  This binding describes the sideband signals as a GPIO nexus. The other
> > +  connector resources remain described by the surrounding board device tree.
> > +
> > +  The nexus exposes connector-local GPIO function numbers to camera overlays
> > +  and maps the functions wired by a carrier board to their GPIO controllers.
> > +  GPIO specifiers contain a function number followed by standard GPIO flags.
> > +  A board may omit functions which it does not wire.
> > +
> > +  The function numbers are:
> > +    - 0: Camera reset, connector pin 11
> > +    - 1: Camera power-down, connector pin 22
> > +    - 2: Camera identification, connector pin 23
> > +    - 3: Camera power control, connector pin 24
> > +
> > +properties:
> > +  compatible:
> > +    const: toradex,camera-connector
> 
> This seems overly generic, but I assume that's what it's actually called
> and if you make a new camera connector the name will be
> "camera connector 2" or something.

Since this came up during last weeks conference, figured I should
clarify that I was commenting on how the generic name, which typically is
something we try to avoid (because it is usually used when someone does
something like "sony,8-megapixel-camera"), was probably actually fine
here. I wasn't looking for a version to be embedded in the string. I
already mentioned this to Ernest after the talk, but mentioning it here
for everyone's benefit..

Attachment: signature.asc
Description: PGP signature