From: Antti Palosaari <crope@iki.fi>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Dmitri Belimov <d.belimov@gmail.com>,
Devin Heitmueller <dheitmueller@kernellabs.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Stefan Ringel <stefan.ringel@arcor.de>,
Bee Hock Goh <beehock@gmail.com>,
Michael Krufky <mkrufky@kernellabs.com>
Subject: Re: [RFC] Resource reservation for frontend - Was: Re: xc5000 and switch RF input
Date: Thu, 14 Oct 2010 11:33:13 +0300 [thread overview]
Message-ID: <4CB6C049.70907@iki.fi> (raw)
In-Reply-To: <4CAC6E45.5030005@redhat.com>
On 10/06/2010 03:40 PM, Mauro Carvalho Chehab wrote:
> So, we really need to implement some type of resource locking that will properly setup I2C gates,
> RF gates, etc, depending on the type of resource currently in use.
>
> Basically, the idea would be to implement something like:
>
> enum frontend_resource {
> ANALOG_TV_TUNER,
> DIGITAL_TV_TUNER,
> FM_TUNER,
> ANALOG_DEMOD,
> DIGITAL_DEMOD,
> };
I haven't examined this yet enough, but for the background information I
can say I have one device which needs this. There is tuner behind
demodulator, but instead of normal I2C-gate switch, it is rather much
likely repeater. All tuner commands are send to the demod which then
writes those to the tuner.
DD = demod I2C addr
TT = tuner I2C addr
Bn = payload data
traditional I2C send to the tuner:
TT >> B0 B1 B2 ...
demod as repeater send to the tuner:
DD >> TT B0 B1 B2 ...
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2010-10-14 8:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 7:30 [PATCH] xc5000, rework xc_write_reg Dmitri Belimov
2010-05-24 2:38 ` Devin Heitmueller
2010-05-25 1:49 ` Dmitri Belimov
2010-07-05 16:11 ` Mauro Carvalho Chehab
2010-07-05 19:07 ` Devin Heitmueller
2010-10-06 19:52 ` xc5000 and switch RF input Dmitri Belimov
2010-10-06 12:25 ` Mauro Carvalho Chehab
2010-10-06 12:40 ` [RFC] Resource reservation for frontend - Was: " Mauro Carvalho Chehab
2010-10-07 13:00 ` Dmitri Belimov
2010-10-07 0:28 ` Mauro Carvalho Chehab
2010-10-12 18:32 ` Dmitri Belimov
2010-10-14 8:33 ` Antti Palosaari [this message]
2010-10-14 8:41 ` Devin Heitmueller
2010-10-15 15:33 ` Antti Palosaari
2010-10-13 21:30 ` [PATCH] " Dmitri Belimov
2010-10-14 0:50 ` Devin Heitmueller
2010-10-14 16:12 ` Dmitri Belimov
2010-10-14 19:27 ` hermann pitton
2010-10-26 3:31 ` [PATCH] saa7134 behold A7 and H7 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=4CB6C049.70907@iki.fi \
--to=crope@iki.fi \
--cc=beehock@gmail.com \
--cc=d.belimov@gmail.com \
--cc=dheitmueller@kernellabs.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=mkrufky@kernellabs.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 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.