From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: Sakari Ailus <sakari.ailus@iki.fi>,
linux-leds@vger.kernel.org, linux-media@vger.kernel.org,
kyungmin.park@samsung.com, pavel@ucw.cz, cooloney@gmail.com,
rpurdie@rpsys.net, devicetree@vger.kernel.org, sre@kernel.org
Subject: Re: [PATCH v8 8/8] DT: samsung-fimc: Add examples for samsung,flash-led property
Date: Mon, 25 May 2015 16:28:22 +0200 [thread overview]
Message-ID: <55633186.1000004@samsung.com> (raw)
In-Reply-To: <55631AAC.6080507@samsung.com>
On 25/05/15 14:50, Jacek Anaszewski wrote:
>> On 23/05/15 14:03, Sakari Ailus wrote:
>>> >> On Thu, May 21, 2015 at 03:28:40PM +0200, Sylwester Nawrocki wrote:
>>>> >>> flash-leds = <&flash_xx &image_sensor_x>, <...>;
>>> >>
>>> >> One more matter to consider: xenon flash devices.
>>> >>
>>> >> How about samsung,camera-flashes (and ti,camera-flashes)? After pondering
>>> >> this awhile, I'm ok with removing the vendor prefix as well.
>>> >>
>>> >> Let me know what you think.
>> >
>> > I thought about it a bit more and I have some doubts about semantics
>> > as above. I'm fine with 'camera-flashes' as far as name is concerned.
>> >
>> > Perhaps we should put only phandles to leds or xenon flash devices
>> > in the 'camera-flashes' property. I think it would be more future
>> > proof in case there is more nodes needed to describe the camera flash
>> > (or a camera module) than the above two. And phandles to corresponding
>> > image sensor device nodes would be put in a separate property.
>
> Could you give examples of the cases you are thinking of?
I don't have any examples in mind ATM, I just wanted to point out
the above convention might not be flexible enough. Especially since
we already know there is more sub-devices within the camera module
than just flashes and image sensors.
>> > camera-flashes = <&flash_xx>, ...
>> > camera-flash-masters = <&image_sensor_x>, ...
>> >
>> > Then pairs at same index would describe a single flash, 0 would indicate
>> > a null entry if needed.
>
> When it should be needed?
Not sure if there is a real use case for null entries, it was just to
note we can skip any entry if needed - probably an irrelevant comment.
I could imagine 2 LEDs of which one is only triggered in software, so
it wouldn't have a 'camera-flash-masters' entry.
>> > Similarly we could create properties for other sub-devices of a camera
>> > module, like lenses, etc.
--
Regards,
Sylwester
next prev parent reply other threads:[~2015-05-25 14:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 14:10 [PATCH v8 0/8] LED / flash API integration Jacek Anaszewski
2015-05-20 14:10 ` [PATCH v8 1/8] media: Add registration helpers for V4L2 flash sub-devices Jacek Anaszewski
2015-05-20 14:44 ` Sakari Ailus
2015-05-20 14:10 ` [PATCH v8 2/8] leds: max77693: add support for V4L2 Flash sub-device Jacek Anaszewski
2015-05-20 14:59 ` Sakari Ailus
2015-05-20 20:02 ` Sakari Ailus
2015-05-20 14:10 ` [PATCH v8 3/8] DT: aat1290: Document handling external strobe sources Jacek Anaszewski
2015-05-20 14:10 ` [PATCH v8 4/8] leds: aat1290: add support for V4L2 Flash sub-device Jacek Anaszewski
2015-05-20 14:10 ` [PATCH v8 5/8] exynos4-is: Add support for v4l2-flash subdevs Jacek Anaszewski
2015-05-21 7:46 ` Sakari Ailus
2015-05-21 9:39 ` Jacek Anaszewski
2015-05-21 10:38 ` Sakari Ailus
2015-05-20 14:10 ` [PATCH v8 6/8] DT: s5c73m3: Add documentation for samsung,flash-led property Jacek Anaszewski
2015-05-20 14:10 ` [PATCH v8 7/8] DT: s5k6a3: " Jacek Anaszewski
2015-05-20 14:10 ` [PATCH v8 8/8] DT: samsung-fimc: Add examples " Jacek Anaszewski
2015-05-20 22:00 ` Sakari Ailus
2015-05-21 9:10 ` Jacek Anaszewski
[not found] ` <555DA119.9030904-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-05-21 11:32 ` Sakari Ailus
2015-05-21 11:32 ` Sakari Ailus
2015-05-21 13:28 ` Sylwester Nawrocki
2015-05-21 14:20 ` Sakari Ailus
2015-05-21 16:58 ` Sylwester Nawrocki
2015-05-21 23:27 ` Sakari Ailus
2015-05-23 12:03 ` Sakari Ailus
2015-05-25 12:00 ` Sylwester Nawrocki
2015-05-25 12:50 ` Jacek Anaszewski
2015-05-25 14:28 ` Sylwester Nawrocki [this message]
2015-05-25 15:20 ` Jacek Anaszewski
2015-05-25 20:56 ` Sakari Ailus
[not found] ` <55630EE1.90307-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-06-01 21:17 ` Sakari Ailus
2015-06-01 21:17 ` Sakari Ailus
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=55633186.1000004@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=cooloney@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=j.anaszewski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=sakari.ailus@iki.fi \
--cc=sre@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.