<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/platform, branch v3.0.79</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/platform?h=v3.0.79</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/platform?h=v3.0.79'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2013-03-28T19:06:14Z</updated>
<entry>
<title>asus-laptop: Do not call HWRS on init</title>
<updated>2013-03-28T19:06:14Z</updated>
<author>
<name>Ben Hutchings</name>
<email>ben@decadent.org.uk</email>
</author>
<published>2012-11-29T08:12:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f2c1a6c85f3cf6be6cf0ddf38fc8a0a5b05498fb'/>
<id>urn:sha1:f2c1a6c85f3cf6be6cf0ddf38fc8a0a5b05498fb</id>
<content type='text'>
commit cb7da022450cdaaebd33078b6b32fb7dd2aaf6db upstream.

Since commit 8871e99f89b7 ('asus-laptop: HRWS/HWRS typo'), module
initialisation is very slow on the Asus UL30A.  The HWRS method takes
about 12 seconds to run, and subsequent initialisation also seems to
be delayed.  Since we don't really need the result, don't bother
calling it on init.  Those who are curious can still get the result
through the 'infos' device attribute.

Update the comment about HWRS in show_infos().

Reported-by: ryan &lt;draziw+deb@gmail.com&gt;
References: http://bugs.debian.org/692436
Signed-off-by: Ben Hutchings &lt;ben@decadent.org.uk&gt;
Signed-off-by: Corentin Chary &lt;corentin.chary@gmail.com&gt;
Signed-off-by: Matthew Garrett &lt;matthew.garrett@nebula.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>acer-wmi: support for P key on TM8372</title>
<updated>2012-12-03T20:59:15Z</updated>
<author>
<name>Merlin Schumacher</name>
<email>merlin.schumacher@gmail.com</email>
</author>
<published>2012-01-23T20:35:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f7118e1b0eec39161739ec702ea359427ade26b2'/>
<id>urn:sha1:f7118e1b0eec39161739ec702ea359427ade26b2</id>
<content type='text'>
commit 67e1d34cd54cbf33f093f1dd53e7bda1124eb972 upstream.

BugLink: http://launchpad.net/bugs/865807

There is no entry for P key on TM8372, so when P key is pressed, only
"acer_wmi: Unknown key number - 0x29" in dmesg.

Signed-off-by: Merlin Schumacher &lt;merlin.schumacher@gmail.com&gt;
Signed-off-by: Ike Panhc &lt;ike.pan@canonical.com&gt;
Signed-off-by: Matthew Garrett &lt;mjg@redhat.com&gt;
Cc: maximilian attems &lt;max@stro.at&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>asus-nb-wmi: add some video toggle keys</title>
<updated>2012-10-02T16:47:40Z</updated>
<author>
<name>AceLan Kao</name>
<email>acelan.kao@canonical.com</email>
</author>
<published>2012-07-04T07:20:14Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7693ca135d181dbc9748f0612bf010cc1681eba0'/>
<id>urn:sha1:7693ca135d181dbc9748f0612bf010cc1681eba0</id>
<content type='text'>
commit 3766054fff4af1b58a1440a284907887f4d2e8be upstream.

There are some new video switch keys that used by newer machines.
0xA0 - SDSP HDMI only
0xA1 - SDSP LCD + HDMI
0xA2 - SDSP CRT + HDMI
0xA3 - SDSP TV + HDMI
But in Linux, there is no suitable userspace application to handle this,
so, mapping them all to KEY_SWITCHVIDEOMODE.

Signed-off-by: AceLan Kao &lt;acelan.kao@canonical.com&gt;
Signed-off-by: Matthew Garrett &lt;mjg@redhat.com&gt;
Cc: Tim Gardner &lt;tim.gardner@canonical.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>asus-laptop: HRWS/HWRS typo</title>
<updated>2012-10-02T16:47:40Z</updated>
<author>
<name>Corentin Chary</name>
<email>corentin.chary@gmail.com</email>
</author>
<published>2012-08-20T21:01:51Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=06aac3b6df0a805f066aa8f5dcf830eeb7f353a3'/>
<id>urn:sha1:06aac3b6df0a805f066aa8f5dcf830eeb7f353a3</id>
<content type='text'>
commit 8871e99f89b7d7b1ea99de550eea2a56273f42ab upstream.

