From: mkrufky@linuxtv.org
To: edubezval@gmail.com
Cc: tony@atomide.com, eduardo.valentin@indt.org.br,
video4linux-list@redhat.com, sakari.ailus@nokia.com,
mchehab@infradead.org
Subject: Re: [PATCH 0/1] Add support for TEA5761 (from linux-omap)
Date: Thu, 5 Jun 2008 11:29:47 -0400 [thread overview]
Message-ID: <4848066B.4020908@linuxtv.org> (raw)
In-Reply-To: <a0580c510806050824k34e0d965yb871dfe18e9b07c1@mail.gmail.com>
Eduardo Valentin wrote:
> Hi guys,
>
> About this Tuner API, what is the best way to [s,g]et mute state?
>
> cheers,
>
You would usually have the bridge driver handle mute / unmute
operation. The tuner driver handles the operations of the tuner chip,
itself. Mute is not normally controlled within the tuner silicon.
For cases where mute IS controlled by the tuner, we tend to call sleep
to mute the tuner, and we re-tune to unmute and ensure that we're on the
correct channel.
-Mike
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-06-05 15:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 15:25 [PATCH 0/1] Add support for TEA5761 (from linux-omap) Eduardo Valentin
2008-06-03 15:25 ` [PATCH 1/1] Add support for tea5761 chip Eduardo Valentin
2008-06-03 15:44 ` [PATCH 0/1] Add support for TEA5761 (from linux-omap) Michael Krufky
2008-06-03 21:56 ` Mauro Carvalho Chehab
2008-06-04 14:25 ` Eduardo Valentin
2008-06-04 14:44 ` Mauro Carvalho Chehab
2008-06-04 15:20 ` mkrufky
2008-06-04 20:13 ` Eduardo Valentin
2008-06-04 20:22 ` Mauro Carvalho Chehab
2008-06-04 21:06 ` mkrufky
2008-06-04 21:44 ` Eduardo Valentin
2008-06-05 15:24 ` Eduardo Valentin
2008-06-05 15:29 ` mkrufky [this message]
2008-06-29 12:04 ` Mauro Carvalho Chehab
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=4848066B.4020908@linuxtv.org \
--to=mkrufky@linuxtv.org \
--cc=eduardo.valentin@indt.org.br \
--cc=edubezval@gmail.com \
--cc=mchehab@infradead.org \
--cc=sakari.ailus@nokia.com \
--cc=tony@atomide.com \
--cc=video4linux-list@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