From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: "Nícolas F. R. A. Prado" <nfraprado@protonmail.com>
Cc: linux-media <linux-media@vger.kernel.org>,
Helen Koike <helen.koike@collabora.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
lkcamp@lists.libreplanetbr.org
Subject: Re: [PATCH 0/3] media: vimc: Add support for GBR and BGR formats on source pad of debayer
Date: Sun, 9 Feb 2020 14:09:17 -0300 [thread overview]
Message-ID: <CAAEAJfDGicyS9RGkLfPEBP9FCVHiu4tYsnq+BKPsez7pWSxXXQ@mail.gmail.com> (raw)
In-Reply-To: <20200202155019.1029993-1-nfraprado@protonmail.com>
On Sun, 2 Feb 2020 at 12:50, Nícolas F. R. A. Prado
<nfraprado@protonmail.com> wrote:
>
> The objective of this series is to add support for GBR and BGR media bus formats
> for the source pad of debayer subdevices of the vimc driver.
>
Can you elaborate why is this needed, e.g. what use-case is this enabling,
or what is this fixing?
Thanks,
Ezequiel
> Since the GBR media bus code doesn't have a corresponding pixelformat, it needed
> to use the pixelformat of another bus code.
>
> The first patch makes it possible to have multiple media bus codes mapping to
> the same pixelformat.
>
> The second patch adds the GBR media bus code, using the RGB pixelformat.
>
> The third patch adds support for GBR and BGR media bus formats on the source
> pad of the debayer subdevice.
>
> This patch series passed all tests of v4l2-compliance:
> $ compliance_git -m /dev/media0
> v4l2-compliance SHA: c4a62f26c5c3ecd856ca10cf2f0d35d100283d7f, 64 bits, 64-bit time_t
>
> Grand Total for vimc device /dev/media0: 461, Succeeded: 461, Failed: 0, Warnings: 0
>
> Nícolas F. R. A. Prado (3):
> media: vimc: Support multiple buscodes for each pixelformat
> media: vimc: Add GBR media bus code
> media: vimc: deb: Add support for GBR and BGR bus formats on source
> pad
>
> drivers/media/platform/vimc/vimc-common.c | 68 +++++++++++++---------
> drivers/media/platform/vimc/vimc-common.h | 9 ++-
> drivers/media/platform/vimc/vimc-debayer.c | 53 +++++++++++++----
> drivers/media/platform/vimc/vimc-scaler.c | 10 +++-
> drivers/media/platform/vimc/vimc-sensor.c | 6 +-
> 5 files changed, 102 insertions(+), 44 deletions(-)
>
> --
> 2.25.0
>
>
next prev parent reply other threads:[~2020-02-09 17:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 15:50 [PATCH 0/3] media: vimc: Add support for GBR and BGR formats on source pad of debayer Nícolas F. R. A. Prado
2020-02-02 15:50 ` [PATCH 1/3] media: vimc: Support multiple buscodes for each pixelformat Nícolas F. R. A. Prado
2020-02-05 14:17 ` Helen Koike
2020-02-08 20:36 ` Nícolas F. R. A. Prado
2020-02-02 15:50 ` [PATCH 2/3] media: vimc: Add GBR media bus code Nícolas F. R. A. Prado
2020-02-05 14:17 ` Helen Koike
2020-02-09 14:00 ` Nícolas F. R. A. Prado
2020-02-02 15:50 ` [PATCH 3/3] media: vimc: deb: Add support for GBR and BGR bus formats on source pad Nícolas F. R. A. Prado
2020-02-05 14:17 ` Helen Koike
2020-02-09 17:09 ` Ezequiel Garcia [this message]
2020-02-09 18:26 ` [PATCH 0/3] media: vimc: Add support for GBR and BGR formats on source pad of debayer Nícolas F. R. A. Prado
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=CAAEAJfDGicyS9RGkLfPEBP9FCVHiu4tYsnq+BKPsez7pWSxXXQ@mail.gmail.com \
--to=ezequiel@vanguardiasur.com.ar \
--cc=helen.koike@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=mchehab@kernel.org \
--cc=nfraprado@protonmail.com \
--cc=skhan@linuxfoundation.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).