From: Helen Koike <helen.koike@collabora.com>
To: linux-media@vger.kernel.org
Cc: lucmaga@gmail.com, linux-kernel@vger.kernel.org,
lkcamp@lists.libreplanetbr.org, andrealmeid@collabora.com,
Hans Verkuil <hverkuil@xs4all.nl>,
kernel@collabora.com
Subject: [PATCH 0/8] media: vimc: remove media bus code limitation
Date: Wed, 6 Mar 2019 19:42:36 -0300 [thread overview]
Message-ID: <20190306224244.21070-1-helen.koike@collabora.com> (raw)
Hello,
This patch series has several vimc fixes (that I am sending in the same
series only for convenience, let me know if you prefer them to be
sent separately from the series).
The last commit removes the vimc_pix_map_list[] that was mapping
pixelformats with media bus formats, but it turns out they are not
1-to-1 equivalent and it is really painful to add other formats.
Also, for the userspace, media bus formats don't really matter as long
as they match between links. So this patch allows any media bus format
to be configured independently of the final expected pixelformat.
The series depends on
"[PATCH] media: Introduce helpers to fill pixel format structs "
Thanks,
Helen
Helen Koike (8):
media: vimc: deb: fix default sink bayer format
media: vimc: stream: fix thread state before sleep
media: vimc: cap: fix step width/height in enum framesize
media: v4l2-common: add bayer formats in v4l2_format_info
media: vimc: stream: cleanup frame field from struct vimc_stream
media: vimc: stream: add docs to struct vimc_stream
media: vimc: stream: init/terminate the first entity
media: vimc: propagate pixel format in the stream
drivers/media/platform/vimc/vimc-capture.c | 80 +++--
drivers/media/platform/vimc/vimc-common.c | 307 ++++++++------------
drivers/media/platform/vimc/vimc-common.h | 13 +
drivers/media/platform/vimc/vimc-debayer.c | 80 +++--
drivers/media/platform/vimc/vimc-scaler.c | 60 ++--
drivers/media/platform/vimc/vimc-sensor.c | 48 +--
drivers/media/platform/vimc/vimc-streamer.c | 39 +--
drivers/media/platform/vimc/vimc-streamer.h | 22 +-
drivers/media/v4l2-core/v4l2-common.c | 22 ++
9 files changed, 341 insertions(+), 330 deletions(-)
--
2.20.1
next reply other threads:[~2019-03-06 22:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 22:42 Helen Koike [this message]
2019-03-06 22:42 ` [PATCH 1/8] media: vimc: deb: fix default sink bayer format Helen Koike
2019-03-06 22:42 ` [PATCH 2/8] media: vimc: stream: fix thread state before sleep Helen Koike
2019-03-06 22:42 ` [PATCH 3/8] media: vimc: cap: fix step width/height in enum framesize Helen Koike
2019-03-06 22:42 ` [PATCH 4/8] media: v4l2-common: add bayer formats in v4l2_format_info Helen Koike
2019-03-06 22:42 ` [PATCH 5/8] media: vimc: stream: cleanup frame field from struct vimc_stream Helen Koike
2019-03-07 20:19 ` André Almeida
2019-03-06 22:42 ` [PATCH 6/8] media: vimc: stream: add docs to " Helen Koike
2019-03-06 22:42 ` [PATCH 7/8] media: vimc: stream: init/terminate the first entity Helen Koike
2019-03-07 20:21 ` André Almeida
2019-03-06 22:42 ` [PATCH 8/8] media: vimc: propagate pixel format in the stream Helen Koike
2019-03-07 20:23 ` André Almeida
2019-03-08 13:43 ` Hans Verkuil
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=20190306224244.21070-1-helen.koike@collabora.com \
--to=helen.koike@collabora.com \
--cc=andrealmeid@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=lucmaga@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.