linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sowjanya Komatineni <skomatineni@nvidia.com>
To: <luca@lucaceresoli.net>, <hverkuil-cisco@xs4all.nl>,
	Frank Chen <frankc@nvidia.com>,
	Thierry Reding <treding@nvidia.com>,
	<linux-media@vger.kernel.org>
Subject: IMX274 driver
Date: Thu, 28 May 2020 19:07:09 -0700	[thread overview]
Message-ID: <4184f80b-eab3-c512-dd99-d24c7af4b45c@nvidia.com> (raw)

Hi Luca,

Quick question regarding IMX274 driver that was up streamed by you.

Upstream IMX274 driver programs Y_OUT_SIZE correctly based on IMX274 
datasheet and register mode table for Y_OUT_SIZE where it includes 6 
ignored area of effective pixels + 8 effective margin for color 
processing pixels.

So, Y_OUT_SIZE register value = height + 14

But somehow with this we are not seeing full frame on CSI.

In our internal NVIDIA IMX274 driver, we are programming Y_OUT_SIZE to 
exact height  Y_OUT_SIZE = height

So for debug, followed the same and updated upstream IMX274 driver to 
program Y_OUT_SIZE = crop.height locally and I see all resolutions 
working fine with this.

Checking with Sony on whats causing sensor not to send full frame when 
Y_OUT_SIZE is set to height + 14.

But thought to check with you in parallel if there are any known issues 
related to this with IMX274 driver.

Appreciate your response.

Thanks & Regards,

Sowjanya



             reply	other threads:[~2020-05-29  2:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29  2:07 Sowjanya Komatineni [this message]
2020-05-31 21:56 ` IMX274 driver Luca Ceresoli
2020-06-01  8:31   ` Hans Verkuil
2020-06-01  8:47     ` Hans Verkuil
2020-06-02  8:51       ` Luca Ceresoli
2020-06-02 14:17         ` Sowjanya Komatineni
2020-06-02 16:16           ` Sowjanya Komatineni
2020-06-02 20:08             ` Luca Ceresoli
2020-06-23 17:25               ` Sowjanya Komatineni

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=4184f80b-eab3-c512-dd99-d24c7af4b45c@nvidia.com \
    --to=skomatineni@nvidia.com \
    --cc=frankc@nvidia.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=luca@lucaceresoli.net \
    --cc=treding@nvidia.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).