public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Ezequiel Garcia <ezequiel@collabora.com>
Subject: [PATCH 00/10] Improvements and fixups for vim2m driver
Date: Fri,  1 Mar 2019 10:24:16 -0300	[thread overview]
Message-ID: <cover.1551446121.git.mchehab+samsung@kernel.org> (raw)

The vim2m was laking care for a long time. It had several issues. Several
were already fixed and are merged for Kernel 5.1, but there are still
some pending things.

This patch series complement the work, making it do the right thing with
regards to different resolutions at capture and output buffers.

Although it contains some improvements (like the addition of Bayer),
I'm tempted to do a late merge for it, in order for the entire set of changes
to go to Kernel 5.1, specially since:

a) It contains a fix at the buffer filling routine. At least this one should
go to 5.1 anyway;

b) while the other patches could eventually go to 5.2, they also do 
significant changes at the buffer handling logic;

c) It disables YUYV as output format (due to the horizontal scaler). It
would be good that such change would go together with the changes for
5.1 with actually implements YUYV support;

d) This is a test driver anyway and shouldn't affect systems in production.

e) As we're using it also to properly implement/fix Bayer support for M2M
transform drivers at Gstreamer, it would be better to have everything
altogether.

So, if nobody complains, I'll likely merge this series later today or along the
weekend for Kernel 5.1.


Mauro Carvalho Chehab (10):
  media: vim2m: add bayer capture formats
  media: vim2m: improve debug messages
  media: vim2m: ensure that width is multiple of two
  media: vim2m: add support for VIDIOC_ENUM_FRAMESIZES
  media: vim2m: use different framesizes for bayer formats
  media: vim2m: better handle cap/out buffers with different sizes
  media: vim2m: add vertical linear scaler
  media: vim2m: don't accept YUYV anymore as output format
  media: vim2m: add an horizontal scaler
  media: vim2m: speedup passthrough copy

 drivers/media/platform/vim2m.c | 415 +++++++++++++++++++++++----------
 1 file changed, 287 insertions(+), 128 deletions(-)

-- 
2.20.1



             reply	other threads:[~2019-03-01 13:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-01 13:24 Mauro Carvalho Chehab [this message]
2019-03-01 13:24 ` [PATCH 01/10] media: vim2m: add bayer capture formats Mauro Carvalho Chehab
2019-03-01 13:24 ` [PATCH 02/10] media: vim2m: improve debug messages Mauro Carvalho Chehab
2019-03-01 13:24 ` [PATCH 03/10] media: vim2m: ensure that width is multiple of two Mauro Carvalho Chehab
2019-03-01 13:24 ` [PATCH 04/10] media: vim2m: add support for VIDIOC_ENUM_FRAMESIZES Mauro Carvalho Chehab
2019-03-01 13:24 ` [PATCH 05/10] media: vim2m: use different framesizes for bayer formats Mauro Carvalho Chehab
2019-03-01 13:24 ` [PATCH 06/10] media: vim2m: better handle cap/out buffers with different sizes Mauro Carvalho Chehab
2019-03-01 13:24 ` [PATCH 07/10] media: vim2m: add vertical linear scaler Mauro Carvalho Chehab
2019-03-01 13:24 ` [PATCH 08/10] media: vim2m: don't accept YUYV anymore as output format Mauro Carvalho Chehab
2019-03-01 13:24 ` [PATCH 09/10] media: vim2m: add an horizontal scaler Mauro Carvalho Chehab
2019-03-01 13:24 ` [PATCH 10/10] media: vim2m: speedup passthrough copy Mauro Carvalho Chehab
2019-03-01 13:35 ` [PATCH 00/10] Improvements and fixups for vim2m driver Mauro Carvalho Chehab

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=cover.1551446121.git.mchehab+samsung@kernel.org \
    --to=mchehab+samsung@kernel.org \
    --cc=ezequiel@collabora.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.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