devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org, pavel@ucw.cz
Subject: Re: [RFC 1/3] dt: bindings: Add a binding for flash devices associated to a sensor
Date: Fri, 5 May 2017 11:28:34 +0300	[thread overview]
Message-ID: <1e8d0a73-3f3f-410b-ca04-89fa35b1f0b9@linux.intel.com> (raw)
In-Reply-To: <20170504142730.tq4k3paofmyk5jul@earth>

Hi Sebastian,

Sebastian Reichel wrote:
> Hi Sakari,
>
> On Tue, May 02, 2017 at 01:25:47PM +0300, Sakari Ailus wrote:
>> Camera flash drivers (and LEDs) are separate from the sensor devices in
>> DT. In order to make an association between the two, provide the
>> association information to the software.
>>
>> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
>> ---
>>  Documentation/devicetree/bindings/media/video-interfaces.txt | 11 +++++++++++
>>  1 file changed, 11 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/media/video-interfaces.txt b/Documentation/devicetree/bindings/media/video-interfaces.txt
>> index 9cd2a36..d6c62bc 100644
>> --- a/Documentation/devicetree/bindings/media/video-interfaces.txt
>> +++ b/Documentation/devicetree/bindings/media/video-interfaces.txt
>> @@ -67,6 +67,17 @@ are required in a relevant parent node:
>>  		    identifier, should be 1.
>>   - #size-cells    : should be zero.
>>
>> +
>> +Optional properties
>> +-------------------
>> +
>> +- flash: An array of phandles that refer to the flash light sources
>> +  related to an image sensor. These could be e.g. LEDs. In case the LED
>> +  driver drives more than a single LED, then the phandles here refer to
>> +  the child nodes of the LED driver describing individual LEDs. Only
>> +  valid for device nodes that are related to an image sensor.
>
> s/driver/controller/g - DT describes HW. Otherwise

Driver is hardware in this case. :-) The chip that acts as a current 
sink or source for the LED is the driver. E.g. the adp1653 documentation 
describes the chip as "Compact, High Efficiency, High Power, Flash/Torch 
LED Driver with Dual Interface".

It might be still possible to improve the wording. Software oriented 
folks are more likely to misunderstand the meaning of driver here, but 
controller might seem ambiguous for hardware oriented people.

How about:

- flash: An array of phandles that refer to the flash light sources
   related to an image sensor. These could be e.g. LEDs. In case the LED
   driver (current sink or source chip for the LED(s)) drives more than a
   single LED, then the phandles here refer to the child nodes of the LED
   driver describing individual LEDs. Only valid for device nodes that are
   related to an image sensor.

-- 
Regards,

Sakari Ailus
sakari.ailus@linux.intel.com

  reply	other threads:[~2017-05-05  8:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02 10:25 [RFC 0/3] Document bindings for camera modules and associated flash devices Sakari Ailus
     [not found] ` <1493720749-31509-1-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-05-02 10:25   ` [RFC 1/3] dt: bindings: Add a binding for flash devices associated to a sensor Sakari Ailus
2017-05-04 14:27     ` Sebastian Reichel
2017-05-05  8:28       ` Sakari Ailus [this message]
2017-05-05  8:38         ` Sebastian Reichel
2017-05-02 10:25   ` [RFC 2/3] dt: bindings: Add lens-focus binding for image sensors Sakari Ailus
2017-05-04 14:33     ` Sebastian Reichel
2017-05-02 10:25   ` [RFC 3/3] dt: bindings: Add a binding for referencing EEPROM from camera sensors Sakari Ailus
     [not found]     ` <1493720749-31509-4-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-05-04 14:38       ` Sebastian Reichel
2017-05-05  8:49         ` Sakari Ailus
2017-05-04 22:01   ` [RFC 0/3] Document bindings for camera modules and associated flash devices Pavel Machek

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=1e8d0a73-3f3f-410b-ca04-89fa35b1f0b9@linux.intel.com \
    --to=sakari.ailus@linux.intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=sebastian.reichel@collabora.co.uk \
    /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).