<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/media/dvb/frontends, branch linux-3.1.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.1.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.1.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2011-11-11T17:43:27Z</updated>
<entry>
<title>DiBcom: protect the I2C bufer access</title>
<updated>2011-11-11T17:43:27Z</updated>
<author>
<name>Patrick Boettcher</name>
</author>
<published>2011-08-03T15:08:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4c505e95cf8dd1ce490c65fc89da183a535d9132'/>
<id>urn:sha1:4c505e95cf8dd1ce490c65fc89da183a535d9132</id>
<content type='text'>
commit 79fcce3230b140f7675f8529ee53fe2f9644f902 upstream.

This patch protects the I2C buffer access in order to manage concurrent
access. This protection is done using mutex.
Furthermore, for the dib9000, if a pid filtering command is
received during the tuning, this pid filtering command is delayed to
avoid any concurrent access issue.

Cc: Mauro Carvalho Chehab &lt;mchehab@redhat.com&gt;
Cc: Florian Mickler &lt;florian@mickler.org&gt;
Signed-off-by: Olivier Grenie &lt;olivier.grenie@dibcom.fr&gt;
Signed-off-by: Patrick Boettcher &lt;Patrick.Boettcher@dibcom.fr&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>[media] tda18271c2dd: Fix saw filter configuration for DVB-C @6MHz</title>
<updated>2011-07-28T20:09:46Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2011-07-28T18:49:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cf845297d592339bcf0839298c4319633df3173a'/>
<id>urn:sha1:cf845297d592339bcf0839298c4319633df3173a</id>
<content type='text'>
Currently, the driver assumes that all QAM carriers are spaced with
8MHz. This is wrong, and may decrease QoS on Countries like Brazil,
that have DVB-C carriers with 6MHz-spaced.

Fortunately, both ITU-T J-83 and EN 300 429 specifies a way to
associate the symbol rate with the bandwidth needed for it.

For ITU-T J-83 2007 annex A, the maximum symbol rate for 6 MHz is:
	6 MHz / 1.15 = 5217391 Bauds
For  ITU-T J-83 2007 annex C, the maximum symbol rate for 6 MHz is:
	6 MHz / 1.13 = 5309735 Bauds.

As this tuner is currently used only for DRX-K, and it is currently
hard-coded to annex A, I've opted to use the roll-off factor of 0.15,
instead of 0.13.

If we ever support annex C, the better would be to add a DVB S2API
call to allow changing between Annex A and C, and add the 0.13 roll-off
factor to it.

This code is currently being used on other frontends, so I think we
should later add a core function with this code, to warrant that
it will be properly implemented everywhere.

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@redhat.com&gt;
</content>
</entry>
<entry>
<title>[media] au8522: set signal field to 100% when signal present</title>
<updated>2011-07-27T20:56:05Z</updated>
<author>
<name>Devin Heitmueller</name>
</author>
<published>2011-07-24T20:23:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d749fb663ef3b891ca5f30650ec2089ec945ce07'/>
<id>urn:sha1:d749fb663ef3b891ca5f30650ec2089ec945ce07</id>
<content type='text'>
The signal state field in G_TUNER is typically scaled from 0-100%.  Since we
don't know the signal level, we really would prefer the field to contain 100%
than 1/256, which in many utilities (such as v4l2-ctl) rounds to 0% even when
a signal is actually present.

This patch makes the behavior consistent with other drivers.

Signed-off-by: Devin Heitmueller &lt;dheitmueller@kernellabs.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@redhat.com&gt;
</content>
</entry>
<entry>
<title>[media] drxk: Fix the logic that selects between DVB-C annex A and C</title>
<updated>2011-07-27T20:56:04Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2011-07-24T12:11:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=119faf90ed79adfd4a8930f62c3b9592adf5d250'/>
<id>urn:sha1:119faf90ed79adfd4a8930f62c3b9592adf5d250</id>
<content type='text'>
Fix the DRX-K logic that selects between DVB-C annex A and C

Fix a typo where DVB-C annex type is set via setEnvParameters, but
the driver, uses, instead, setParamParameters[2].

While here, cleans up the code, fixing a bad identation at the fallback
code for other types of firmware, and put the multiple-line comments
into the Linux CodingStyle.

Acked-by: Oliver Endriss &lt;o.endriss@gmx.de&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@redhat.com&gt;
</content>
</entry>
<entry>
<title>[media] drxk: Fix read debug message</title>
<updated>2011-07-27T20:56:03Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2011-07-22T01:30:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f07a0bc111829707f1277c19467a7129ddb5aeb1'/>
<id>urn:sha1:f07a0bc111829707f1277c19467a7129ddb5aeb1</id>
<content type='text'>
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@redhat.com&gt;
</content>
</entry>
<entry>
<title>[media] drxk: Fix error return code during drxk init</title>
<updated>2011-07-27T20:56:03Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2011-07-21T22:35:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e716adacef360fde5a5327ee95aa33dfca276c61'/>
<id>urn:sha1:e716adacef360fde5a5327ee95aa33dfca276c61</id>
<content type='text'>
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@redhat.com&gt;
</content>
</entry>
<entry>
<title>[media] drxk: Remove goto/break after return</title>
<updated>2011-07-27T20:56:03Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2011-07-15T12:35:58Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ab12f41f62ee8824bb2eec12c8dcbfb31dd4572a'/>
<id>urn:sha1:ab12f41f62ee8824bb2eec12c8dcbfb31dd4572a</id>
<content type='text'>
After return, we don't need any other statement to change the
function flux ;)

Reported-by: Oliver Endriss &lt;o.endriss@gmx.de&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@redhat.com&gt;
</content>
</entry>
<entry>
<title>[media] drxk: Fix a bug at some switches that broke DVB-T</title>
<updated>2011-07-27T20:56:03Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2011-07-15T04:14:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=320ed23ebf135a3403a7068ede7ca7915675bd47'/>
<id>urn:sha1:320ed23ebf135a3403a7068ede7ca7915675bd47</id>
<content type='text'>
The error propagation changeset c23bf4402 broke the DVB-T
code.

The legacy way for propagate errors was:

do {
	status = foo_func()
	if (status &lt; 0)
		break;
} while (0);
return status;

However, on a few places, it was doing:
do {
	switch(foo) {
	case bar:
		status = foo_func()
		if (status &lt; 0)
			break;
		break;
	}
	switch(foo2) {
	case bar:
		status = foo_func()
		if (status &lt; 0)
			break;
		break;
	}
	...
} while (0);
return (status)

The inner error break were not working, as it were breaking only
the switch, instead of the do. The solution used were to do a
s/break/goto error/ at the inner breaks, but preserving the last
break. Onfortunately, on a few switches, the replacement were
applied also to the final break for the case statements.

Fix the broken logic, by reverting them to break, where pertinent,
in order to fix DVB-T support.

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@redhat.com&gt;
</content>
</entry>
<entry>
<title>[media] Remove the double symbol increment hack from drxk_hard</title>
<updated>2011-07-27T20:56:03Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2011-07-15T01:23:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c4c3a3d32a2eac18dba04683bb5b7357402405c7'/>
<id>urn:sha1:c4c3a3d32a2eac18dba04683bb5b7357402405c7</id>
<content type='text'>
Both ngene and ddbrige calls dvb_attach once for drxk_attach.
The logic used there, and by tda18271c2dd driver is different
from similar logic on other frontends.

The right fix is to change them to use the same logic, but,
while we don't do that, we need to patch em28xx-dvb in order
to do cope with ngene/ddbridge magic.

While here, document why drxk_t_release should do nothing.

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@redhat.com&gt;
</content>
</entry>
<entry>
<title>[media] media, Micronas dvb-t: Fix mem leaks, don't needlessly zero mem, fix spelling</title>
<updated>2011-07-27T20:55:56Z</updated>
<author>
<name>Jesper Juhl</name>
</author>
<published>2011-07-13T20:58:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8afe9119e25809b044d9b5afbe2fb2853a5bd10c'/>
<id>urn:sha1:8afe9119e25809b044d9b5afbe2fb2853a5bd10c</id>
<content type='text'>
In drivers/media/dvb/frontends/drxd_hard.c::load_firmware() I see 3
small issues:

 1) When the 'fw' variable goes out of scope we'll leak the memory
 allocated to it by request_firmware() by neglecting to call
 release_firmware().

 2) After a successful request_firmware() we allocate fw-&gt;size bytes
 of memory using kzalloc() only to immediately overwrite all that
 memory with memcpy(), so asking for zeroed memory seems like wasted
 effort - just use kmalloc().

 3) In one of the error messages "no memory" lacks a space and is
 written as "nomemory".

This patch fixes all 3 issues.

Signed-off-by: Jesper Juhl &lt;jj@chaosbits.net&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@redhat.com&gt;
</content>
</entry>
</feed>
