<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/platform, branch v3.10.10</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/platform?h=v3.10.10</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/platform?h=v3.10.10'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2013-08-29T16:47:38Z</updated>
<entry>
<title>drivers/platform/olpc/olpc-ec.c: initialise earlier</title>
<updated>2013-08-29T16:47:38Z</updated>
<author>
<name>Daniel Drake</name>
<email>dsd@laptop.org</email>
</author>
<published>2013-08-22T23:35:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6797361e99b0103055b26c0a3d1079bf2402a3a0'/>
<id>urn:sha1:6797361e99b0103055b26c0a3d1079bf2402a3a0</id>
<content type='text'>
commit 93dbc1b3b506e16c1f6d5b5dcfe756a85cb1dc58 upstream.

Being a low-level component, various drivers (e.g.  olpc-battery) assume
that it is ok to communicate with the OLPC Embedded Controller during
probe.  Therefore the OLPC EC driver must be initialised before other
drivers try to use it.  This was the case until it was recently moved
out of arch/x86 and restructured around commits ac2504151f5a ("Platform:
OLPC: turn EC driver into a platform_driver") and 85f90cf6ca56 ("x86:
OLPC: switch over to using new EC driver on x86").

Use arch_initcall so that olpc-ec is readied earlier, matching the
previous behaviour.

Fixes a regression introduced in Linux-3.6 where various drivers such as
olpc-battery and olpc-xo1-sci failed to load due to an inability to
communicate with the EC.  The user-visible effect was a lack of battery
monitoring, missing ebook/lid switch input devices, etc.

Signed-off-by: Daniel Drake &lt;dsd@laptop.org&gt;
Cc: Andres Salomon &lt;dilinger@queued.net&gt;
Cc: Paul Fox &lt;pgf@laptop.org&gt;
Cc: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>x86 / platform / hp_wmi: Fix bluetooth_rfkill misuse in hp_wmi_rfkill_setup()</title>
<updated>2013-06-01T21:51:48Z</updated>
<author>
<name>lan,Tianyu</name>
<email>tianyu.lan@intel.com</email>
</author>
<published>2013-05-28T02:25:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=af1d486c18bad7820b0ca52b413458914231102c'/>
<id>urn:sha1:af1d486c18bad7820b0ca52b413458914231102c</id>
<content type='text'>
HP wmi platform driver fails to initialize GPS and causes poweroff
failure in HP Elitebook 6930p.

Call Trace:
 [&lt;ffffffffa088d25a&gt;] hp_wmi_bios_setup+0x25a/0x3a0 [hp_wmi]
 [&lt;ffffffff8135978c&gt;] platform_drv_probe+0x3c/0x70
 [&lt;ffffffff81356d6a&gt;] ? driver_sysfs_add+0x7a/0xb0
 [&lt;ffffffff81357407&gt;] driver_probe_device+0x87/0x3a0
 [&lt;ffffffff813577f3&gt;] __driver_attach+0x93/0xa0
 [&lt;ffffffff81357760&gt;] ? __device_attach+0x40/0x40
 [&lt;ffffffff81355403&gt;] bus_for_each_dev+0x63/0xa0
 [&lt;ffffffff81356e8e&gt;] driver_attach+0x1e/0x20
 [&lt;ffffffff81356a28&gt;] bus_add_driver+0x1f8/0x2b0
 [&lt;ffffffff81357e81&gt;] driver_register+0x71/0x150
 [&lt;ffffffff813594e6&gt;] platform_driver_register+0x46/0x50
 [&lt;ffffffff813595ab&gt;] platform_driver_probe+0x1b/0xa0
 [&lt;ffffffffa088d55e&gt;] hp_wmi_init+0x1be/0x1fb [hp_wmi]
 [&lt;ffffffffa088d3a0&gt;] ? hp_wmi_bios_setup+0x3a0/0x3a0 [hp_wmi]
 [&lt;ffffffff8100210a&gt;] do_one_initcall+0x10a/0x160
 [&lt;ffffffff810bdac6&gt;] load_module+0x1b46/0x2640
 [&lt;ffffffff8128da20&gt;] ? ddebug_proc_write+0xf0/0xf0
 [&lt;ffffffff810be662&gt;] sys_init_module+0xa2/0xf0
 [&lt;ffffffff814d975d&gt;] system_call_fastpath+0x1a/0x1f
Code: 48 ff ff ff 80 7b 24 00 74 d2 41 83 e5 01 45 38 ec 74 c9 48 8d bb a0 03 00 00 e8 ed fb aa e0 5b 41 5c 41 5d 44 89 f0 41 5e 5d c3 &lt;0f&gt; 0b 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66
RIP  [&lt;ffffffffa05c57af&gt;] rfkill_set_hw_state+0x9f/0xb0 [rfkill]
 RSP &lt;ffff880071523b60&gt;

Check code and find this error is caused by misusing variable bluetooth_rfkill
where gps_rfkill should be.

Reported-and-tested-by: Iru Cai &lt;mytbk920423@gmail.com&gt;
References: https://bugzilla.kernel.org/show_bug.cgi?id=58401
Cc: All &lt;stable@vger.kernel.org&gt;
Signed-off-by: Lan Tianyu &lt;tianyu.lan@intel.com&gt;
Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;
</content>
</entry>
<entry>
<title>Add support for fan button on Ideapad Z580</title>
<updated>2013-05-09T00:00:50Z</updated>
<author>
<name>Maxim Mikityanskiy</name>
<email>maxtram95@gmail.com</email>
</author>
<published>2013-03-20T10:34:17Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a1ec56ed9f42fb5374cd2add373811c9527c0995'/>
<id>urn:sha1:a1ec56ed9f42fb5374cd2add373811c9527c0995</id>
<content type='text'>
The patch adds support for fan control button on Ideapad Z580. This is
the same button as on Z570, but it raises different bit in
VPCCMD_R_SPECIAL_BUTTONS. Also add message to dmesg when unknown button
press detected, it will help adding support for new special buttons.

Signed-off-by: Maxim Mikityanskiy &lt;maxtram95@gmail.com&gt;
Tested-by: Ivan Vojtko &lt;nekroman.sk@gmail.com&gt;
Signed-off-by: Matthew Garrett &lt;matthew.garrett@nebula.com&gt;
</content>
</entry>
<entry>
<title>pvpanic: pvpanic device driver</title>
<updated>2013-05-08T23:59:52Z</updated>
<author>
<name>Hu Tao</name>
<email>hutao@cn.fujitsu.com</email>
</author>
<published>2013-05-08T03:15:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8b10acd74cdad9063c7a63468e31759d9ac877d9'/>
<id>urn:sha1:8b10acd74cdad9063c7a63468e31759d9ac877d9</id>
<content type='text'>
pvpanic device is a qemu simulated device through which guest panic
event is sent to host.

Signed-off-by: Hu Tao &lt;hutao@cn.fujitsu.com&gt;
Signed-off-by: Matthew Garrett &lt;matthew.garrett@nebula.com&gt;
</content>
</entry>
<entry>
<title>asus-nb-wmi: set wapf=4 for ASUSTeK COMPUTER INC. X75A</title>
<updated>2013-05-08T23:59:52Z</updated>
<author>
<name>AceLan Kao</name>
<email>acelan.kao@canonical.com</email>
</author>
<published>2013-04-25T07:11:07Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a849e0024a84480c7be85e3b723610e14042751b'/>
<id>urn:sha1:a849e0024a84480c7be85e3b723610e14042751b</id>
<content type='text'>
BugLink: http://bugs.launchpad.net/bugs/1172151

Need to set wapf to 4 for ASUSTeK COMPUTER INC. X75A, so that
user can toggle wifi function through function key correctly.

Signed-off-by: AceLan Kao &lt;acelan.kao@canonical.com&gt;
Signed-off-by: Matthew Garrett &lt;matthew.garrett@nebula.com&gt;
</content>
</entry>
<entry>
<title>drivers: platform: x86: Use PTR_RET function</title>
<updated>2013-05-08T23:59:44Z</updated>
<author>
<name>Alexandru Gheorghiu</name>
<email>gheorghiuandru@gmail.com</email>
</author>
<published>2013-03-19T01:01:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2fbaf9b24a953ea13350f9cd9be5609492ea20a7'/>
<id>urn:sha1:2fbaf9b24a953ea13350f9cd9be5609492ea20a7</id>
<content type='text'>
Used PTR_RET function instead of IS_ERR and PTR_ERR.
Patch found using coccinelle.

Signed-off-by: Alexandru Gheorghiu &lt;gheorghiuandru@gmail.com&gt;
Signed-off-by: Matthew Garrett &lt;matthew.garrett@nebula.com&gt;
</content>
</entry>
<entry>
<title>sony-laptop: SVS151290S kbd backlight and gfx switch support</title>
<updated>2013-05-08T23:59:44Z</updated>
<author>
<name>Arthur Wirski</name>
<email>awirski@gmail.com</email>
</author>
<published>2013-03-17T19:21:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0572b12aa23b96afacc936990539f4b67ae64bda'/>
<id>urn:sha1:0572b12aa23b96afacc936990539f4b67ae64bda</id>
<content type='text'>
SVS151290S series uses handle 0x0163 for keyboard backlight and 0x015B for the graphics switch.

Signed-off-by: Arthur Wirski &lt;awirski@gmail.com&gt;
Signed-off-by: Matthew Garrett &lt;matthew.garrett@nebula.com&gt;
</content>
</entry>
<entry>
<title>hp-wmi: add more definitions for new event_id's</title>
<updated>2013-05-08T23:59:44Z</updated>
<author>
<name>Alex Hung</name>
<email>alex.hung@canonical.com</email>
</author>
<published>2013-03-15T09:18:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d9e290a0ff16aaa51d968e7a0714ea5e2ca2407d'/>
<id>urn:sha1:d9e290a0ff16aaa51d968e7a0714ea5e2ca2407d</id>
<content type='text'>
New HP laptops start generating new events, and hp-wmi prints unknown
event_ids for them. This patch also removes these messages

Signed-off-by: Alex Hung &lt;alex.hung@canonical.com&gt;
Signed-off-by: Matthew Garrett &lt;matthew.garrett@nebula.com&gt;
</content>
</entry>
<entry>
<title>dell-laptop: Fix krealloc() misuse in parse_da_table()</title>
<updated>2013-05-08T23:59:44Z</updated>
<author>
<name>David Woodhouse</name>
<email>dwmw2@infradead.org</email>
</author>
<published>2013-03-14T13:33:15Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a30450c7bbb04212c5f01936274ca8d965cabf79'/>
<id>urn:sha1:a30450c7bbb04212c5f01936274ca8d965cabf79</id>
<content type='text'>
If krealloc() returns NULL, it *doesn't* free the original. So any code
of the form 'foo = krealloc(foo, …);' is almost certainly a bug.

Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
Signed-off-by: Matthew Garrett &lt;matthew.garrett@nebula.com&gt;
</content>
</entry>
<entry>
<title>hp_accel: Ignore the error from lis3lv02d_poweron() at resume</title>
<updated>2013-05-08T23:59:44Z</updated>
<author>
<name>Shuah Khan</name>
<email>shuah.khan@hp.com</email>
</author>
<published>2013-03-09T18:39:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7783819920ca52fc582a2782f654fe6ed373f465'/>
<id>urn:sha1:7783819920ca52fc582a2782f654fe6ed373f465</id>
<content type='text'>
The error in lis3lv02_poweron() is harmless in the resume path, so
we should ignore it. It is inline with the other usages of lis3lv02_poweron()
and matches the 3.0 code for this routine. This patch is in suse git and
might have missed making it into the mainline.
opensuse - commit id: 66ccdac87c322cf7af12bddba8c805af640b1cff

Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
Signed-off-by: Shuah Khan &lt;shuah.khan@hp.com&gt;
CC: stable@vger.kernel.org 3.8, 3.4, 3.5, 3.2
Signed-off-by: Matthew Garrett &lt;matthew.garrett@nebula.com&gt;
</content>
</entry>
</feed>
