The following changes since commit 0fae1997f09796aca8ada5edc028aef587f6716c:
[media] dib0700: avoid the risk of forgetting to add the adapter's size (2015-05-14 19:31:34 -0300)
are available in the git repository at:
git://linuxtv.org/hverkuil/media_tree.git for-4.2h
for you to fetch changes up to ac640baa8ee43f01529e8ca5b98972ed50de1f7d:
DocBook/media: add missing entry for V4L2_PIX_FMT_Y16_BE (2015-05-15 12:30:54 +0200)
----------------------------------------------------------------
Hans Verkuil (7):
DocBook/media: fix querycap error code
sta2x11: use monotonic timestamp
rcar-vin: use monotonic timestamps
DocBook/media: remove spurious space.
DocBook/media: improve timestamp documentation
DocBook/media: fix syntax error
DocBook/media: add missing entry for V4L2_PIX_FMT_Y16_BE
Prashant Laddha (1):
v4l2-dv-timings: fix overflow in gtf timings calculation
Ricardo Ribalda Delgado (4):
media/vivid: Add support for Y16 format
media/v4l2-core: Add support for V4L2_PIX_FMT_Y16_BE
media/vivid: Add support for Y16_BE format
media/vivid: Code cleanout
Documentation/DocBook/media/v4l/io.xml | 2 +-
Documentation/DocBook/media/v4l/pixfmt-y16-be.xml | 81 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Documentation/DocBook/media/v4l/pixfmt.xml | 1 +
Documentation/DocBook/media/v4l/vidioc-dqevent.xml | 5 ++++-
Documentation/DocBook/media/v4l/vidioc-qbuf.xml | 4 +++-
Documentation/DocBook/media/v4l/vidioc-querycap.xml | 2 +-
drivers/media/pci/sta2x11/sta2x11_vip.c | 3 ++-
drivers/media/platform/soc_camera/rcar_vin.c | 2 +-
drivers/media/platform/vivid/vivid-tpg.c | 20 ++++++++++++++----
drivers/media/platform/vivid/vivid-vid-common.c | 16 +++++++++++++++
drivers/media/v4l2-core/v4l2-dv-timings.c | 28 ++++++++++++++++---------
drivers/media/v4l2-core/v4l2-ioctl.c | 1 +
include/uapi/linux/videodev2.h | 1 +
13 files changed, 146 insertions(+), 20 deletions(-)
create mode 100644 Documentation/DocBook/media/v4l/pixfmt-y16-be.xml
--
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
