From: Antti Palosaari <crope@iki.fi>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Steven Toth <stoth@kernellabs.com>,
tonyc@wincomm.com.tw, Linux-Media <linux-media@vger.kernel.org>
Subject: Re: Adding support for three new Hauppauge HVR-1275 variants - testers reqd.
Date: Mon, 20 Jul 2015 19:54:56 +0300 [thread overview]
Message-ID: <55AD27E0.6080102@iki.fi> (raw)
In-Reply-To: <CAGoCfiy5Fy26EJzRPYEk_kgH0YESTXiR-E=83Rur6PWZjyi8jQ@mail.gmail.com>
On 07/20/2015 07:45 PM, Devin Heitmueller wrote:
>> Look at the em28xx driver and you will probably see why it does not work as
>> expected. For my eyes, according to em28xx driver, it looks like that bus
>> control is aimed for bridge driver. You or em28xx is wrong.
>
> Neither are wrong. In some cases the call needs to be intercepted by
> the frontend in order to disable its TS output. In other cases it
> needs to be intercepted by the bridge to control a MUX chip which
> dictates which demodulator's TS output to route from (typically by
> toggling a GPIO).
Quickly looking the existing use cases and I found only lgdt3306a demod
which uses that callback to control its TS interface. All the rest seems
to be somehow more related to bridge driver, mostly changing bridge TS
IF or leds etc.
I don't simply see that correct solution for disabling demod TS IF -
there is sleep() for this kind of things - and as I pointed out it does
not even work for me em28xx based device because em28xx uses that
routine to switch own TS mode.
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2015-07-20 16:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 22:21 Adding support for three new Hauppauge HVR-1275 variants - testers reqd Steven Toth
2015-07-19 7:34 ` Tycho Lürsen
2015-07-20 13:13 ` Steven Toth
2015-07-20 16:06 ` Tycho Lürsen
2015-07-20 16:32 ` Steven Toth
2015-07-21 16:11 ` Tycho Lürsen
2015-07-21 16:19 ` Steven Toth
2015-07-21 18:07 ` Tycho Lürsen
2015-07-21 18:59 ` Tycho Lürsen
2015-07-21 19:02 ` Steven Toth
2015-07-21 19:21 ` Tycho Lürsen
2015-07-21 19:00 ` Steven Toth
2015-07-21 21:33 ` Tycho Lürsen
2015-07-22 7:15 ` Tycho Lürsen
2015-07-22 12:55 ` Steven Toth
2015-07-22 17:44 ` Tycho Lürsen
2015-07-24 13:38 ` Steven Toth
2015-07-20 0:52 ` Tony Chang(Wincomm)
[not found] ` <1454427BAA91444C85615ABB9382A2DE@wincomm.com.tw>
2015-07-20 12:38 ` Steven Toth
2015-07-20 14:30 ` Antti Palosaari
2015-07-20 15:00 ` Steven Toth
2015-07-20 16:35 ` Antti Palosaari
2015-07-20 16:45 ` Devin Heitmueller
2015-07-20 16:54 ` Antti Palosaari [this message]
2015-07-20 17:14 ` Steven Toth
2015-07-20 17:28 ` Antti Palosaari
2015-07-20 19:04 ` Steven Toth
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=55AD27E0.6080102@iki.fi \
--to=crope@iki.fi \
--cc=dheitmueller@kernellabs.com \
--cc=linux-media@vger.kernel.org \
--cc=stoth@kernellabs.com \
--cc=tonyc@wincomm.com.tw \
/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