Resolves-bug: https://bugzilla.kernel.org/show_bug.cgi?id=24222
Signed-off-by: Corentin Chary &lt;corentin.chary@gmail.com&gt;
Signed-off-by: Matthew Garrett &lt;mjg@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>intel_ips: blacklist HP ProBook laptops</title>
<updated>2012-07-19T15:58:21Z</updated>
<author>
<name>Takashi Iwai</name>
<email>tiwai@suse.de</email>
</author>
<published>2012-06-25T13:07:17Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=19b0759e73cdf97db6f36ac04bbd37d3feb0657b'/>
<id>urn:sha1:19b0759e73cdf97db6f36ac04bbd37d3feb0657b</id>
<content type='text'>
commit 88ca518b0bb4161e5f20f8a1d9cc477cae294e54 upstream.

intel_ips driver spews the warning message
  "ME failed to update for more than 1s, likely hung"
at each second endlessly on HP ProBook laptops with IronLake.

As this has never worked, better to blacklist the driver for now.

Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
Signed-off-by: Matthew Garrett &lt;mjg@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>sony-laptop: Enable keyboard backlight by default</title>
<updated>2012-05-21T16:40:00Z</updated>
<author>
<name>Josh Boyer</name>
<email>jwboyer@redhat.com</email>
</author>
<published>2011-11-02T18:32:00Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d1e6e65a8d800bc91fb2389a33f2d9d8447bcfbd'/>
<id>urn:sha1:d1e6e65a8d800bc91fb2389a33f2d9d8447bcfbd</id>
<content type='text'>
commit 6fe6ae56a7cebaebc2e6daa11c423e4692f9b592 upstream.

When the keyboard backlight support was originally added, the commit said
to default it to on with a 10 second timeout.  That actually wasn't the
case, as the default value is commented out for the kbd_backlight parameter.
Because it is a static variable, it gets set to 0 by default without some
other form of initialization.

However, it seems the function to set the value wasn't actually called
immediately, so whatever state the keyboard was in initially would remain.
Then commit df410d522410e67660 was introduced during the 2.6.39 timeframe to
immediately set whatever value was present (as well as attempt to
restore/reset the state on module removal or resume).  That seems to have
now forced the light off immediately when the module is loaded unless
the option kbd_backlight=1 is specified.

Let's enable it by default again (for the first time).  This should solve
https://bugzilla.redhat.com/show_bug.cgi?id=728478

Signed-off-by: Josh Boyer &lt;jwboyer@redhat.com&gt;
Acked-by: Mattia Dongili &lt;malattia@linux.it&gt;
Signed-off-by: Matthew Garrett &lt;mjg@redhat.com&gt;
Cc: maximilian attems &lt;max@stro.at&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>acer-wmi: No wifi rfkill on Sony machines</title>
<updated>2012-04-13T15:14:08Z</updated>
<author>
<name>Lee, Chun-Yi</name>
<email>joeyli.kernel@gmail.com</email>
</author>
<published>2012-03-23T04:36:44Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1802657ecb10d7ca620c3cf642920009d1aa2ec3'/>
<id>urn:sha1:1802657ecb10d7ca620c3cf642920009d1aa2ec3</id>
<content type='text'>
commit 5719b81988f3c24ff694dc3a37e35b35630a3966 upstream.

The wireless rfkill should charged by sony-laptop but not acer-wmi.
So, add Sony's SNY5001 acpi device to blacklist in acer-wmi.

Tested on Sony Vaio

