From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Alex Tran <alex.t.tran@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Pavel Machek <pavel@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Pavel Machek <pavel@ucw.cz>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] media: dt-bindings: i2c: toshiba,et8ek8: Convert to DT schema
Date: Sat, 27 Dec 2025 13:34:17 +0200 [thread overview]
Message-ID: <20251227113417.GI4094@pendragon.ideasonboard.com> (raw)
In-Reply-To: <b1637433-6bbf-4e08-8f58-0e9bad37b790@kernel.org>
On Sat, Dec 27, 2025 at 12:23:15PM +0100, Krzysztof Kozlowski wrote:
> On 27/12/2025 12:12, Laurent Pinchart wrote:
> > Regarding flash-leds, none of the existing bindings set a constraint on
> > the number of items. I'm not sure there are use cases for more than two,
> > but the number of flash LEDs is not an intrinsic properties of the image
> > sensor. I think listing
> >
> > flash-leds: true
> >
> > is correct. Sakari may have more information.
>
> IOW, that's not a pin going from the sensor to the LED but rather final
> board/system design? And same sensor could be used that way with
> arbitrary number of LEDs?
Yes, those are LEDs typically controlled by a GPIO of the SoC, not LEDs
tied to a pin of the sensor. No LED, one LED or two LEDs are the most
common cases (the second LED would typically be an indicator LED, to
indicate when the camera is active), but a system could use more than
two at least in theory.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2025-12-27 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 21:59 [PATCH v2 0/2] Convert et8ek8 and omap3isp bindings to DT schema Alex Tran
2025-12-24 21:59 ` [PATCH v2 1/2] media: dt-bindings: i2c: toshiba,et8ek8: Convert " Alex Tran
2025-12-25 8:40 ` Krzysztof Kozlowski
2025-12-25 8:57 ` Alex Tran
2025-12-25 9:08 ` Krzysztof Kozlowski
2025-12-27 11:12 ` Laurent Pinchart
2025-12-27 11:23 ` Krzysztof Kozlowski
2025-12-27 11:34 ` Laurent Pinchart [this message]
2025-12-24 21:59 ` [PATCH v2 2/2] media: dt-bindings: ti,omap3isp: " Alex Tran
2025-12-25 8:44 ` Krzysztof Kozlowski
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=20251227113417.GI4094@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=alex.t.tran@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=pavel@kernel.org \
--cc=pavel@ucw.cz \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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