From: Robert Foss <robert.foss@linaro.org>
To: Bingbu Cao <bingbu.cao@linux.intel.com>
Cc: Dongchun Zhu <dongchun.zhu@mediatek.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media <linux-media@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Ben Kao <ben.kao@intel.com>
Subject: Re: [PATCH] media: ov8856: Remove 3280x2464 mode
Date: Tue, 24 Nov 2020 11:20:25 +0100 [thread overview]
Message-ID: <CAG3jFyssMMHpi4WgWmeDjuVYKz12UwJoBT0WoOsdB4PZxnuqSw@mail.gmail.com> (raw)
In-Reply-To: <cf0b935d-3ccd-8360-1b52-89fab0b181eb@linux.intel.com>
On Tue, 24 Nov 2020 at 10:42, Bingbu Cao <bingbu.cao@linux.intel.com> wrote:
>
> Hi, Robert
>
> I remember that the full size of ov8856 image sensor is 3296x2480 and we can get the 3280x2464
> frames based on current settings.
>
> Do you have any issues with this mode?
As far as I can tell using the 3280x2464 mode actually yields an
output resolution that is 3264x2448.
What does your hardware setup look like? And which revision of the
sensor are you using?
next prev parent reply other threads:[~2020-11-24 10:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 15:50 [PATCH] media: ov8856: Remove 3280x2464 mode Robert Foss
2020-11-24 7:40 ` Dongchun Zhu
2020-11-24 8:43 ` Sakari Ailus
2020-11-24 10:10 ` Dongchun Zhu
2020-11-24 10:45 ` Robert Foss
[not found] ` <CAG3jFytX_=RcKyLkNOSCEmNHnruxSP_=PNFuGRdrevJ17x4ndQ@mail.gmail.com>
[not found] ` <961bb1b9384a4261949e9afd1e37d43e@MTKMBS31N1.mediatek.inc>
2020-11-24 10:18 ` Robert Foss
2020-11-24 9:40 ` Bingbu Cao
2020-11-24 10:20 ` Robert Foss [this message]
2020-11-25 4:11 ` Bingbu Cao
2020-11-25 7:32 ` Tomasz Figa
2020-11-26 10:00 ` Robert Foss
2020-11-27 10:26 ` Tomasz Figa
2020-11-27 13:38 ` Robert Foss
2020-12-09 5:07 ` Tomasz Figa
2020-11-24 11:27 ` Tomasz Figa
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=CAG3jFyssMMHpi4WgWmeDjuVYKz12UwJoBT0WoOsdB4PZxnuqSw@mail.gmail.com \
--to=robert.foss@linaro.org \
--cc=ben.kao@intel.com \
--cc=bingbu.cao@linux.intel.com \
--cc=dongchun.zhu@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.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.