linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alfredo Jesús Delaiti" <alfredodelaiti@netscape.net>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: linux-media@vger.kernel.org
Subject: Re: mb86a20s and cx23885
Date: Mon, 04 Mar 2013 21:00:17 -0300	[thread overview]
Message-ID: <51353591.4040709@netscape.net> (raw)
In-Reply-To: <20130304164234.18df36a7@redhat.com>

Hi all

El 04/03/13 16:42, Mauro Carvalho Chehab escribió:
> Em Sun, 3 Mar 2013 13:40:51 -0300
> Mauro Carvalho Chehab <mchehab@redhat.com> escreveu:
>
>> Em Sun, 03 Mar 2013 11:50:25 -0300
>> Alfredo Jesús Delaiti <alfredodelaiti@netscape.net> escreveu:
>>
>>
>>> The new data replacement in mb86a20s
>>>
>>> /*
>>>    * Initialization sequence: Use whatevere default values that PV SBTVD
>>>    * does on its initialisation, obtained via USB snoop
>>>    */
>>> static struct regdata mb86a20s_init[] = {
>> Please test first my mb86a20s patchset. If it doesn't work, we'll need
>> to dig into the differences.
>>
>> The better is to group these and reorder them to look like what's there
>> at the driver, and send it like a diff. That would make a way easier to
>> see what's different there.
>>
>> Anyway, it follows my comments about a few things that came into my eyes.
>>
>>>       { 0x09, 0x3a },
>> No idea what's here, but it seems a worth trial to change it.
> It controls inversion. I just pushed a patch that will let it handle
> both normal and inverted spectrum. The DVB core will automatically
> switch inversion during device tuning.

I test, but not work.

Before the latest patches, obtained as follows, for example:

dmesg
[  397.076641] mb86a20s: mb86a20s_read_status:
[  397.077129] mb86a20s: mb86a20s_read_status: val = X, status = 0xXX

and now, I don't get anything. But if I use VLC I get this:


dtvdebug: frontend status: 0x00

dtvdebug: frontend status: 0x03

dtvdebug: frontend status: 0x07

dtvdebug: frontend status: 0x01


Before only got:


dtvdebug: frontend status: 0x00

dtvdebug: frontend status: 0x01



>>>       { 0x28, 0x2a },
>>>       { 0x29, 0x00 },
>>>       { 0x2a, 0xfd },
>>>       { 0x2b, 0xc8 },
>> Hmm... the above may explain why it is not working. This is calculated
>> from the XTAL frequency, and IF (if different than 4MHz).
>>
>> Just changing it could fix the issue.
> I also added a patch that allows using a different XTAL frequency.
>
> You can use the calculus there to convert from 0x00fdc8 into the XTAL
> frequency, if you have the IF set by xc5000.
I don't have the IF. How I can know the intermediate frequency?

Xtal near of xc5000 is 32.000MHz. Perhaps 32/8=4 -->IF

There are other 2 xtal of 16.000MHz and other of 28.636MHz.
Xtal of mb86a20s is 32.571MHz.

In total there are 4 xtal.

With mb86a20s changes made, the logs (i2c traffic) obtained are 
different from those obtained with Windows

I have yet to thoroughly analyze 24 samples I took with the logic 
analyzer and try to see your logic. This is going to take some time.


Again thank you very much,

Alfredo

  reply	other threads:[~2013-03-05  0:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51054759.7050202@netscape.net>
2013-01-27 16:16 ` mb86a20s and cx23885 Mauro Carvalho Chehab
2013-01-27 21:48   ` Alfredo Jesús Delaiti
2013-01-27 21:52     ` Fwd: " Alfredo Jesús Delaiti
2013-01-28 10:23     ` Mauro Carvalho Chehab
2013-01-28 20:47       ` Alfredo Jesús Delaiti
2013-02-06 14:12         ` Alfredo Jesús Delaiti
2013-03-03 14:50           ` Alfredo Jesús Delaiti
2013-03-03 16:15             ` Mauro Carvalho Chehab
2013-03-04 23:09               ` Alfredo Jesús Delaiti
2013-03-03 16:40             ` Mauro Carvalho Chehab
2013-03-04 19:42               ` Mauro Carvalho Chehab
2013-03-05  0:00                 ` Alfredo Jesús Delaiti [this message]
2013-03-05  2:30                   ` Mauro Carvalho Chehab
2013-03-08 22:42                     ` Alfredo Jesús Delaiti
2013-04-01 22:41                       ` Alfredo Jesús Delaiti
2013-07-15 19:30                         ` Alfredo Jesús Delaiti
2013-07-15 20:30                           ` Mauro Carvalho Chehab
2013-07-17 13:54                             ` Alfredo Jesús Delaiti
2013-07-17 19:23                               ` Mauro Carvalho Chehab
2013-07-19  3:38                                 ` Alfredo Jesús Delaiti
2013-07-21 13:50                                 ` Alfredo Jesús Delaiti
2013-07-23 20:58                                   ` Alfredo Jesús Delaiti
2013-07-23 21:46                                     ` Alfredo Jesús Delaiti
2013-07-27 17:55                                 ` Alfredo Jesús Delaiti
     [not found]                                   ` <20130801090436.6dfa0f68@infradead.org>
2013-08-01 17:16                                     ` Alfredo Jesús Delaiti
2013-08-01 17:37                                       ` Mauro Carvalho Chehab
2013-08-01 18:09                                         ` Alfredo Jesús Delaiti
2013-08-01 18:48                                           ` Mauro Carvalho Chehab
2013-08-02  3:18                                             ` Alfredo Jesús Delaiti

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=51353591.4040709@netscape.net \
    --to=alfredodelaiti@netscape.net \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.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).