mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Ernest Van Hoecke <ernestvanhoecke@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Kieran Bingham <kieran.bingham@ideasonboard.com>,
	Francesco Dolcini <francesco.dolcini@toradex.com>,
	Dave Stevenson <dave.stevenson@raspberrypi.com>,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Ernest Van Hoecke <ernest.vanhoecke@toradex.com>
Subject: Re: [PATCH v2 3/6] dt-bindings: connector: Add Toradex camera connector
Date: Sun, 11 Oct 2026 22:04:07 +0100	[thread overview]
Message-ID: <20261011-expulsion-frivolous-690de090cf9d@spud> (raw)
In-Reply-To: <20261002-prepaid-retired-3d2c9cbc035e@spud>

[-- Attachment #1: Type: text/plain, Size: 3377 bytes --]

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@toradex.com>
> > 
> > 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@toradex.com>
> > ---
> >  .../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@toradex.com>
> > +  - Toradex Linux BSP Team <linux-bsp@toradex.com>
> > +
> > +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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-10-11 21:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 11:44 [PATCH v2 0/6] arm64: dts: freescale: Add Verdin iMX8M OV5640 and Verdin iMX8MP M7 support Ernest Van Hoecke
2026-10-01 11:44 ` [PATCH v2 1/6] arm64: dts: freescale: imx8mp-verdin: Add Cortex-M7 remoteproc Ernest Van Hoecke
2026-10-01 14:19   ` Frank Li
2026-10-02  8:32     ` Ernest Van Hoecke
2026-10-01 11:44 ` [PATCH v2 2/6] arm64: dts: freescale: imx8mp-verdin: Add Cortex-M7 UART_4 overlay Ernest Van Hoecke
2026-10-01 14:18   ` Frank Li
2026-10-01 11:44 ` [PATCH v2 3/6] dt-bindings: connector: Add Toradex camera connector Ernest Van Hoecke
2026-10-01 14:14   ` Frank Li
2026-10-02 17:05   ` Conor Dooley
2026-10-11 21:04     ` Conor Dooley [this message]
2026-10-21 15:30     ` Ernest Van Hoecke
2026-10-21 16:06       ` Conor Dooley
2026-10-01 11:44 ` [PATCH v2 4/6] arm64: dts: freescale: imx8m{m,p}-verdin: Add camera connector nexus Ernest Van Hoecke
2026-10-01 11:44 ` [PATCH v2 5/6] arm64: dts: freescale: imx8m{m,p}-verdin: Add shared OV5640 overlays Ernest Van Hoecke
2026-10-01 11:44 ` [PATCH v2 6/6] arm64: dts: freescale: imx8mp-verdin: Add mezzanine " Ernest Van Hoecke

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=20261011-expulsion-frivolous-690de090cf9d@spud \
    --to=conor@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ernest.vanhoecke@toradex.com \
    --cc=ernestvanhoecke@gmail.com \
    --cc=festevam@gmail.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@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

all inboxes | Powered by JetHome®