From: Antti Palosaari <crope@iki.fi>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Dmitri Belimov <d.belimov@gmail.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: Fri, 15 Oct 2010 18:33:56 +0300 [thread overview]
Message-ID: <4CB87464.5010209@iki.fi> (raw)
In-Reply-To: <AANLkTikz+eczKDwo4-1H-QFXsg0dzRcbsdgwb=XL0cXH@mail.gmail.com>
On 10/14/2010 11:41 AM, Devin Heitmueller wrote:
> On Thu, Oct 14, 2010 at 4:33 AM, Antti Palosaari<crope@iki.fi> wrote:
>> 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 ...
>
> You can accomplish this by having the demod create an i2c adapter
> instance, which generates i2c commands to the bridge. Then when
> instantiating the tuner subdev, pass a pointer to the demod's i2c
> adapter instead of the i2c adapter provided by the bridge.
>
> No changes required to the core framework.
Thank you Devin. I didn't realized that earlier. It worked just fine.
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2010-10-15 15:34 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
2010-10-14 8:41 ` Devin Heitmueller
2010-10-15 15:33 ` Antti Palosaari [this message]
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=4CB87464.5010209@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox