From: Antti Palosaari <crope@iki.fi>
To: Malcolm Priestley <tvboxspy@gmail.com>
Cc: Josu Lazkano <josu.lazkano@gmail.com>,
Jason Hecker <jwhecker@gmail.com>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH] af9013 Extended monitoring in set_frontend.
Date: Sat, 08 Oct 2011 17:06:32 +0300 [thread overview]
Message-ID: <4E9058E8.1070902@iki.fi> (raw)
In-Reply-To: <4e904f71.ce66e30a.69f3.ffff9870@mx.google.com>
I have been following that discussion and hoping you would finally find
out the reason.
But I want to point out few things;
* .set_frontend() is called only when channel changed
* .set_params() is called only when channel changed
* there is no I2C traffic for tuner after channel changed
* there is I2C traffic to tuner only when channel is changed
Since generally changes to .set_frontend() will not have effect in
normal use, when both devices are already streaming. Only in case of
lock is missed and re-tune initialized or channel changed.
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2011-10-08 14:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4e83369f.5d6de30a.485b.ffffdc29@mx.google.com>
2011-10-04 19:28 ` [PATCH] af9013 frontend tuner bus lock Josu Lazkano
2011-10-04 20:44 ` Jason Hecker
2011-10-04 21:54 ` Malcolm Priestley
2011-10-04 22:10 ` Jason Hecker
2011-10-05 11:40 ` Josu Lazkano
2011-10-05 22:19 ` Jason Hecker
2011-10-05 23:12 ` Josu Lazkano
2011-10-06 2:39 ` Jason Hecker
2011-10-06 20:07 ` dave cunningham
2011-10-06 21:48 ` Josu Lazkano
2011-10-06 22:34 ` Jason Hecker
2011-10-06 21:13 ` Malcolm Priestley
2011-10-07 21:11 ` [PATCH] af9013 Extended monitoring in set_frontend Malcolm Priestley
2011-10-07 22:46 ` Jason Hecker
2011-10-08 13:10 ` Malcolm Priestley
2011-10-08 13:13 ` Josu Lazkano
2011-10-08 13:26 ` Malcolm Priestley
2011-10-08 13:42 ` Josu Lazkano
2011-10-08 14:06 ` Antti Palosaari [this message]
2011-10-08 20:05 ` Jason Hecker
2011-10-10 19:31 ` Antti Palosaari
2011-10-10 20:27 ` Malcolm Priestley
2011-10-10 21:06 ` Jason Hecker
2011-10-16 20:26 ` Malcolm Priestley
2011-10-16 21:18 ` Jason Hecker
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=4E9058E8.1070902@iki.fi \
--to=crope@iki.fi \
--cc=josu.lazkano@gmail.com \
--cc=jwhecker@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=tvboxspy@gmail.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 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.