[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251227113417.GI4094@pendragon.ideasonboard.com>
Date: Sat, 27 Dec 2025 13:34:17 +0200
From: Laurent Pinchart <laurent.pinchart@...asonboard.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Alex Tran <alex.t.tran@...il.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Pavel Machek <pavel@...nel.org>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Pavel Machek <pavel@....cz>, linux-media@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] media: dt-bindings: i2c: toshiba,et8ek8: Convert
to DT schema
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
Powered by blists - more mailing lists