Re: [RFC] V4L2 API for flash devices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Sakari,

2011-03-29 ìí 11:41, Sakari Ailus ì ê:
> Kim, HeungJun wrote:
[snip]
>> I think it's not different method to turn on/off, whatever the mode name is.
>> But, the mode name DEDICATED is look more reasonable, because the reason 
>> which is devided FLASH and TORCH in the mode, is why only power up the led,
>> not sensor.
> 
> Sensor? Is the flash part of the sensor module for you?
Yes. The flash is a part of the sensor module(our case like M-5MOLS).
Precisely, the sensor internal core's gpio pin is connected with
external Flash LED, and the control master is the sensor internal core.
For turnning on the Flash LED, we should use I2C register access.
So, I think it's exactly matches with hardware strobe as you metioned.

> 
> I think it should be other factors than the flash mode that are used to
> make the decision on whether to power on the sensor or not.
> 
> The factors based on which to power the subdevs probably will be
> discussed in the future, and which entity is responsible for power
> management. The power management code originally was part of the Media
> controller framework but it was removed since it was not seen to be
> generic enough.
> 
> Many subdev drivers (including the adp1653) basically get powered as
> long as the subdev device node is open. Sensor can be powered based on
> other factors as well, such as the streaming state and what are the
> connections to the video nodes.
That's the start point I said. When the user use only the flash, it should be
accompanied(of course, I have same circumstance) by opening the videonode
and doing the media control operation, but we have no option to do because
it's depending on the hardware connection architecture.

So, I suggesst that, if we can not give to users(of course, this user
want to use only flash function, not the camera) proper method usage
(openning the videonode for using flash), let's express that the camera
flash is used in the DEDICATED MODE now, as the enumeration name DEDICATED.

But, I think it might be not a big issue. So, any others don't comment at this,
it's ok for me to pass this naming issue.

I can see this API is very cool for camera man just like me.

Cheers!

plus: actually I have the one of N-series, N810. So, the omap3isp is available to
activate this device, not even it's cpu is omap3? Just question.

Regards,
Heungjun Kim

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux