diff options
author | Guennadi Liakhovetski <g.liakhovetski@gmx.de> | 2013-10-21 06:28:02 -0300 |
---|---|---|
committer | Mauro Carvalho Chehab <m.chehab@samsung.com> | 2013-10-31 04:38:40 -0200 |
commit | 40f075330adfa497cc2894f9c6a32bb99c5cd5b8 (patch) | |
tree | 61755f3cb66f0c8133711141d8db989ae89c850b /tools/perf/builtin-evlist.c | |
parent | fc5d0f8a8878319f6cb87045fd704360b2bb4e52 (diff) | |
download | linux-40f075330adfa497cc2894f9c6a32bb99c5cd5b8.tar.bz2 |
[media] V4L2: soc-camera: work around unbalanced calls to .s_power()
Some non soc-camera drivers, e.g. em28xx, use subdevice drivers, originally
written for soc-camera, which use soc_camera_power_on() and
soc_camera_power_off() helpers to implement their .s_power() methods. Those
helpers in turn can enable and disable a clock, if it is supplied to them
as a parameter. This works well when camera host drivers balance their
calls to subdevices' .s_power() methods. However, some such drivers fail to
do that, which leads to unbalanced calls to v4l2_clk_enable() /
v4l2_clk_disable(), which then in turn produce kernel warnings. Such
behaviour is wrong and should be fixed, however, sometimes it is difficult,
because some of those drivers are rather old and use lots of subdevices,
which all should be tested after such a fix. To support such drivers this
patch adds a work-around, allowing host drivers or platforms to set a flag,
in which case soc-camera helpers will only enable the clock, if it is
disabled, and disable it only once on the first call to .s_power(0).
Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
Diffstat (limited to 'tools/perf/builtin-evlist.c')
0 files changed, 0 insertions, 0 deletions