On 11/24/2011 09:58 PM, Mauro Carvalho Chehab wrote:
Em 13-11-2011 17:20, Antti Palosaari escreveu:
Mauro,
and these too for 3.3. Sorry about mistakes.
In fact, those 3 patches seemed to be good for 3.2:
576b849 [media] mxl5007t: fix reg read
d7d89dc [media] tda18218: fix 6 MHz default IF frequency
ff83bd8 [media] af9015: limit I2C access to keep FW happy
So, I've backported d7d89dc to 3.2, and applied there. the others,
I've added for 3.3.
You could put mxl5007t and tda18218. But as I changed tda18218 to
support .get_if_frequency() just before that fix and it touches same
code lines, it will not apply unless you do some hand editing or apply
tda18218 get_if_frequency() patch too.
DO *NOT* push af9015 I2C patch to the 3.2. I see there could be
potential problems if there is heavy demodulator I2C traffic since it
forces to wait some I2C related tasks. I suspect that could lead bad
situation when there is more traffic we can handle due to I2C access
waiting coming from patch.
I have optimized af9013 I2C load, reduced it rather much switching
multibyte I2C where possible and running statistic polls using timers in
backround. Now it returns all statistics from cache and not make any
statistics queries directly when userspace app is asking.
After my af9013 optimizations are ready those could be put to master,
which will happen likely 3.3 schedule. It is absolutely too risky put
that single patch to 3.2.
regards
Antti
--
http://palosaari.fi/
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
