From: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>
To: linux-media@vger.kernel.org, dafna.hirschfeld@collabora.com,
helen.koike@collabora.com, 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: [PATCH 1/3] media: staging: rkisp1: rsz: get the capture format info from the capture struct
Date: Sat, 28 Mar 2020 11:56:04 +0100 [thread overview]
Message-ID: <20200328105606.13660-2-dafna.hirschfeld@collabora.com> (raw)
In-Reply-To: <20200328105606.13660-1-dafna.hirschfeld@collabora.com>
Currently the format info of the capture is retrieved by calling
the function v4l2_format_info. This is not needed since it is
already save in the capture object.
Signed-off-by: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>
---
drivers/staging/media/rkisp1/rkisp1-resizer.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/media/rkisp1/rkisp1-resizer.c b/drivers/staging/media/rkisp1/rkisp1-resizer.c
index 87799fbf0363..8704267a066f 100644
--- a/drivers/staging/media/rkisp1/rkisp1-resizer.c
+++ b/drivers/staging/media/rkisp1/rkisp1-resizer.c
@@ -387,8 +387,7 @@ static void rkisp1_rsz_config(struct rkisp1_resizer *rsz,
if (rsz->fmt_type == RKISP1_FMT_YUV) {
struct rkisp1_capture *cap =
&rsz->rkisp1->capture_devs[rsz->id];
- const struct v4l2_format_info *pixfmt_info =
- v4l2_format_info(cap->pix.fmt.pixelformat);
+ const struct v4l2_format_info *pixfmt_info = cap->pix.info;
hdiv = pixfmt_info->hdiv;
vdiv = pixfmt_info->vdiv;
--
2.17.1
next prev parent reply other threads:[~2020-03-28 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 10:56 [PATCH 0/3] media: staging: rkisp1: add support for RGB formats Dafna Hirschfeld
2020-03-28 10:56 ` Dafna Hirschfeld [this message]
2020-03-30 20:00 ` [PATCH 1/3] media: staging: rkisp1: rsz: get the capture format info from the capture struct Helen Koike
2020-04-05 17:24 ` Laurent Pinchart
2020-03-28 10:56 ` [PATCH 2/3] media: staging: rkisp1: rsz: change (hv)div only if capture format is YUV Dafna Hirschfeld
2020-03-30 20:04 ` Helen Koike
2020-04-04 12:09 ` Dafna Hirschfeld
2020-04-05 17:29 ` Laurent Pinchart
2020-03-28 10:56 ` [PATCH 3/3] media: staging: rkisp1: cap: enable RGB capture format with YUV media bus Dafna Hirschfeld
2020-04-05 17:37 ` Laurent Pinchart
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=20200328105606.13660-2-dafna.hirschfeld@collabora.com \
--to=dafna.hirschfeld@collabora.com \
--cc=dafna3@gmail.com \
--cc=ezequiel@collabora.com \
--cc=helen.koike@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 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.