public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <maurochehab@gmail.com>
To: Andy Walls <awalls@radix.net>
Cc: "Aleksandr V. Piskunov" <aleksandr.v.piskunov@gmail.com>,
	ivtv-devel@ivtvdriver.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] AVerTV MCE 116 Plus radio
Date: Tue, 02 Feb 2010 13:29:58 -0200	[thread overview]
Message-ID: <4B6844F6.2090404@gmail.com> (raw)
In-Reply-To: <1258774767.9080.1.camel@palomino.walls.org>

Hi Andy,

This patch has never been applied or nacked. From your last comment, it
seems that you're waiting for Aleksandr Signed-of-by:.

If this is still the case, I suggest you to wait for a couple days. If he doesn't
send it, it is safe to add it without his SOB, since it is really a trivial change.

Cheers,
Mauro.

Andy Walls wrote:
> On Sun, 2009-10-11 at 04:01 +0300, Aleksandr V. Piskunov wrote:
>> On Tue, Oct 06, 2009 at 11:11:59AM +0300, Aleksandr V. Piskunov wrote:
>>> On Tue, Oct 06, 2009 at 11:04:06AM +0300, Aleksandr V. Piskunov wrote:
>>>> Added FM radio support to Avermedia AVerTV MCE 116 Plus card
>>>>
>>> What leaves me puzzled, radio only works ok with ivtv newi2c=1
>>>
>>> With default newi2c audio is tinny, metallic, with some strange static.
>>> Similar problem with pvr-150 was reported years ago, guess issue is still
>>> unresolved, perhaps something with cx25840..
>> This particular "tinny" audio problem is definitely I2C speed related, to be
>> more precise, audio only goes bad if i2c-algo-bit is being run with udelay
>> less than 15, i.e. i2c bus frequency is higher than 30 KHz.
>>
>> So with default udelay=10 or udelay=5 (optimal for IR reciever on that board)
>> radio goes bad. Running with newi2c=1 is ok, but again it isn't optimal for IR
>> reciever on AVerTV M116.
>>
>> I2C reads/writes to cx25840 themself are ok, verified using register readback
>> after each write/write4. Problem seems to be that with cx25840 register writes
>> coming too fast on higher i2c bus speed, switching register 0x808 _from_ 
>> TV standard autodetection mode (0xff) _to_ FM radio mode (0xf9) leaves chip 
>> audio detection routine in inconsistent state.
>>
>> The only solution I found is to do standard routine (assert_reset + write +
>> deassert_reset) followed by 50ms delay and another reset.
>>
>> Following patch works_for_me, can be improved to only delay/doublereset when
>> really needed, etc. Andy, could you comment/review?
> 
> Aleksandr,
> 
> Could you provide your Signed-off-by for this patch?  I'm going to
> commit it as is.
> 
> Thanks,
> Andy
> 
>> diff --git a/linux/drivers/media/video/cx25840/cx25840-core.c b/linux/drivers/media/video/cx25840/cx25840-core.c
>> --- a/linux/drivers/media/video/cx25840/cx25840-core.c
>> +++ b/linux/drivers/media/video/cx25840/cx25840-core.c
>> @@ -626,7 +642,13 @@
>>  	if (state->radio) {
>>  		cx25840_write(client, 0x808, 0xf9);
>>  		cx25840_write(client, 0x80b, 0x00);
>> -	}
>> +		/* Double reset cx2384x after setting FM radio mode, helps to
>> +		   avoid "tinny" audio when ivtv I2C bus is being run on
>> +		   frequency higher than 30 KHz */
>> +		cx25840_and_or(client, 0x810, ~0x01, 0);
>> +		msleep(50);
>> +		cx25840_and_or(client, 0x810, ~0x01, 1);
>> +	}	
>>  	else if (std & V4L2_STD_525_60) {
>>  		/* Certain Hauppauge PVR150 models have a hardware bug
>>  		   that causes audio to drop out. For these models the
>>
>> --
>> 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
>>
> 
> --
> 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


-- 

Cheers,
Mauro

  reply	other threads:[~2010-02-02 15:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06  8:04 [PATCH] AVerTV MCE 116 Plus radio Aleksandr V. Piskunov
2009-10-06  8:11 ` Aleksandr V. Piskunov
2009-10-11  1:01   ` Aleksandr V. Piskunov
2009-10-11 12:05     ` Andy Walls
2009-11-21  3:39     ` Andy Walls
2010-02-02 15:29       ` Mauro Carvalho Chehab [this message]
2010-02-04  0:33         ` Andy Walls
2010-02-09 14:15           ` Aleksandr V. Piskunov

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=4B6844F6.2090404@gmail.com \
    --to=maurochehab@gmail.com \
    --cc=aleksandr.v.piskunov@gmail.com \
    --cc=awalls@radix.net \
    --cc=ivtv-devel@ivtvdriver.org \
    --cc=linux-media@vger.kernel.org \
    /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