From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Arun Kumar K <arunkk.samsung@gmail.com>
Cc: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
Arun Kumar K <arun.kk@samsung.com>,
LMML <linux-media@vger.kernel.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
kilyeon.im@samsung.com, shaik.ameer@samsung.com,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>
Subject: Re: [RFC v2 06/10] exynos5-fimc-is: Adds isp subdev
Date: Wed, 17 Jul 2013 00:11:29 +0200 [thread overview]
Message-ID: <51E5C511.70202@gmail.com> (raw)
In-Reply-To: <CALt3h7_Bo3P9WsZORXXWtXrWLS4Uoeq10HYr0WsgO5wVzqQ95w@mail.gmail.com>
On 07/09/2013 01:42 PM, Arun Kumar K wrote:
>>> + /* Check if same as sensor width& height */
>>> >>
>>> >> + sensor_width = p->sensor->drvdata->pixel_width;
>>> >> + sensor_height = p->sensor->drvdata->pixel_height;
>>> >> + if ((sensor_width != f->fmt.pix_mp.width) ||
>>> >> + (sensor_height != f->fmt.pix_mp.height)) {
>> >
>> >
>> > What's the point of this check ?
>> >
> Check was added to ensure ISP input width and height is
> set same as the sensor output or not.
> But yes this cannot be extended to generic (non-IS controlled) sensors.
> Will drop this check and let media controller take care.
>
>> >
>>> >> + f->fmt.pix_mp.width = sensor_width;
>>> >> + f->fmt.pix_mp.height = sensor_height;
>>> >> + }
I meant that you could do the assignment unconditionally, since you
always end up with sensor_width/height assigned to pix_mp.width/height.
Indeed, this should be handled by subdev ioctls, and any discrepancies
should be detected while starting streaming and reported to user space.
--
Thanks,
Sylwester
next prev parent reply other threads:[~2013-07-16 22:11 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 13:03 [RFC v2 00/10] Exynos5 FIMC-IS driver Arun Kumar K
2013-05-31 13:03 ` [RFC v2 01/10] exynos5-fimc-is: Add Exynos5 FIMC-IS device tree bindings documentation Arun Kumar K
2013-06-20 22:45 ` Sylwester Nawrocki
2013-07-09 11:08 ` Arun Kumar K
2013-07-16 21:23 ` Sylwester Nawrocki
2013-07-17 4:42 ` Arun Kumar K
2013-05-31 13:03 ` [RFC v2 02/10] exynos5-fimc-is: Adds fimc-is driver core files Arun Kumar K
2013-06-06 5:20 ` Sachin Kamat
2013-06-07 10:26 ` Arun Kumar K
2013-06-20 22:46 ` Sylwester Nawrocki
2013-07-09 11:10 ` Arun Kumar K
2013-05-31 13:03 ` [RFC v2 03/10] exynos5-fimc-is: Adds common driver header files Arun Kumar K
2013-06-20 22:46 ` Sylwester Nawrocki
2013-06-21 7:14 ` Arun Kumar K
2013-07-09 11:20 ` Arun Kumar K
2013-05-31 13:03 ` [RFC v2 04/10] exynos5-fimc-is: Adds the register definition and context header Arun Kumar K
2013-06-06 6:24 ` Sachin Kamat
2013-06-07 10:27 ` Arun Kumar K
2013-05-31 13:03 ` [RFC v2 05/10] exynos5-fimc-is: Adds the sensor subdev Arun Kumar K
2013-06-06 6:39 ` Sachin Kamat
2013-06-07 10:30 ` Arun Kumar K
2013-06-20 23:04 ` Sylwester Nawrocki
2013-07-09 12:01 ` Arun Kumar K
2013-06-26 7:27 ` Hans Verkuil
2013-07-09 12:04 ` Arun Kumar K
2013-07-16 22:03 ` Sylwester Nawrocki
2013-07-17 4:55 ` Arun Kumar K
2013-07-17 14:14 ` Sylwester Nawrocki
2013-07-18 4:35 ` Arun Kumar K
2013-05-31 13:03 ` [RFC v2 06/10] exynos5-fimc-is: Adds isp subdev Arun Kumar K
2013-06-06 6:18 ` Sachin Kamat
2013-06-07 10:28 ` Arun Kumar K
2013-06-20 23:25 ` Sylwester Nawrocki
2013-07-09 11:42 ` Arun Kumar K
2013-07-16 22:11 ` Sylwester Nawrocki [this message]
2013-07-17 4:56 ` Arun Kumar K
2013-08-02 4:31 ` Arun Kumar K
2013-08-03 21:38 ` Sylwester Nawrocki
2013-06-26 7:15 ` Hans Verkuil
2013-07-09 11:42 ` Arun Kumar K
2013-05-31 13:03 ` [RFC v2 07/10] exynos5-fimc-is: Adds scaler subdev Arun Kumar K
2013-06-06 6:45 ` Sachin Kamat
2013-06-26 7:13 ` Hans Verkuil
2013-07-09 11:30 ` Arun Kumar K
2013-05-31 13:03 ` [RFC v2 08/10] exynos5-fimc-is: Adds the hardware pipeline control Arun Kumar K
2013-05-31 13:03 ` [RFC v2 09/10] exynos5-fimc-is: Adds the hardware interface module Arun Kumar K
2013-06-21 11:23 ` Andrzej Hajda
2013-07-09 11:26 ` Arun Kumar K
2013-05-31 13:03 ` [RFC v2 10/10] exynos5-fimc-is: Adds the Kconfig and Makefile Arun Kumar K
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=51E5C511.70202@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=arun.kk@samsung.com \
--cc=arunkk.samsung@gmail.com \
--cc=kilyeon.im@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=shaik.ameer@samsung.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).