<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers, branch v2.6.30.9</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers?h=v2.6.30.9</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers?h=v2.6.30.9'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2009-10-05T15:28:07Z</updated>
<entry>
<title>thinkpad-acpi: fix incorrect use of TPACPI_BRGHT_MODE_ECNVRAM</title>
<updated>2009-10-05T15:28:07Z</updated>
<author>
<name>Henrique de Moraes Holschuh</name>
<email>hmh@hmh.eng.br</email>
</author>
<published>2009-09-26T00:57:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=30f5582a68a013f742657c3f2b8737f0c5ad6c79'/>
<id>urn:sha1:30f5582a68a013f742657c3f2b8737f0c5ad6c79</id>
<content type='text'>
HBRV-based default selection of backlight control strategy didn't work
well, at least the X41 defines it but doesn't use it and I don't think
it will stop there.  Switch to a blacklist, and make sure only Radeon-
based models get ECNVRAM.

Symptoms of incorrect backlight mode selection are:

1. Non-working backlight control through sysfs;

2. Backlight gets reset to the lowest level at every shutdown, reboot
   and when thinkpad-acpi gets unloaded;

This fixes a regression in 2.6.30, bugzilla #13826.  This fix is
already present on 2.6.31.

This is a minimal patch for 2.6.30-stable, based on mainline
commits: 050df107c408a3df048524b3783a5fc6d4dccfdb,
	 7d95a3d564901e88ed42810f054e579874151999,
	 59fe4fe34d7afdf63208124f313be9056feaa2f4,
	 6da25bf51689a5cc60370d30275dbb9e6852e0cb

Signed-off-by: Henrique de Moraes Holschuh &lt;hmh@hmh.eng.br&gt;
Reported-by: Tobias Diedrich &lt;ranma+kernel@tdiedrich.de&gt;
Reported-by: Robert de Rooy &lt;robert.de.rooy@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>PM / yenta: Fix cardbus suspend/resume regression</title>
<updated>2009-10-05T15:28:06Z</updated>
<author>
<name>Rafael J. Wysocki</name>
<email>rjw@sisk.pl</email>
</author>
<published>2009-09-28T22:11:03Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=51acd2e6291fe7527bfd3106f5535e68993de0f9'/>
<id>urn:sha1:51acd2e6291fe7527bfd3106f5535e68993de0f9</id>
<content type='text'>
commit 0c570cdeb8fdfcb354a3e9cd81bfc6a09c19de0c upstream.

Since 2.6.29 the PCI PM core have been restoring the standard
configuration registers of PCI devices in the early phase of
resume.  In particular, PCI devices without drivers have been handled
this way since commit 355a72d75b3b4f4877db4c9070c798238028ecb5
(PCI: Rework default handling of suspend and resume).  Unfortunately,
this leads to post-resume problems with CardBus devices which cannot
be accessed in the early phase of resume, because the sockets they
are on have not been woken up yet at that point.

To solve this problem, move the yenta socket resume to the early
phase of resume and, analogously, move the suspend of it to the late
phase of suspend.  Additionally, remove some unnecessary PCI code
from the yenta socket's resume routine.

Fixes http://bugzilla.kernel.org/show_bug.cgi?id=13092, which is a
post-2.6.28 regression.

Signed-off-by: Rafael J. Wysocki &lt;rjw@sisk.pl&gt;
Reported-by: Florian &lt;fs-kernelbugzilla@spline.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>PM / PCMCIA: Drop second argument of pcmcia_socket_dev_suspend()</title>
<updated>2009-10-05T15:28:06Z</updated>
<author>
<name>Rafael J. Wysocki</name>
<email>rjw@sisk.pl</email>
</author>
<published>2009-09-28T22:10:41Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=130abc03e8b7aeaefcdda3cb9c6915e91c0a78f5'/>
<id>urn:sha1:130abc03e8b7aeaefcdda3cb9c6915e91c0a78f5</id>
<content type='text'>
commit 827b4649d4626bf97b203b4bcd69476bb9b4e760 upstream.

pcmcia_socket_dev_suspend() doesn't use its second argument, so it
may be dropped safely.

This change is necessary for the subsequent yenta suspend/resume fix.

Signed-off-by: Rafael J. Wysocki &lt;rjw@sisk.pl&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ahci: restore pci_intx() handling</title>
<updated>2009-10-05T15:27:58Z</updated>
<author>
<name>Tejun Heo</name>
<email>tj@kernel.org</email>
</author>
<published>2009-09-16T15:34:39Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2eca1dfad3e38655eb434d7706b98f7092c9d009'/>
<id>urn:sha1:2eca1dfad3e38655eb434d7706b98f7092c9d009</id>
<content type='text'>
commit 31b239ad1ba7225435e13f5afc47e48eb674c0cc upstream.

Commit a5bfc4714b3f01365aef89a92673f2ceb1ccf246 dropped explicit
pci_intx() manipulation from ahci because it seemed unnecessary and
ahci doesn't seem to be the right place to be tweaking it if it were.
This was largely okay but there are exceptions.  There was one on an
embedded platform which was fixed via firmware and now bko#14124
reports it on a HP DL320.

  http://bugzilla.kernel.org/show_bug.cgi?id=14124

I still think this isn't something libata drivers should be caring
about (the only ones which are calling pci_intx() explicitly are
libata ones and one other driver) but for now reverting the change
seems to be the right thing to do.

Signed-off-by: Tejun Heo &lt;tj@kernel.org&gt;
Reported-by: Thomas Jarosch &lt;thomas.jarosch@intra2net.com&gt;
Signed-off-by: Jeff Garzik &lt;jgarzik@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>p54usb: add Zcomax XG-705A usbid</title>
<updated>2009-10-05T15:27:50Z</updated>
<author>
<name>Christian Lamparter</name>
<email>chunkeey@googlemail.com</email>
</author>
<published>2009-09-14T21:08:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1c3a00c887a2942679b96676dc3294685e5860c9'/>
<id>urn:sha1:1c3a00c887a2942679b96676dc3294685e5860c9</id>
<content type='text'>
commit f7f71173ea69d4dabf166533beffa9294090b7ef upstream.

This patch adds a new usbid for Zcomax XG-705A to the device table.

Reported-by: Jari Jaakola &lt;jari.jaakola@gmail.com&gt;
Signed-off-by: Christian Lamparter &lt;chunkeey@googlemail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ACPI: pci_slot.ko wants a 64-bit _SUN</title>
<updated>2009-10-05T15:27:44Z</updated>
<author>
<name>Alex Chiang</name>
<email>achiang@hp.com</email>
</author>
<published>2009-08-04T20:44:17Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=562702289faac232f54b2d2d50ba31646c3d51a5'/>
<id>urn:sha1:562702289faac232f54b2d2d50ba31646c3d51a5</id>
<content type='text'>
commit 7e24bc1ce669b2876ffa475ea1147f2bb9ffdc52 upstream.

Similar to commit b6adc195 (PCI hotplug: acpiphp wants a 64-bit
_SUN), pci_slot.ko reads and creates sysfs directories based on
the _SUN method.

Certain HP platforms return 64 bits in _SUN. This change to
pci_slot.ko allows us to see the correct sysfs directories.

Reported-by: Chad Smith &lt;chad.smith@hp.com&gt;
Signed-off-by: Alex Chiang &lt;achiang@hp.com&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>PCI: Unhide the SMBus on the Compaq Evo D510 USDT</title>
<updated>2009-09-24T15:27:29Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2009-07-28T09:49:19Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8717bad06ba13356600381e5babe5f62e74c49be'/>
<id>urn:sha1:8717bad06ba13356600381e5babe5f62e74c49be</id>
<content type='text'>
commit 6b5096e4d4496e185cd1ada5d1b8e1d941c805ed upstream.

One more form factor for Compaq Evo D510, which needs the same quirk
as the other form factors. Apparently there's no hardware monitoring
chip on that one, but SPD EEPROMs, so it's still worth unhiding the
SMBus.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Tested-by: Nuzhna Pomoshch &lt;nuzhna_pomoshch@yahoo.com&gt;
Signed-off-by: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>libata: fix off-by-one error in ata_tf_read_block()</title>
<updated>2009-09-24T15:27:28Z</updated>
<author>
<name>Tejun Heo</name>
<email>htejun@gmail.com</email>
</author>
<published>2009-08-16T12:21:21Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=db4d3b9dedd857ae5f90301a654b7997132be7ae'/>
<id>urn:sha1:db4d3b9dedd857ae5f90301a654b7997132be7ae</id>
<content type='text'>
commit ac8672ea922bde59acf50eaa1eaa1640a6395fd2 upstream.

ata_tf_read_block() has off-by-one error when converting CHS address
to LBA.  The bug isn't very visible because ata_tf_read_block() is
used only when generating sense data for a failed RW command and CHS
addressing isn't used too often these days.

This problem was spotted by Atsushi Nemoto.

Signed-off-by: Tejun Heo &lt;tj@kernel.org&gt;
Reported-by: Atsushi Nemoto &lt;anemo@mba.ocn.ne.jp&gt;
Signed-off-by: Jeff Garzik &lt;jgarzik@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>virtio_blk: don't bounce highmem requests</title>
<updated>2009-09-24T15:27:28Z</updated>
<author>
<name>Christoph Hellwig</name>
<email>hch@lst.de</email>
</author>
<published>2009-09-11T22:49:19Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=98d53d73e1a28f0f55de4141ef91799aba0507b6'/>
<id>urn:sha1:98d53d73e1a28f0f55de4141ef91799aba0507b6</id>
<content type='text'>
commit 4eff3cae9c9809720c636e64bc72f212258e0bd5 upstream

virtio_blk: don't bounce highmem requests

By default a block driver bounces highmem requests, but virtio-blk is
perfectly fine with any request that fit into it's 64 bit addressing scheme,
mapped in the kernel virtual space or not.

Besides improving performance on highmem systems this also makes the
reproducible oops in __bounce_end_io go away (but hiding the real cause).

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
Cc: Chuck Ebbert &lt;cebbert@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>V4L: em28xx: set up tda9887_conf in em28xx_card_setup()</title>
<updated>2009-09-24T15:27:27Z</updated>
<author>
<name>Franklin Meng</name>
<email>fmeng2002@yahoo.com</email>
</author>
<published>2009-09-12T14:31:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=330c9c3402b93246476e685c41da974663c152cc'/>
<id>urn:sha1:330c9c3402b93246476e685c41da974663c152cc</id>
<content type='text'>
V4L: em28xx: set up tda9887_conf in em28xx_card_setup()

(cherry picked from commit ae3340cbf59ea362c2016eea762456cc0969fd9e)

Added tda9887_conf set up into em28xx_card_setup()

Signed-off-by: Franklin Meng &lt;fmeng2002@yahoo.com&gt;
Signed-off-by: Douglas Schilling Landgraf &lt;dougsland@redhat.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@redhat.com&gt;
Tested-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Signed-off-by: Michael Krufky &lt;mkrufky@linuxtv.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
</feed>
