From: Helen Koike <helen.koike@collabora.com>
To: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>,
linux-media@vger.kernel.org, ezequiel@collabora.com,
hverkuil@xs4all.nl, kernel@collabora.com, dafna3@gmail.com,
sakari.ailus@linux.intel.com, linux-rockchip@lists.infradead.org,
mchehab@kernel.org, laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH v2 4/4] media: staging: rkisp1: cap: remove support of BGR666 format
Date: Wed, 20 May 2020 19:34:55 -0300 [thread overview]
Message-ID: <fc4dbc40-ab57-0ca4-4ac7-5ffdb7f0ad81@collabora.com> (raw)
In-Reply-To: <20200515142952.20163-5-dafna.hirschfeld@collabora.com>
On 5/15/20 11:29 AM, Dafna Hirschfeld wrote:
> The rkisp1 supports RGB encoding with 6 bits per
> color with the following format:
> - - b5 b4 b3 b2 b1 b0 - - g5 g4 g3 g2 g1 g0 - - r5 r4 r3 r2 r1 r0 - - - - - - - -
Is this the same as V4L2_PIX_FMT_XBGR32 format, but with colors range from 0 to 63 ?
I was wondering what is the usage of such a format. If it is useful, then I'm sad
to see this being removed from the driver, since this is a v4l2 api limitation, and not
a hw limitation.
Regards,
Helen
>
> This is not how V4L2_PIX_FMT_BGR666 is defined, so remove
> this format from the driver's formats list.
>
> Signed-off-by: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>
> ---
> drivers/staging/media/rkisp1/rkisp1-capture.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/staging/media/rkisp1/rkisp1-capture.c b/drivers/staging/media/rkisp1/rkisp1-capture.c
> index 61b9ebe577b2..2660e44eda88 100644
> --- a/drivers/staging/media/rkisp1/rkisp1-capture.c
> +++ b/drivers/staging/media/rkisp1/rkisp1-capture.c
> @@ -283,10 +283,6 @@ static const struct rkisp1_capture_fmt_cfg rkisp1_sp_fmts[] = {
> .fourcc = V4L2_PIX_FMT_RGB565,
> .write_format = RKISP1_MI_CTRL_SP_WRITE_PLA,
> .output_format = RKISP1_MI_CTRL_SP_OUTPUT_RGB565,
> - }, {
> - .fourcc = V4L2_PIX_FMT_BGR666,
> - .write_format = RKISP1_MI_CTRL_SP_WRITE_PLA,
> - .output_format = RKISP1_MI_CTRL_SP_OUTPUT_RGB666,
> },
> };
>
>
next prev parent reply other threads:[~2020-05-20 22:35 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 14:29 [PATCH v2 0/4] media: staging: rkisp1: various fixes to capture formats Dafna Hirschfeld
2020-05-15 14:29 ` [PATCH v2 1/4] media: staging: rkisp1: cap: change RGB24 format to XBGR32 Dafna Hirschfeld
2020-05-20 21:50 ` Helen Koike
2020-05-26 23:04 ` Tomasz Figa
2020-06-10 16:11 ` Dafna Hirschfeld
2020-06-10 16:15 ` Tomasz Figa
2020-05-15 14:29 ` [PATCH v2 2/4] media: staging: rkisp1: rsz: use hdiv, vdiv of yuv422 instead of macros Dafna Hirschfeld
2020-05-20 21:54 ` Helen Koike
2020-05-20 22:08 ` Helen Koike
2020-05-22 12:11 ` Dafna Hirschfeld
2020-05-22 13:31 ` Ezequiel Garcia
2020-05-22 14:15 ` Dafna Hirschfeld
2020-05-22 15:04 ` Ezequiel Garcia
2020-05-25 9:51 ` Dafna Hirschfeld
2020-05-26 22:26 ` Tomasz Figa
2020-05-22 13:57 ` Laurent Pinchart
2020-05-22 14:54 ` Dafna Hirschfeld
2020-05-22 14:59 ` Laurent Pinchart
2020-06-10 16:36 ` Dafna Hirschfeld
2020-05-26 22:44 ` Tomasz Figa
2020-06-10 17:01 ` Dafna Hirschfeld
2020-06-10 17:08 ` Tomasz Figa
2020-05-15 14:29 ` [PATCH v2 3/4] media: staging: rkisp1: rsz: set output format to YUV422 if cap format is YUV444 Dafna Hirschfeld
2020-05-20 22:23 ` Helen Koike
2020-05-26 23:09 ` Tomasz Figa
2020-06-12 12:45 ` Dafna Hirschfeld
2020-06-18 17:47 ` Tomasz Figa
2020-06-18 18:00 ` Dafna Hirschfeld
2020-06-18 18:12 ` Tomasz Figa
2020-06-18 18:50 ` Dafna Hirschfeld
2020-06-18 19:18 ` Tomasz Figa
2020-06-19 7:30 ` Dafna Hirschfeld
2020-06-19 12:04 ` Tomasz Figa
2020-07-18 16:05 ` Dafna Hirschfeld
2020-05-15 14:29 ` [PATCH v2 4/4] media: staging: rkisp1: cap: remove support of BGR666 format Dafna Hirschfeld
2020-05-20 22:34 ` Helen Koike [this message]
2020-05-26 22:57 ` Tomasz Figa
2020-05-27 10:14 ` Helen Koike
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=fc4dbc40-ab57-0ca4-4ac7-5ffdb7f0ad81@collabora.com \
--to=helen.koike@collabora.com \
--cc=dafna.hirschfeld@collabora.com \
--cc=dafna3@gmail.com \
--cc=ezequiel@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=kernel@collabora.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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 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).