All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: Dave Stevenson <dave.stevenson@raspberrypi.org>,
	Mats Randgaard <matrandg@cisco.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH 2/3] [media] tc358743: Increase FIFO level to 300.
Date: Tue, 19 Sep 2017 13:49:30 -0300	[thread overview]
Message-ID: <20170919134930.6fa28562@recife.lan> (raw)
In-Reply-To: <1505834685.10076.5.camel@pengutronix.de>

Em Tue, 19 Sep 2017 17:24:45 +0200
Philipp Zabel <p.zabel@pengutronix.de> escreveu:

> Hi Dave,
> 
> On Tue, 2017-09-19 at 14:08 +0100, Dave Stevenson wrote:
> > The existing fixed value of 16 worked for UYVY 720P60 over
> > 2 lanes at 594MHz, or UYVY 1080P60 over 4 lanes. (RGB888
> > 1080P60 needs 6 lanes at 594MHz).
> > It doesn't allow for lower resolutions to work as the FIFO
> > underflows.
> > 
> > Using a value of 300 works for all resolutions down to VGA60,
> > and the increase in frame delay is <4usecs for 1080P60 UYVY
> > (2.55usecs for RGB888).
> > 
> > Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.org>  
> 
> Can we increase this to 320? This would also allow
> 720p60 at 594 Mbps / 4 lanes, according to the xls.

Hmm... if this is dependent on the resolution and frame rate, wouldn't
it be better to dynamically adjust it accordingly?

Regards,
Maur

Thanks,
Mauro

  reply	other threads:[~2017-09-19 16:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19 13:08 [PATCH 0/3] [media] tc358743: Support for a wider range of inputs Dave Stevenson
2017-09-19 13:08 ` [PATCH 1/3] [media] tc358743: Correct clock mode reported in g_mbus_config Dave Stevenson
2017-09-21  9:21   ` Philipp Zabel
2017-09-19 13:08 ` [PATCH 2/3] [media] tc358743: Increase FIFO level to 300 Dave Stevenson
2017-09-19 15:24   ` Philipp Zabel
2017-09-19 16:49     ` Mauro Carvalho Chehab [this message]
2017-09-20  9:14       ` Dave Stevenson
2017-09-20 10:23         ` Philipp Zabel
2017-09-20 11:00           ` Dave Stevenson
2017-09-20 11:24             ` Hans Verkuil
2017-09-20 12:23               ` Dave Stevenson
2017-09-20 12:37                 ` Hans Verkuil
2017-09-20 12:36               ` Philipp Zabel
2017-09-20 12:50               ` Sakari Ailus
2017-09-20 13:12                 ` Hans Verkuil
2017-09-21  6:35                   ` Sakari Ailus
2017-09-21  9:04                   ` Philipp Zabel
2017-09-19 13:08 ` [PATCH 3/3] [media] tc358743: Add support for 972Mbit/s link freq Dave Stevenson

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=20170919134930.6fa28562@recife.lan \
    --to=mchehab@s-opensource.com \
    --cc=dave.stevenson@raspberrypi.org \
    --cc=hans.verkuil@cisco.com \
    --cc=linux-media@vger.kernel.org \
    --cc=matrandg@cisco.com \
    --cc=mchehab@kernel.org \
    --cc=p.zabel@pengutronix.de \
    /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.