Message ID | 20200202155019.1029993-1-nfraprado@protonmail.com (mailing list archive) |
---|---|
Headers |
Received: from vger.kernel.org ([209.132.180.67]) by www.linuxtv.org with esmtp (Exim 4.92) (envelope-from <linux-media-owner@vger.kernel.org>) id 1iyHV1-00H8vL-NF; Sun, 02 Feb 2020 15:49:27 +0000 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726930AbgBBPui (ORCPT <rfc822;mkrufky@linuxtv.org> + 1 other); Sun, 2 Feb 2020 10:50:38 -0500 Received: from mail2.protonmail.ch ([185.70.40.22]:59070 "EHLO mail2.protonmail.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726881AbgBBPui (ORCPT <rfc822;linux-media@vger.kernel.org>); Sun, 2 Feb 2020 10:50:38 -0500 Date: Sun, 02 Feb 2020 15:50:28 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=default; t=1580658635; bh=Sf33ELn3vL0wbKIMUe34Sc9qlpaLyZtY2LGk/koDQ2I=; h=Date:To:From:Cc:Reply-To:Subject:Feedback-ID:From; b=Srnz0n2ppQt2y8jNw/RqeDcr6vAtvK3ikRfLngKz51/nwszHCbi55Hn8gUbG6+MnR NMpec3uAssELazJSR2RxFBqoIj0tDvkxvypS2TCXchHrMUWy9R3issj8IzRK+ROhXm 6p+gAPUVcuTm0S41duejvhY73cbXTmgn9cGsn4/8= To: linux-media@vger.kernel.org From: =?utf-8?b?TsOtY29sYXMgRi4gUi4gQS4gUHJhZG8=?= <nfraprado@protonmail.com> Cc: Helen Koike <helen.koike@collabora.com>, Shuah Khan <skhan@linuxfoundation.org>, Mauro Carvalho Chehab <mchehab@kernel.org>, Hans Verkuil <hverkuil@xs4all.nl>, linux-kernel@vger.kernel.org, lkcamp@lists.libreplanetbr.org Reply-To: =?utf-8?b?TsOtY29sYXMgRi4gUi4gQS4gUHJhZG8=?= <nfraprado@protonmail.com> Subject: [PATCH 0/3] media: vimc: Add support for GBR and BGR formats on source pad of debayer Message-ID: <20200202155019.1029993-1-nfraprado@protonmail.com> Feedback-ID: cwTKJQq-dqva77NrgNeIaWzOvcDQqfI9VSy7DoyJdvgY6-nEE7fD-E-3GiKFHexW4OBWbzutmMZN6q4SflMDRw==:Ext:ProtonMail MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,BAYES_40, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.protonmail.ch Sender: linux-media-owner@vger.kernel.org Precedence: bulk List-ID: <linux-media.vger.kernel.org> X-Mailing-List: linux-media@vger.kernel.org |
Series |
media: vimc: Add support for GBR and BGR formats on source pad of debayer
|
|
Message
Nícolas F. R. A. Prado
Feb. 2, 2020, 3:50 p.m. UTC
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. 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(-)
Comments
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 > >
Hi, Ezequiel. On Sun, Feb 09, 2020 at 02:09:17PM -0300, Ezequiel Garcia wrote: > > 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? Sure. At the moment, the only supported media bus format on the source pad of the debayer subdevice is the RGB888_1X24. The mbus format of the source pad of the debayer ultimately determines the pixelformat that is streamed on /dev/video3, since: * The mbus formats of the links on the topology have to match for the streaming to be possible, and [1] shows that the source pad of the debayer links to the sink of the scaler. * The scaler uses the same mbus format on sink and source. * The source pad of the scaler is linked to the /dev/video3 Capture. That said, there isn't a GBR pixelformat, so it uses the RGB pixelformat. So what this patch series enables: * Setting debayer and scaler subdevices to use GBR and BGR mbus formats. * Stream video using the BGR pixelformat from /dev/video3. By enabling these, it makes it possible to use vimc to emulate hardware that uses GBR or BGR mbus formats internally or that streams using the BGR pixelformat. Regards, Nícolas [1] https://linuxtv.org/downloads/v4l-dvb-apis-new/v4l-drivers/vimc.html#topology > > Thanks, > Ezequiel