From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: linux-renesas-soc@vger.kernel.org, linux-media@vger.kernel.org,
laurent.pinchart@ideasonboard.com
Cc: corbet@lwn.net, mchehab@kernel.org, sakari.ailus@linux.intel.com,
hans.verkuil@cisco.com,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: [PATCHv3 0/2] v4l: vsp1: Add HGT support
Date: Wed, 7 Sep 2016 14:09:36 +0200 [thread overview]
Message-ID: <20160907120938.818-1-niklas.soderlund+renesas@ragnatech.se> (raw)
Hi,
This series add support for the VSP1 2-D histogram engine HGT.
It's based on top of Laurent Pinchart tree at
git://linuxtv.org/pinchartl/media.git hgo. And depends on Laurents patch
'[PATCH] v4l: vsp1: Move subdev operations from HGO to common histogram
code'.
It is tested on Koelsch using a modified vsp-tests suite package,
modifications can be found at https://git.ragnatech.se/vsp-tests hgt.
* Changes since v2
- Add .try_ctrl() handling and return -EINVAL instead of trying to correct the
hue areas. Thanks Laurent for suggesting a solution to this.
- Fixed typo in pixel format documentation, thanks Laurent for spotting it.
* Changes since v1
- Rebased on top of Laurents patch which made all subdev operations
common for HGO and HGT. This removed a lot of code that is now shared.
- Removed the Hue area configuration for the histogram pixel format.
These values are set by userspace so it already knows them.
- Updated pixel format documentation after input from Laurent.
- Better aligned the code to the existing VSP code base.
- Simplify check that hue areas are valid for the hardware.
- Fixed spelling.
Niklas Söderlund (2):
v4l: Define a pixel format for the R-Car VSP1 2-D histogram engine
v4l: vsp1: Add HGT support
Documentation/media/uapi/v4l/meta-formats.rst | 1 +
.../media/uapi/v4l/pixfmt-meta-vsp1-hgt.rst | 120 +++++++++++
drivers/media/platform/vsp1/Makefile | 2 +-
drivers/media/platform/vsp1/vsp1.h | 3 +
drivers/media/platform/vsp1/vsp1_drv.c | 33 ++-
drivers/media/platform/vsp1/vsp1_entity.c | 33 ++-
drivers/media/platform/vsp1/vsp1_entity.h | 1 +
drivers/media/platform/vsp1/vsp1_hgt.c | 221 +++++++++++++++++++++
drivers/media/platform/vsp1/vsp1_hgt.h | 42 ++++
drivers/media/platform/vsp1/vsp1_pipe.c | 16 ++
drivers/media/platform/vsp1/vsp1_pipe.h | 2 +
drivers/media/platform/vsp1/vsp1_regs.h | 9 +
drivers/media/platform/vsp1/vsp1_video.c | 10 +-
drivers/media/v4l2-core/v4l2-ioctl.c | 1 +
include/uapi/linux/videodev2.h | 3 +-
15 files changed, 480 insertions(+), 17 deletions(-)
create mode 100644 Documentation/media/uapi/v4l/pixfmt-meta-vsp1-hgt.rst
create mode 100644 drivers/media/platform/vsp1/vsp1_hgt.c
create mode 100644 drivers/media/platform/vsp1/vsp1_hgt.h
--
2.9.3
next reply other threads:[~2016-09-07 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 12:09 Niklas Söderlund [this message]
2016-09-07 12:09 ` [PATCHv3 1/2] v4l: Define a pixel format for the R-Car VSP1 2-D histogram engine Niklas Söderlund
2016-09-07 12:09 ` [PATCHv3 2/2] v4l: vsp1: Add HGT support Niklas Söderlund
2016-09-07 12:48 ` Laurent Pinchart
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=20160907120938.818-1-niklas.soderlund+renesas@ragnatech.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=corbet@lwn.net \
--cc=hans.verkuil@cisco.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).