Cc: Carlos Corbacho &lt;carlos@strangeworlds.co.uk&gt;
Cc: Matthew Garrett &lt;mjg@redhat.com&gt;
Cc: Mattia Dongili &lt;malattia@linux.it&gt;
Cc: Dimitris N &lt;ddarlac@gmail.com&gt;
Tested-by: Dimitris N &lt;ddarlac@gmail.com&gt;
Signed-off-by: Lee, Chun-Yi &lt;jlee@suse.com&gt;
Signed-off-by: Matthew Garrett &lt;mjg@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>acer-wmi: No wifi rfkill on Lenovo machines</title>
<updated>2012-03-19T15:57:45Z</updated>
<author>
<name>Ike Panhc</name>
<email>ike.pan@canonical.com</email>
</author>
<published>2012-02-03T08:46:39Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7affb2673c36d8fb93ac39e889b674c95eb3c8f8'/>
<id>urn:sha1:7affb2673c36d8fb93ac39e889b674c95eb3c8f8</id>
<content type='text'>
commit 461e74377cfcfc2c0d6bbdfa8fc5fbc21b052c2a upstream.

We have several reports which says acer-wmi is loaded on ideapads
and register rfkill for wifi which can not be unblocked.

Since ideapad-laptop also register rfkill for wifi and it works
reliably, it will be fine acer-wmi is not going to register rfkill
for wifi once VPC2004 is found.

Also put IBM0068/LEN0068 in the list. Though thinkpad_acpi has no
wifi rfkill capability, there are reports which says acer-wmi also
block wireless on Thinkpad E520/E420.

Signed-off-by: Ike Panhc &lt;ike.pan@canonical.com&gt;
Signed-off-by: Matthew Garrett &lt;mjg@redhat.com&gt;
Cc: Jonathan Nieder &lt;jrnieder@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>acer-wmi: check wireless capability flag before register rfkill</title>
<updated>2012-03-19T15:57:45Z</updated>
<author>
<name>Lee, Chun-Yi</name>
<email>joeyli.kernel@gmail.com</email>
</author>
<published>2011-08-18T10:47:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2b033b873b428b01d8508ba9f0c56b9246ab31b4'/>
<id>urn:sha1:2b033b873b428b01d8508ba9f0c56b9246ab31b4</id>
<content type='text'>
commit 1709adab0773616da7a8190f2762e599afb0a295 upstream.

There will be better to check the wireless capability flag
(ACER_CAP_WIRELESS) before register wireless rfkill because maybe
the machine doesn't have wifi module or the module removed by user.

Tested on Acer Travelmate 8572
Tested on Acer Aspire 4739Z

Tested-by: AceLan Kao &lt;acelan.kao@canonical.com&gt;
Cc: Carlos Corbacho &lt;carlos@strangeworlds.co.uk&gt;
Cc: Matthew Garrett &lt;mjg@redhat.com&gt;
Cc: Dmitry Torokhov &lt;dtor@mail.ru&gt;
Cc: Corentin Chary &lt;corentincj@iksaif.net&gt;
Cc: Thomas Renninger &lt;trenn@suse.de&gt;
Signed-off-by: Lee, Chun-Yi &lt;jlee@suse.com&gt;
Signed-off-by: Matthew Garrett &lt;mjg@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>acer-wmi: Add wireless quirk for Lenovo 3000 N200</title>
<updated>2012-03-19T15:57:44Z</updated>
<author>
<name>Seth Forshee</name>
<email>seth.forshee@canonical.com</email>
</author>
<published>2011-10-06T20:01:55Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=bbc1505482e5bb16fa956e23f22dae6cd25172e6'/>
<id>urn:sha1:bbc1505482e5bb16fa956e23f22dae6cd25172e6</id>
<content type='text'>
commit be3128b107e36271f7973ef213ccde603a494fe8 upstream.

This quirk fixes the wlan rfkill status on this machine. Without
it, wlan is permanently soft blocked whenever acer-wmi is loaded.

BugLink: https://bugs.launchpad.net/bugs/857297
Signed-off-by: Seth Forshee &lt;seth.forshee@canonical.com&gt;
Reviewed-by: Lee, Chun-Yi &lt;jlee@novell.com&gt;
Signed-off-by: Matthew Garrett &lt;mjg@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

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