From: Hans Verkuil <hverkuil@xs4all.nl>
To: Bryan Wu <cooloney@gmail.com>
Cc: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>,
Andy Walls <awalls@md.metrocast.net>, Milo Kim <milo.kim@ti.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
"media-workshop@linuxtv.org" <media-workshop@linuxtv.org>,
Sakari Ailus <sakari.ailus@iki.fi>,
Thierry Reding <thierry.reding@gmail.com>,
Oliver Schinagl <oliver+list@schinagl.nl>,
linux-pwm@vger.kernel.org, Hans Verkuil <hansverk@cisco.com>,
Bryan Wu <bryan.wu@canonical.com>,
Richard Purdie <rpurdie@rpsys.net>,
Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Paul Walmsley <paul@pwsan.com>
Subject: Re: [media-workshop] V2: Agenda for the Edinburgh mini-summit
Date: Mon, 21 Oct 2013 18:52:42 +0000 [thread overview]
Message-ID: <526577FA.7070602@xs4all.nl> (raw)
In-Reply-To: <CAK5ve-+PiRDEriYrCpbWq5WTPTq=n-xYZM0D46mDRAZWZi2GWw@mail.gmail.com>
On 10/21/2013 06:40 PM, Bryan Wu wrote:
> On Sat, Oct 19, 2013 at 1:25 PM, Ricardo Ribalda Delgado
> <ricardo.ribalda@gmail.com> wrote:
>> Please find the multi selection api proposal attached.
>>
>> See you in Edinburgh.
>>
>>
>> Thanks
>>
>> On Sat, Oct 19, 2013 at 2:17 AM, Bryan Wu <cooloney@gmail.com> wrote:
>>> On Wed, Oct 16, 2013 at 5:12 PM, Andy Walls <awalls@md.metrocast.net> wrote:
>>>> On Thu, 2013-10-17 at 08:36 +0900, Milo Kim wrote:
>>>>
>>>>>> That's current solution, we plan to unify this two API since those
>>>>>> chip are basically LED.
>>>>>>
>>>>>>> On the other hands, LM3642 has an indicator mode with flash/torch.
>>>>>>> Then, it will consist of 3 parts - MFD core, LED(indicator) and
>>>>>>> V4L2(flash/torch).
>>>>>>>
>>>>>>
>>>>>> So if one LED device driver can support that, we don't need these 3 parts.
>>>>>
>>>>> Let me clarify our discussion briefly.
>>>>>
>>>>> For the flash and torch, there are scattered user-space APIs.
>>>>> We need to unify them.
>>>>
>>>> Sorry for the late input.
>>>>
>>>> There are also subject matter illuminators (is that the same as torch?).
>>>> They may be LED or halogen incadescent bulbs that are integral to a
>>>> device such as the QX5 microscope:
>>>>
>>>> http://git.linuxtv.org/media_tree.git/blob/HEAD:/drivers/media/usb/cpia2/cpia2_v4l.c#l1152
>>>>
>>>> The V4L2 user controls ioctl()'s are used to control those two lamps
>>>> currently. Their activation seemed like a switch the user would want to
>>>> turn easily, via a GUI that contained other V4L2 device controls.
>>>>
>>>> Do these fit in anywhere into the unification? Not that I'm advocating
>>>> that. I just thought cases like this shouldn't be overlooked in deciding
>>>> what to do.
>>>>
>>>> Regards,
>>>> Andy
>>>>
>>>>> We are considering supporting V4L2 structures in the LED camera trigger.
>>>>> Then, camera application controls the flash/torch via not the LED sysfs
>>>>> but the V4L2 ioctl interface.
>>>>> So, changing point is the ledtrig-camera.c. No chip driver changes at all.
>>>>>
>>>>> Is it correct?
>>>>>
>>>>> Best regards,
>>>>> Milo
>>>>
>>>>
>>>
>>> Please find my proposal attached and probably my colleague Paul
>>> Walmsley will show up for this media mini summit if he is available.
>>>
>>> Thanks,
>>> -Bryan
>>
>>
>
> Is the time and location of media mini-summit fixed? My colleague
> might show up if it's not conflicted with ARM mini-summit.
It's in the Glamis room on Wednesday. We start at 9 am and the LED topic
is currently scheduled as the second topic so I expect that it will be
discussed between 9 and 10 am.
Regards,
Hans
next prev parent reply other threads:[~2013-10-21 18:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201309101134.32883.hansverk@cisco.com>
[not found] ` <52405427.6000002@samsung.com>
[not found] ` <52406E5C.2020709@schinagl.nl>
2013-09-23 20:27 ` V2: Agenda for the Edinburgh mini-summit Sylwester Nawrocki
2013-09-24 9:20 ` Thierry Reding
2013-10-07 21:06 ` Sakari Ailus
2013-10-07 22:24 ` [media-workshop] " Laurent Pinchart
2013-10-11 0:02 ` Bryan Wu
2013-10-11 7:38 ` Laurent Pinchart
2013-10-15 18:37 ` Bryan Wu
2013-10-15 18:50 ` Laurent Pinchart
2013-10-15 20:55 ` Bryan Wu
2013-10-15 19:03 ` Sylwester Nawrocki
2013-10-16 1:49 ` Milo Kim
2013-10-16 10:24 ` Sylwester Nawrocki
2013-10-16 17:17 ` Bryan Wu
2013-10-16 23:36 ` Milo Kim
2013-10-16 23:54 ` Bryan Wu
2013-10-16 23:56 ` Bryan Wu
2013-10-17 0:12 ` Andy Walls
2013-10-19 0:17 ` Bryan Wu
[not found] ` <CAPybu_2KRF_VHkjCEV8d7YOaZo27QJ=TxGTsUOeWO5X_tp8Ozw@mail.gmail.com>
2013-10-21 18:40 ` Bryan Wu
2013-10-21 18:52 ` Hans Verkuil [this message]
[not found] ` <CAPybu_1NZ-CfNkMt_stev5L9oL1MqSAhV03jQW7QoF=q4c2JzQ@mail.gmail.com>
2013-10-21 19:39 ` Hans Verkuil
2013-10-22 9:50 ` Hans Verkuil
2013-09-24 9:32 ` Thierry Reding
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=526577FA.7070602@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=awalls@md.metrocast.net \
--cc=bryan.wu@canonical.com \
--cc=cooloney@gmail.com \
--cc=hansverk@cisco.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=media-workshop@linuxtv.org \
--cc=milo.kim@ti.com \
--cc=oliver+list@schinagl.nl \
--cc=paul@pwsan.com \
--cc=ricardo.ribalda@gmail.com \
--cc=rpurdie@rpsys.net \
--cc=sakari.ailus@iki.fi \
--cc=sylvester.nawrocki@gmail.com \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).