From: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Ramakrishnan Muthukrishnan <ramakrmu@cisco.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org
Cc: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Subject: [PATCH 0/4] Add support for V4L2_PIX_FMT_Y16_BE
Date: Mon, 4 May 2015 10:07:28 +0200 [thread overview]
Message-ID: <1430726852-11715-1-git-send-email-ricardo.ribalda@gmail.com> (raw)
New pixel format type Y16_BE (16 bits greyscale big-endian).
Once I get the fist feedback on this patch I will send the patches for
v4lconvert and qv4l2.
Thanks
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
drivers/media/platform/vivid/vivid-tpg.c | 20 ++++++++++++++++----
drivers/media/platform/vivid/vivid-vid-common.c | 16 ++++++++++++++++
drivers/media/v4l2-core/v4l2-ioctl.c | 1 +
include/uapi/linux/videodev2.h | 1 +
4 files changed, 34 insertions(+), 4 deletions(-)
--
2.1.4
next reply other threads:[~2015-05-04 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 8:07 Ricardo Ribalda Delgado [this message]
2015-05-04 8:07 ` [PATCH 1/4] media/vivid: Add support for Y16 format Ricardo Ribalda Delgado
2015-05-04 8:07 ` [PATCH 2/4] media/v4l2-core: Add support for V4L2_PIX_FMT_Y16_BE Ricardo Ribalda Delgado
2015-05-04 8:07 ` [PATCH 3/4] media/vivid: Add support for Y16_BE format Ricardo Ribalda Delgado
2015-05-04 8:07 ` [PATCH 4/4] media/vivid: Code cleanout Ricardo Ribalda Delgado
2015-05-18 19:26 ` [PATCH 0/4] Add support for V4L2_PIX_FMT_Y16_BE Mauro Carvalho Chehab
2015-05-18 19:31 ` Ricardo Ribalda Delgado
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=1430726852-11715-1-git-send-email-ricardo.ribalda@gmail.com \
--to=ricardo.ribalda@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=ramakrmu@cisco.com \
--cc=sakari.ailus@linux.intel.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
all inboxes | Powered by JetHome®