STV6110 FE_READ_STATUS implementation

STV6110 FE_READ_STATUS implementation

[Guy Martin]

Hi Manu,

I'm currently writing an application that needs to know the detailed
frontend status when there is no lock.
As far as I can see from the sources, the code will only set the right
status when there is a lock in stv6110x_get_status().

Does the STV6110 supports reporting of signal, carrier, viterbi and
sync ?

I'd be happy to implement that if it does but I wasn't able to find the
datasheet. Do you have that available ?

Regards,
  Guy

RE: STV6110 FE_READ_STATUS implementation

[Sébastien RAILLARD (COEXSI)]

> -----Original Message-----
> From: linux-media-owner@vger.kernel.org [mailto:linux-media-
> owner@vger.kernel.org] On Behalf Of Guy Martin
> Sent: mardi 24 mai 2011 18:18
> To: abraham.manu@gmail.com
> Cc: linux-media@vger.kernel.org
> Subject: STV6110 FE_READ_STATUS implementation
> 
> 
> Hi Manu,
> 
> I'm currently writing an application that needs to know the detailed
> frontend status when there is no lock.
> As far as I can see from the sources, the code will only set the right
> status when there is a lock in stv6110x_get_status().
> 
> Does the STV6110 supports reporting of signal, carrier, viterbi and sync
> ?
> 

I've done some tests with the CineS2, that is using the STV6110A as the
tuner and the STV0903 as the demodulator.

The values you are searching for don't come from the tuner, but the
demodulator.

In my case, the STV0903 is reporting the five following states : SCVYL.


> I'd be happy to implement that if it does but I wasn't able to find the
> datasheet. Do you have that available ?
> 
> Regards,
>   Guy
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media"
> in the body of a message to majordomo@vger.kernel.org More majordomo
> info at  http://vger.kernel.org/majordomo-info.html

Re: STV090x FE_READ_STATUS implementation

[Guy Martin]

On Tue, 24 May 2011 19:47:17 +0200
Sébastien RAILLARD (COEXSI) <sr@coexsi.fr> wrote:

> > Does the STV6110 supports reporting of signal, carrier, viterbi and
> > sync ?
> > 
> 
> I've done some tests with the CineS2, that is using the STV6110A as
> the tuner and the STV0903 as the demodulator.
> 
> The values you are searching for don't come from the tuner, but the
> demodulator.
> 
> In my case, the STV0903 is reporting the five following states :
> SCVYL.
> 

Indeed, after some more troubleshooting, I found out that the problem
is not in the STV6110 but in the STV090X code. The card I'm using is a
TT S2-1600.

The function stv090x_read_status() only reports the status when locked.

I couldn't find the datasheet either for this one. Manu is the
maintainer as well. Maybe he has more input on this.

In the meantime, I'll give a closer look at the code see if I can figure
out a way to fix that.


Thanks,
  Guy

RE: STV090x FE_READ_STATUS implementation

[Sébastien RAILLARD (COEXSI)]

> -----Original Message-----
> From: linux-media-owner@vger.kernel.org [mailto:linux-media-
> owner@vger.kernel.org] On Behalf Of Guy Martin
> Sent: mardi 24 mai 2011 20:45
> To: Sébastien RAILLARD (COEXSI)
> Cc: abraham.manu@gmail.com; linux-media@vger.kernel.org
> Subject: Re: STV090x FE_READ_STATUS implementation
> 
> On Tue, 24 May 2011 19:47:17 +0200
> Sébastien RAILLARD (COEXSI) <sr@coexsi.fr> wrote:
> 
> > > Does the STV6110 supports reporting of signal, carrier, viterbi and
> > > sync ?
> > >
> >
> > I've done some tests with the CineS2, that is using the STV6110A as
> > the tuner and the STV0903 as the demodulator.
> >
> > The values you are searching for don't come from the tuner, but the
> > demodulator.
> >
> > In my case, the STV0903 is reporting the five following states :
> > SCVYL.
> >
> 
> Indeed, after some more troubleshooting, I found out that the problem is
> not in the STV6110 but in the STV090X code. The card I'm using is a TT
> S2-1600.
> 
> The function stv090x_read_status() only reports the status when locked.
> 
> I couldn't find the datasheet either for this one. Manu is the
> maintainer as well. Maybe he has more input on this.
> 

Strange, as it must be the same demodulator and code as for the CineS2!

Not easy to get the datasheets from ST, they have never replied to my enquiries...

> In the meantime, I'll give a closer look at the code see if I can figure
> out a way to fix that.
> 
> 
> Thanks,
>   Guy
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media"
> in the body of a message to majordomo@vger.kernel.org More majordomo
> info at  http://vger.kernel.org/majordomo-info.html

Re: STV090x FE_READ_STATUS implementation

[Guy Martin]

On Tue, 24 May 2011 21:05:33 +0200
Sébastien RAILLARD (COEXSI) <sr@coexsi.fr> wrote:

> 
> 
> > > In my case, the STV0903 is reporting the five following states :
> > > SCVYL.
> > >
> > 
> > Indeed, after some more troubleshooting, I found out that the
> > problem is not in the STV6110 but in the STV090X code. The card I'm
> > using is a TT S2-1600.
> > 
> > The function stv090x_read_status() only reports the status when
> > locked.
> > 
> > I couldn't find the datasheet either for this one. Manu is the
> > maintainer as well. Maybe he has more input on this.
> > 
> 
> Strange, as it must be the same demodulator and code as for the
> CineS2!

I think there is some missunderstanding about the issue I'm facing.
When I have a lock, it does report all the SCVYL bits.
The problem occurs when there is no lock. For instance if you try to
tune to a transponder with an invalid symbol rate, you should get
SIGNAL and CARRIER but no SYNC.

Provided the demod would report that correctly, that'd allow me to try
other possible symbol rate and only do so when the demod detects a
carrier wave.

Since I'm probing a lot of frequencies, trying ~10 possible
symbol rates when there isn't a signal slows down the process a lot.


> 
> Not easy to get the datasheets from ST, they have never replied to my
> enquiries...