All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Dmitri Belimov <d.belimov@gmail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Felipe Sanches <juca@members.fsf.org>,
	Stefan Ringel <stefan.ringel@arcor.de>,
	Bee Hock Goh <beehock@gmail.com>,
	Luis Henrique Fagundes <lhfagundes@hacklab.com.br>
Subject: Re: [PATCH v2] tm6000+audio
Date: Thu, 23 Sep 2010 02:00:38 -0300	[thread overview]
Message-ID: <4C9ADEF6.4040809@redhat.com> (raw)
In-Reply-To: <20100923124524.73a28b0c@glory.local>

Em 23-09-2010 13:45, Dmitri Belimov escreveu:
> Hi
> 
>> Em 20-09-2010 17:07, Dmitri Belimov escreveu:
>>> Hi 
>>>
>>> I rework my last patch for audio and now audio works well. This
>>> patch can be submited to GIT tree Quality of audio now is good for
>>> SECAM-DK. For other standard I set some value from datasheet need
>>> some tests.
>>>
>>> 1. Fix pcm buffer overflow
>>> 2. Rework pcm buffer fill method
>>> 3. Swap bytes in audio stream
>>> 4. Change some registers value for TM6010
>>> 5. Change pcm buffer size
>>> --- a/drivers/staging/tm6000/tm6000-stds.c
>>> +++ b/drivers/staging/tm6000/tm6000-stds.c
>>> @@ -96,6 +96,7 @@ static struct tm6000_std_tv_settings tv_stds[] = {
>>>  
>>>  			{TM6010_REQ07_R04_LUMA_HAGC_CONTROL, 0xdc},
>>>  			{TM6010_REQ07_R0D_CHROMA_KILL_LEVEL, 0x07},
>>> +			{TM6010_REQ08_R05_A_STANDARD_MOD,
>>> 0x21}, /* FIXME */
>>
>> This didn't seem to work for PAL-M. Probably, the right value for it
>> is 0x22, to follow NTSC/M, since both uses the same audio standard.
>>
>> On some tests, I was able to receive some audio there, at the proper
>> rate, with a tm6010-based device. It died when I tried to change the
>> channel, so I didn't rear yet the real audio, but I suspect it will
>> work on my next tests.
>>
>> Yet, is being hard to test, as the driver has a some spinlock logic
>> broken. I'm enclosing the logs.
> 
> Yes. I have some as crash from mplayer and arecord.
> 
>> I was able to test only when using a monitor on the same machine. All
>> trials of using vnc and X11 export ended by not receiving any audio
>> and hanging the machine.
>>
>> I suspect that we need to fix the spinlock issue, in order to better
>> test it.
> 
> Who can fix it?

Well, any of us ;)

I did a BKL lock fix series of patches, and hverkuil is improving them.
They'll make easier to avoid problems inside tm6000. We just need to make
sure that we'll hold/release the proper locks at tm6000-alsa, after applying
it at the mainstream.

Cheers,
Mauro 

  reply	other threads:[~2010-09-23  5:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100622180521.614eb85d@glory.loctelecom.ru>
     [not found] ` <4C20D91F.500@redhat.com>
     [not found]   ` <4C212A90.7070707@arcor.de>
     [not found]     ` <4C213257.6060101@redhat.com>
     [not found]       ` <4C222561.4040605@arcor.de>
     [not found]         ` <4C224753.2090109@redhat.com>
2010-06-27 12:14           ` tm6000 + audio Stefan Ringel
     [not found]           ` <4C225A5C.7050103@arcor.de>
     [not found]             ` <20100716161623.2f3314df@glory.loctelecom.ru>
     [not found]               ` <4C4C4DCA.1050505@redhat.com>
     [not found]                 ` <20100728113158.0f1495c0@glory.loctelecom.ru>
     [not found]                   ` <4C4FD659.9050309@arcor.de>
     [not found]                     ` <20100729140936.5bddd275@glory.loctelecom.ru>
     [not found]                       ` <4C51ADB5.7010906@redhat.com>
     [not found]                         ` <20100731122428.4ee569b4@glory.loctelecom.ru>
     [not found]                           ` <4C53A837.3070700@redhat.com>
     [not found]                             ` <20100825043746.225a352a@glory.local>
     [not found]                               ` <4C7543DA.1070307@redhat.com>
     [not found]                                 ` <AANLkTimr3=1QHzX3BzUVyo6uqLdCKt8SS9sDtHfZtHGZ@mail.gmail.com>
     [not found]                                   ` <4C767302.7070506@redhat.com>
2010-09-20 20:07                                     ` [PATCH v2] tm6000+audio Dmitri Belimov
2010-09-21  3:05                                       ` Mauro Carvalho Chehab
2010-09-21 19:56                                         ` Dmitri Belimov
2010-09-21 18:00                                           ` Mauro Carvalho Chehab
2010-09-21 20:37                                       ` Mauro Carvalho Chehab
2010-09-23 16:45                                         ` Dmitri Belimov
2010-09-23  5:00                                           ` Mauro Carvalho Chehab [this message]
2010-09-27 17:49                                             ` Dmitri Belimov
2010-09-27 12:33                                               ` Mauro Carvalho Chehab
2010-10-05 15:48                                                 ` tm6000 and new TV card Dmitri Belimov

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=4C9ADEF6.4040809@redhat.com \
    --to=mchehab@redhat.com \
    --cc=beehock@gmail.com \
    --cc=d.belimov@gmail.com \
    --cc=juca@members.fsf.org \
    --cc=lhfagundes@hacklab.com.br \
    --cc=linux-media@vger.kernel.org \
    --cc=stefan.ringel@arcor.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.