Hi Mauro,
This pull request adds the bitmask controls, flash API and the adp1653
driver.
Changes since the first pull request:
- Added a patch to document the V4L2 control endianness. It's on the top.
- Rebased the patches. I haven't tested vivi, though.
- The adp1653 uses dev_pm_ops instead of i2c ops for suspend/resume.
Changes since the last patchset since the first pull request:
- Adp1653 flash faults control is volatile. Fix this.
- Flash interface marked as experimental.
- Moved the DocBook documentation to a new location.
- The target version is 3.1, not 2.6.41.
The following changes since commit df6aabbeb2b8799d97f3886fc994c318bc6a6843:
[media] v4l2-ctrls.c: add support for V4L2_EVENT_SUB_FL_ALLOW_FEEDBACK (2011-07-01 20:54:51 -0300)
are available in the git repository at:
ssh://linuxtv.org/git/sailus/media_tree.git media-for-3.1-flash-3
Hans Verkuil (3):
v4l2-ctrls: add new bitmask control type.
vivi: add bitmask test control.
DocBook: document V4L2_CTRL_TYPE_BITMASK.
Sakari Ailus (4):
v4l: Add a class and a set of controls for flash devices.
v4l: Add flash control documentation
adp1653: Add driver for LED flash controller
v4l: Document V4L2 control endianness as machine endianness.
Documentation/DocBook/media/v4l/compat.xml | 11 +
Documentation/DocBook/media/v4l/controls.xml | 291 ++++++++++++
Documentation/DocBook/media/v4l/v4l2.xml | 6 +-
.../DocBook/media/v4l/vidioc-g-ext-ctrls.xml | 7 +
.../DocBook/media/v4l/vidioc-queryctrl.xml | 12 +-
drivers/media/video/Kconfig | 9 +
drivers/media/video/Makefile | 1 +
drivers/media/video/adp1653.c | 491 ++++++++++++++++++++
drivers/media/video/v4l2-common.c | 3 +
drivers/media/video/v4l2-ctrls.c | 62 +++-
drivers/media/video/vivi.c | 18 +-
include/linux/videodev2.h | 37 ++
include/media/adp1653.h | 126 +++++
13 files changed, 1067 insertions(+), 7 deletions(-)
create mode 100644 drivers/media/video/adp1653.c
create mode 100644 include/media/adp1653.h
--
Sakari Ailus
sakari.ailus@xxxxxx
--
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
