From: Rohit Athavale <rohit.athavale@xilinx.com>
To: <devel@driverdev.osuosl.org>
Cc: <gregkh@linuxfoundation.org>, <linux-media@vger.kernel.org>,
<rohit.athavale@xilinx.com>
Subject: [PATCH v2 0/3] Initial driver support for Xilinx M2M Video Scaler
Date: Wed, 21 Feb 2018 14:43:13 -0800 [thread overview]
Message-ID: <1519252996-787-1-git-send-email-rohit.athavale@xilinx.com> (raw)
This patch series has three commits :
- Driver support for the Xilinx M2M Video Scaler IP
- TODO document
- DT binding doc
Changes in HW register map is expected as the IP undergoes changes.
This is a first attempt at the driver as an early prototype.
This is a M2M Video Scaler IP that uses polyphases filters to perform
video scaling. The driver will be used by an application like a
gstreamer plugin.
Change Log:
v2
- Cc'ing linux-media mailing list as suggested by Dan Carpenter.
Dan wanted to see if someone from linux-media can review the
driver interface in xm2m_vscale.c to see if it makes sense.
- Another question would be the right place to keep the driver,
in drivers/staging/media or drivers/staging/
- Dropped empty mmap_open, mmap_close ops.
- Removed incorrect DMA_SHARED_BUFFER select from Kconfig
v1 - Initial version
Rohit Athavale (3):
staging: xm2mvscale: Driver support for Xilinx M2M Video Scaler
staging: xm2mvscale: Add TODO for the driver
Documentation: devicetree: bindings: Add DT binding doc for xm2mvsc
driver
drivers/staging/Kconfig | 2 +
drivers/staging/Makefile | 1 +
.../devicetree/bindings/xm2mvscaler.txt | 25 +
drivers/staging/xm2mvscale/Kconfig | 11 +
drivers/staging/xm2mvscale/Makefile | 3 +
drivers/staging/xm2mvscale/TODO | 18 +
drivers/staging/xm2mvscale/ioctl_xm2mvsc.h | 134 +++
drivers/staging/xm2mvscale/scaler_hw_xm2m.c | 945 +++++++++++++++++++++
drivers/staging/xm2mvscale/scaler_hw_xm2m.h | 152 ++++
drivers/staging/xm2mvscale/xm2m_vscale.c | 768 +++++++++++++++++
drivers/staging/xm2mvscale/xvm2mvsc_hw_regs.h | 204 +++++
11 files changed, 2263 insertions(+)
create mode 100644 drivers/staging/xm2mvscale/Documentation/devicetree/bindings/xm2mvscaler.txt
create mode 100644 drivers/staging/xm2mvscale/Kconfig
create mode 100644 drivers/staging/xm2mvscale/Makefile
create mode 100644 drivers/staging/xm2mvscale/TODO
create mode 100644 drivers/staging/xm2mvscale/ioctl_xm2mvsc.h
create mode 100644 drivers/staging/xm2mvscale/scaler_hw_xm2m.c
create mode 100644 drivers/staging/xm2mvscale/scaler_hw_xm2m.h
create mode 100644 drivers/staging/xm2mvscale/xm2m_vscale.c
create mode 100644 drivers/staging/xm2mvscale/xvm2mvsc_hw_regs.h
--
1.9.1
next reply other threads:[~2018-02-21 23:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 22:43 Rohit Athavale [this message]
2018-02-21 22:43 ` [PATCH v2 1/3] staging: xm2mvscale: Driver support for Xilinx M2M Video Scaler Rohit Athavale
2018-02-22 13:46 ` Greg KH
2018-03-09 11:57 ` Hans Verkuil
2018-03-20 0:46 ` Rohit Athavale
2018-03-20 1:41 ` Nicolas Dufresne
2018-03-20 7:27 ` Hans Verkuil
2018-02-21 22:43 ` [PATCH v2 2/3] staging: xm2mvscale: Add TODO for the driver Rohit Athavale
2018-02-21 22:43 ` [PATCH v2 3/3] Documentation: devicetree: bindings: Add DT binding doc for xm2mvsc driver Rohit Athavale
2018-02-23 0:42 ` [PATCH v2 0/3] Initial driver support for Xilinx M2M Video Scaler Nicolas Dufresne
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=1519252996-787-1-git-send-email-rohit.athavale@xilinx.com \
--to=rohit.athavale@xilinx.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-media@vger.kernel.org \
/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).