From: Dmitri Belimov <d.belimov@gmail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Stefan Ringel <stefan.ringel@arcor.de>,
linux-media@vger.kernel.org, fabbione@redhat.com
Subject: Re: [PATCH] Fix tm6010 audio
Date: Fri, 25 Nov 2011 10:13:17 +1000 [thread overview]
Message-ID: <20111125101317.1794963d@glory.local> (raw)
In-Reply-To: <4ECE6EBC.8020006@redhat.com>
Hi
> Em 07-11-2011 22:45, Dmitri Belimov escreveu:
> > Hi
> >
> > I found why audio dosn't work for me and fix it.
> >
> > 2Stefan:
> > The V4L2_STD_DK has V4L2_STD_SECAM_DK but not equal
> > switch-case statement not worked
> >
> > you can use
> > if (dev->norm & V4L2_STD_DK) {
> > }
> >
> > This patch fix this problem.
> >
> > Other, please don't remove any workarounds without important reason.
> > For your chip revision it can be work but for other audio will be
> > bad.
> >
> > I can watch TV but radio not work. After start Gnomeradio I see
> > VIDIOCGAUDIO incorrect
> > VIDIOCSAUDIO incorrect
> > VIDIOCSFREQ incorrect
> >
> > Try found what happens with radio.
>
> This patch has several issues. The usage of switch for video doesn't
> work well. A better approach follows. Not tested yet.
>
> PS.: I couldn't test it: not sure why, but the audio source is not
> working for me: arecord is not able to read from the device input.
URB_MSG_AUDIO is zero size no data for fill to audio buffer.
for watch TV I used this command
mplayer -v tv:// -tv driver=v4l2:fps=25:outfmt=i420:width=720:height=576:alsa:adevice=hw.1,0:amode=1:audiorate=48000:forceaudio:immediatemode=0:freq=77.25:normid=15 -aspect 4:3 -vo xv
AFTER this command radio can works
URB_MSG_AUDIO is not zero and audio buffer filled.
I think incorrect init a register. When I start mplayer a register set correct mode and audio
via arecord and sox can work.
I try found it.
With my best regards, Dmitry.
> -
> [media] tm6000: Fix tm6010 audio standard selection
>
> A V4L2 standards mask may contain several standards. A more restricted
> mask with just one standard is used when user needs to bind to an
> specific standard that can't be auto-detect among a more generic mask.
>
> So, Improve the autodetection logic to detect the correct audio
> standard most of the time.
>
> Based on a patch made by Dmitri Belimov <d.belimov@gmail.com>.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
>
>
> diff --git a/drivers/media/video/tm6000/tm6000-core.c
> b/drivers/media/video/tm6000/tm6000-core.c index 9783616..55d097e
> 100644 --- a/drivers/media/video/tm6000/tm6000-core.c
> +++ b/drivers/media/video/tm6000/tm6000-core.c
> @@ -696,11 +696,13 @@ int tm6000_set_audio_rinput(struct tm6000_core
> *dev) if (dev->dev_type == TM6010) {
> /* Audio crossbar setting, default SIF1 */
> u8 areg_f0;
<snip>
> + 0x30, 0xf0);
> break;
> default:
> break;
prev parent reply other threads:[~2011-11-25 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E8C5675.8070604@arcor.de>
[not found] ` <20111017155537.6c55aec8@glory.local>
[not found] ` <4E9C65CD.2070409@arcor.de>
2011-11-08 0:45 ` [PATCH] Fix tm6010 audio Dmitri Belimov
2011-11-08 9:12 ` Mauro Carvalho Chehab
2011-11-24 16:20 ` Mauro Carvalho Chehab
2011-11-25 0:13 ` Dmitri Belimov [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=20111125101317.1794963d@glory.local \
--to=d.belimov@gmail.com \
--cc=fabbione@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox