linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Marc Gonzalez <marc.w.gonzalez@free.fr>,
	Olli Salonen <olli.salonen@iki.fi>
Cc: linux-media <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: si2168 gapped clock
Date: Tue, 25 Jun 2019 02:09:28 +0300	[thread overview]
Message-ID: <8b54e64c-8a56-c917-a712-1e708f48f4b6@iki.fi> (raw)
In-Reply-To: <cdffeaf7-86cf-32d5-88c1-a6d7b07127b3@free.fr>

Hello,

On 6/18/19 7:47 PM, Marc Gonzalez wrote:
> Hello,
> 
> In the qcom SoC, the TS interface has two modes of operation.
> 
> - with 3 signals (clk, valid, data)
> - with 4 signals (clk, valid, data, sync)
> 
> In the si2168 short datasheet, I can see a diagram with these
> 4 signals.
> 
> My question is: how do we configure the si2168 demod to be
> in the first mode or the second mode?
> 
> Is it the ts_clock_gapped parameter?
> 
> ts_clock_gapped=0 means no sync
> ts_clock_gapped=1 means with sync ???
> 
> Regards.
> 

In general for mpeg ts you will need:
data + clock + valid : when clock is running continuously
or
data + clock : when clock is running only when there is data


Valid is used to tell there is new data when clock is running 
continuously - when valid signal is not set there is no data even clock 
is running.

When only data and clock lines are used, clock is ran only when there is 
data.

Sync signal is set for beginning of every TS packet (and it is not 
hardly needed if you parse ts data by software for example).

Thus ts_clock_gapped means demod will flip clock only when there is data 
to feed ==> no need for valid signal.

Configuring demod to first *or* second mode should be just 
ts_clock_gapped=false.

regards
Antti

-- 
http://palosaari.fi/

      reply	other threads:[~2019-06-24 23:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18 16:47 si2168 gapped clock Marc Gonzalez
2019-06-24 23:09 ` Antti Palosaari [this message]

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=8b54e64c-8a56-c917-a712-1e708f48f4b6@iki.fi \
    --to=crope@iki.fi \
    --cc=linux-media@vger.kernel.org \
    --cc=marc.w.gonzalez@free.fr \
    --cc=mchehab@kernel.org \
    --cc=olli.salonen@iki.fi \
    /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).