<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-toradex.git/drivers, branch v2.6.32.15</title>
<subtitle>Linux kernel for Apalis and Colibri modules</subtitle>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/'/>
<entry>
<title>Revert "ath9k: fix lockdep warning when unloading module" on stable kernels</title>
<updated>2010-05-26T21:29:21+00:00</updated>
<author>
<name>Luis R. Rodriguez</name>
<email>lrodriguez@atheros.com</email>
</author>
<published>2010-05-19T21:33:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=4ee20bc28f74a77307091b15d498e44c7f54645e'/>
<id>4ee20bc28f74a77307091b15d498e44c7f54645e</id>
<content type='text'>
Johannes' patch 34e8950 titled:

	mac80211: allow station add/remove to sleep

changed the way mac80211 adds and removes peers. The new
sta_add() / sta_remove() callbacks allowed the driver callbacks
to sleep. Johannes also ported ath9k to use sta_add() / sta_remove()
via the patch 4ca7786 titled:

	ath9k: convert to new station add/remove callbacks

but this patch forgot to address a change in locking issue which
Ming Lei eventually found on his 2.6.33-wl #12 build. The 2.6.33-wl
build includes code for the 802.11 subsystem for 2.6.34 though so did
already have the above two patches (ath9k_sta_remove() on his trace),
the 2.6.33 kernel did not however have these two patches. Ming eventually
cured his lockdep warnign via the patch a9f042c titled:

	ath9k: fix lockdep warning when unloading module

This went in to 2.6.34 and although it was not marked as a stable
fix it did get trickled down and applied on both 2.6.33 and 2.6.32.

In review, the culprits:

	mac80211: allow station add/remove to sleep
git describe --contains 34e895075e21be3e21e71d6317440d1ee7969ad0
v2.6.34-rc1~233^2~49^2~107

	ath9k: convert to new station add/remove callbacks
git describe --contains 4ca778605cfec53d8a689f0b57babb93b030c784
v2.6.34-rc1~233^2~49^2~10

	ath9k: fix lockdep warning when unloading module

This last one trickled down to 2.6.33 (OK), 2.6.33 (invalid) and 2.6.32 (invalid).

git describe --contains a9f042cbe5284f34ccff15f3084477e11b39b17b
v2.6.34-rc2~48^2~77^2~7
git describe --contains 0524bcfa80f1fffb4e1fe18a0a28900869a58a7c
v2.6.33.2~125
git describe --contains 0dcc9985f34aef3c60bffab3dfc7f7ba3748f35a
v2.6.32.11~79

The patch titled "ath9k: fix lockdep warning when unloading module"
should be reverted on both 2.6.33 and 2.6.32 as it is invalid and
actually ended up causing the following warning:

ADDRCONF(NETDEV_CHANGE): wlan31: link becomes ready
phy0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 txop=0
phy0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 txop=0
phy0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 txop=94
phy0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 txop=47
phy0: device now idle
------------[ cut here ]------------
WARNING: at kernel/softirq.c:143 local_bh_enable_ip+0x7b/0xa0()
Hardware name: 7660A14
Modules linked in: ath9k(-) mac80211 ath cfg80211 &lt;whatever-bleh-etc&gt;
Pid: 2003, comm: rmmod Not tainted 2.6.32.11 #6
Call Trace:
 [&lt;ffffffff8105d178&gt;] warn_slowpath_common+0x78/0xb0
 [&lt;ffffffff8105d1bf&gt;] warn_slowpath_null+0xf/0x20
 [&lt;ffffffff81063f8b&gt;] local_bh_enable_ip+0x7b/0xa0
 [&lt;ffffffff815121e4&gt;] _spin_unlock_bh+0x14/0x20
 [&lt;ffffffffa034aea5&gt;] ath_tx_node_cleanup+0x185/0x1b0 [ath9k]
 [&lt;ffffffffa0345597&gt;] ath9k_sta_notify+0x57/0xb0 [ath9k]
 [&lt;ffffffffa02ac51a&gt;] __sta_info_unlink+0x15a/0x260 [mac80211]
 [&lt;ffffffffa02ac658&gt;] sta_info_unlink+0x38/0x60 [mac80211]
 [&lt;ffffffffa02b3fbe&gt;] ieee80211_set_disassoc+0x1ae/0x210 [mac80211]
 [&lt;ffffffffa02b42d9&gt;] ieee80211_mgd_deauth+0x109/0x110 [mac80211]
 [&lt;ffffffffa02ba409&gt;] ieee80211_deauth+0x19/0x20 [mac80211]
 [&lt;ffffffffa028160e&gt;] __cfg80211_mlme_deauth+0xee/0x130 [cfg80211]
 [&lt;ffffffff81118540&gt;] ? init_object+0x50/0x90
 [&lt;ffffffffa0285429&gt;] __cfg80211_disconnect+0x159/0x1d0 [cfg80211]
 [&lt;ffffffffa027125f&gt;] cfg80211_netdev_notifier_call+0x10f/0x450 [cfg80211]
 [&lt;ffffffff81514ca7&gt;] notifier_call_chain+0x47/0x90
 [&lt;ffffffff8107f501&gt;] raw_notifier_call_chain+0x11/0x20
 [&lt;ffffffff81442d66&gt;] call_netdevice_notifiers+0x16/0x20
 [&lt;ffffffff8144352d&gt;] dev_close+0x4d/0xa0
 [&lt;ffffffff814439a8&gt;] rollback_registered+0x48/0x120
 [&lt;ffffffff81443a9d&gt;] unregister_netdevice+0x1d/0x70
 [&lt;ffffffffa02b6cc4&gt;] ieee80211_remove_interfaces+0x84/0xc0 [mac80211]
 [&lt;ffffffffa02aa072&gt;] ieee80211_unregister_hw+0x42/0xf0 [mac80211]
 [&lt;ffffffffa0347bde&gt;] ath_detach+0x8e/0x180 [ath9k]
 [&lt;ffffffffa0347ce1&gt;] ath_cleanup+0x11/0x50 [ath9k]
 [&lt;ffffffffa0351a2c&gt;] ath_pci_remove+0x1c/0x20 [ath9k]
 [&lt;ffffffff8129d712&gt;] pci_device_remove+0x32/0x60
 [&lt;ffffffff81332373&gt;] __device_release_driver+0x53/0xb0
 [&lt;ffffffff81332498&gt;] driver_detach+0xc8/0xd0
 [&lt;ffffffff81331405&gt;] bus_remove_driver+0x85/0xe0
 [&lt;ffffffff81332a5a&gt;] driver_unregister+0x5a/0x90
 [&lt;ffffffff8129da00&gt;] pci_unregister_driver+0x40/0xb0
 [&lt;ffffffffa03518d0&gt;] ath_pci_exit+0x10/0x20 [ath9k]
 [&lt;ffffffffa0353cd5&gt;] ath9k_exit+0x9/0x2a [ath9k]
 [&lt;ffffffff81092838&gt;] sys_delete_module+0x1a8/0x270
 [&lt;ffffffff8107ebe9&gt;] ? up_read+0x9/0x10
 [&lt;ffffffff81011f82&gt;] system_call_fastpath+0x16/0x1b
---[ end trace fad957019ffdd40b ]---
phy0: Removed STA 00:22:6b:56:fd:e8
phy0: Destroyed STA 00:22:6b:56:fd:e8
wlan31: deauthenticating from 00:22:6b:56:fd:e8 by local choice (reason=3)
ath9k 0000:16:00.0: PCI INT A disabled

The original lockdep fixed an issue where due to the new changes
the driver was not disabling the bottom halves but it is incorrect
to do this on the older kernels since IRQs are already disabled.

Cc: Ming Lei &lt;tom.leiming@gmail.com&gt;
Cc: Johannes Berg &lt;johannes@sipsolutions.net&gt;
Cc: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Luis R. Rodriguez &lt;lrodriguez@atheros.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Johannes' patch 34e8950 titled:

	mac80211: allow station add/remove to sleep

changed the way mac80211 adds and removes peers. The new
sta_add() / sta_remove() callbacks allowed the driver callbacks
to sleep. Johannes also ported ath9k to use sta_add() / sta_remove()
via the patch 4ca7786 titled:

	ath9k: convert to new station add/remove callbacks

but this patch forgot to address a change in locking issue which
Ming Lei eventually found on his 2.6.33-wl #12 build. The 2.6.33-wl
build includes code for the 802.11 subsystem for 2.6.34 though so did
already have the above two patches (ath9k_sta_remove() on his trace),
the 2.6.33 kernel did not however have these two patches. Ming eventually
cured his lockdep warnign via the patch a9f042c titled:

	ath9k: fix lockdep warning when unloading module

This went in to 2.6.34 and although it was not marked as a stable
fix it did get trickled down and applied on both 2.6.33 and 2.6.32.

In review, the culprits:

	mac80211: allow station add/remove to sleep
git describe --contains 34e895075e21be3e21e71d6317440d1ee7969ad0
v2.6.34-rc1~233^2~49^2~107

	ath9k: convert to new station add/remove callbacks
git describe --contains 4ca778605cfec53d8a689f0b57babb93b030c784
v2.6.34-rc1~233^2~49^2~10

	ath9k: fix lockdep warning when unloading module

This last one trickled down to 2.6.33 (OK), 2.6.33 (invalid) and 2.6.32 (invalid).

git describe --contains a9f042cbe5284f34ccff15f3084477e11b39b17b
v2.6.34-rc2~48^2~77^2~7
git describe --contains 0524bcfa80f1fffb4e1fe18a0a28900869a58a7c
v2.6.33.2~125
git describe --contains 0dcc9985f34aef3c60bffab3dfc7f7ba3748f35a
v2.6.32.11~79

The patch titled "ath9k: fix lockdep warning when unloading module"
should be reverted on both 2.6.33 and 2.6.32 as it is invalid and
actually ended up causing the following warning:

ADDRCONF(NETDEV_CHANGE): wlan31: link becomes ready
phy0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 txop=0
phy0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 txop=0
phy0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 txop=94
phy0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 txop=47
phy0: device now idle
------------[ cut here ]------------
WARNING: at kernel/softirq.c:143 local_bh_enable_ip+0x7b/0xa0()
Hardware name: 7660A14
Modules linked in: ath9k(-) mac80211 ath cfg80211 &lt;whatever-bleh-etc&gt;
Pid: 2003, comm: rmmod Not tainted 2.6.32.11 #6
Call Trace:
 [&lt;ffffffff8105d178&gt;] warn_slowpath_common+0x78/0xb0
 [&lt;ffffffff8105d1bf&gt;] warn_slowpath_null+0xf/0x20
 [&lt;ffffffff81063f8b&gt;] local_bh_enable_ip+0x7b/0xa0
 [&lt;ffffffff815121e4&gt;] _spin_unlock_bh+0x14/0x20
 [&lt;ffffffffa034aea5&gt;] ath_tx_node_cleanup+0x185/0x1b0 [ath9k]
 [&lt;ffffffffa0345597&gt;] ath9k_sta_notify+0x57/0xb0 [ath9k]
 [&lt;ffffffffa02ac51a&gt;] __sta_info_unlink+0x15a/0x260 [mac80211]
 [&lt;ffffffffa02ac658&gt;] sta_info_unlink+0x38/0x60 [mac80211]
 [&lt;ffffffffa02b3fbe&gt;] ieee80211_set_disassoc+0x1ae/0x210 [mac80211]
 [&lt;ffffffffa02b42d9&gt;] ieee80211_mgd_deauth+0x109/0x110 [mac80211]
 [&lt;ffffffffa02ba409&gt;] ieee80211_deauth+0x19/0x20 [mac80211]
 [&lt;ffffffffa028160e&gt;] __cfg80211_mlme_deauth+0xee/0x130 [cfg80211]
 [&lt;ffffffff81118540&gt;] ? init_object+0x50/0x90
 [&lt;ffffffffa0285429&gt;] __cfg80211_disconnect+0x159/0x1d0 [cfg80211]
 [&lt;ffffffffa027125f&gt;] cfg80211_netdev_notifier_call+0x10f/0x450 [cfg80211]
 [&lt;ffffffff81514ca7&gt;] notifier_call_chain+0x47/0x90
 [&lt;ffffffff8107f501&gt;] raw_notifier_call_chain+0x11/0x20
 [&lt;ffffffff81442d66&gt;] call_netdevice_notifiers+0x16/0x20
 [&lt;ffffffff8144352d&gt;] dev_close+0x4d/0xa0
 [&lt;ffffffff814439a8&gt;] rollback_registered+0x48/0x120
 [&lt;ffffffff81443a9d&gt;] unregister_netdevice+0x1d/0x70
 [&lt;ffffffffa02b6cc4&gt;] ieee80211_remove_interfaces+0x84/0xc0 [mac80211]
 [&lt;ffffffffa02aa072&gt;] ieee80211_unregister_hw+0x42/0xf0 [mac80211]
 [&lt;ffffffffa0347bde&gt;] ath_detach+0x8e/0x180 [ath9k]
 [&lt;ffffffffa0347ce1&gt;] ath_cleanup+0x11/0x50 [ath9k]
 [&lt;ffffffffa0351a2c&gt;] ath_pci_remove+0x1c/0x20 [ath9k]
 [&lt;ffffffff8129d712&gt;] pci_device_remove+0x32/0x60
 [&lt;ffffffff81332373&gt;] __device_release_driver+0x53/0xb0
 [&lt;ffffffff81332498&gt;] driver_detach+0xc8/0xd0
 [&lt;ffffffff81331405&gt;] bus_remove_driver+0x85/0xe0
 [&lt;ffffffff81332a5a&gt;] driver_unregister+0x5a/0x90
 [&lt;ffffffff8129da00&gt;] pci_unregister_driver+0x40/0xb0
 [&lt;ffffffffa03518d0&gt;] ath_pci_exit+0x10/0x20 [ath9k]
 [&lt;ffffffffa0353cd5&gt;] ath9k_exit+0x9/0x2a [ath9k]
 [&lt;ffffffff81092838&gt;] sys_delete_module+0x1a8/0x270
 [&lt;ffffffff8107ebe9&gt;] ? up_read+0x9/0x10
 [&lt;ffffffff81011f82&gt;] system_call_fastpath+0x16/0x1b
---[ end trace fad957019ffdd40b ]---
phy0: Removed STA 00:22:6b:56:fd:e8
phy0: Destroyed STA 00:22:6b:56:fd:e8
wlan31: deauthenticating from 00:22:6b:56:fd:e8 by local choice (reason=3)
ath9k 0000:16:00.0: PCI INT A disabled

The original lockdep fixed an issue where due to the new changes
the driver was not disabling the bottom halves but it is incorrect
to do this on the older kernels since IRQs are already disabled.

Cc: Ming Lei &lt;tom.leiming@gmail.com&gt;
Cc: Johannes Berg &lt;johannes@sipsolutions.net&gt;
Cc: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Luis R. Rodriguez &lt;lrodriguez@atheros.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</pre>
</div>
</content>
</entry>
<entry>
<title>megaraid_sas: fix for 32bit apps</title>
<updated>2010-05-26T21:29:20+00:00</updated>
<author>
<name>Tomas Henzl</name>
<email>thenzl@redhat.com</email>
</author>
<published>2010-02-11T17:01:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=9e79d5307f9e53930b1cca4440e2691e0c4d0293'/>
<id>9e79d5307f9e53930b1cca4440e2691e0c4d0293</id>
<content type='text'>
commit b3dc1a212e5167984616445990c76056034f8eeb upstream.

It looks like this patch -

commit 7b2519afa1abd1b9f63aa1e90879307842422dae
Author: Yang, Bo &lt;Bo.Yang@lsi.com&gt;
Date:   Tue Oct 6 14:52:20 2009 -0600

    [SCSI] megaraid_sas: fix 64 bit sense pointer truncation

has caused a problem for 32bit programs with 64bit os -

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

fix by converting the user space 32bit pointer to a 64 bit one when
needed.

[jejb: fix up some 64 bit warnings]
Signed-off-by: Tomas Henzl &lt;thenzl@redhat.com&gt;
Cc: Bo Yang &lt;Bo.Yang@lsi.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commit b3dc1a212e5167984616445990c76056034f8eeb upstream.

It looks like this patch -

commit 7b2519afa1abd1b9f63aa1e90879307842422dae
Author: Yang, Bo &lt;Bo.Yang@lsi.com&gt;
Date:   Tue Oct 6 14:52:20 2009 -0600

    [SCSI] megaraid_sas: fix 64 bit sense pointer truncation

has caused a problem for 32bit programs with 64bit os -

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

fix by converting the user space 32bit pointer to a 64 bit one when
needed.

[jejb: fix up some 64 bit warnings]
Signed-off-by: Tomas Henzl &lt;thenzl@redhat.com&gt;
Cc: Bo Yang &lt;Bo.Yang@lsi.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</pre>
</div>
</content>
</entry>
<entry>
<title>p54: disable channels with incomplete calibration data sets</title>
<updated>2010-05-26T21:29:20+00:00</updated>
<author>
<name>Christian Lamparter</name>
<email>chunkeey@googlemail.com</email>
</author>
<published>2009-10-31T21:59:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=7bb08a1cac8ed8e4fda495bd907988bd4077b342'/>
<id>7bb08a1cac8ed8e4fda495bd907988bd4077b342</id>
<content type='text'>
commit 93a59d7527147e3656664aa3179f8d19de256081 upstream.

James Grossmann [1] reported that p54 spews out confusing
messages instead of preventing the mayhem from happening.

the reason is that "p54: generate channel list dynamically"
is not perfect. It didn't discard incomplete channel data
sets and therefore p54 advertised to support them as well.

[1]: http://marc.info/?l=linux-wireless&amp;m=125699830215890

Cc: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Reported-by: James Grossmann &lt;cctsurf@gmail.com&gt;
Signed-off-by: Christian Lamparter &lt;chunkeey@web.de&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commit 93a59d7527147e3656664aa3179f8d19de256081 upstream.

James Grossmann [1] reported that p54 spews out confusing
messages instead of preventing the mayhem from happening.

the reason is that "p54: generate channel list dynamically"
is not perfect. It didn't discard incomplete channel data
sets and therefore p54 advertised to support them as well.

[1]: http://marc.info/?l=linux-wireless&amp;m=125699830215890

Cc: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Reported-by: James Grossmann &lt;cctsurf@gmail.com&gt;
Signed-off-by: Christian Lamparter &lt;chunkeey@web.de&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</pre>
</div>
</content>
</entry>
<entry>
<title>iwlwifi: clear all the stop_queue flag after load firmware</title>
<updated>2010-05-26T21:29:20+00:00</updated>
<author>
<name>Wey-Yi Guy</name>
<email>wey-yi.w.guy@intel.com</email>
</author>
<published>2010-02-09T16:14:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=79ec1d305fe1f2aa77797118fd31ea41e72e7867'/>
<id>79ec1d305fe1f2aa77797118fd31ea41e72e7867</id>
<content type='text'>
commit a9e10fb9b1c6ad16e73cf2656951fce3a817611e upstream.

All the queues are awake and ready to use after loading firmware,
for firmware reload case, if any queues was stopped before
reload, mac80211 will wake those queues after restart hardware, so make
sure all the flag used to keep track of the queue status are
reset correctly.

Signed-off-by: Wey-Yi Guy &lt;wey-yi.w.guy@intel.com&gt;
Signed-off-by: Reinette Chatre &lt;reinette.chatre@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commit a9e10fb9b1c6ad16e73cf2656951fce3a817611e upstream.

All the queues are awake and ready to use after loading firmware,
for firmware reload case, if any queues was stopped before
reload, mac80211 will wake those queues after restart hardware, so make
sure all the flag used to keep track of the queue status are
reset correctly.

Signed-off-by: Wey-Yi Guy &lt;wey-yi.w.guy@intel.com&gt;
Signed-off-by: Reinette Chatre &lt;reinette.chatre@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</pre>
</div>
</content>
</entry>
<entry>
<title>serial: imx.c: fix CTS trigger level lower to avoid lost chars</title>
<updated>2010-05-26T21:29:16+00:00</updated>
<author>
<name>Valentin Longchamp</name>
<email>valentin.longchamp@epfl.ch</email>
</author>
<published>2010-05-05T09:47:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=5eb1c77df310f6def7a8d9e9e2e2061142a2ad63'/>
<id>5eb1c77df310f6def7a8d9e9e2e2061142a2ad63</id>
<content type='text'>
commit 1c5250d6163dac28be3afabdfb6c723f107051b7 upstream.

The imx CTS trigger level is left at its reset value that is 32
chars. Since the RX FIFO has 32 entries, when CTS is raised, the
FIFO already is full. However, some serial port devices first empty
their TX FIFO before stopping when CTS is raised, resulting in lost
chars.

This patch sets the trigger level lower so that other chars arrive
after CTS is raised, there is still room for 16 of them.

Signed-off-by: Valentin Longchamp&lt;valentin.longchamp@epfl.ch&gt;
Tested-by: Philippe Rétornaz&lt;philippe.retornaz@epfl.ch&gt;
Acked-by: Wolfram Sang&lt;w.sang@pengutronix.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commit 1c5250d6163dac28be3afabdfb6c723f107051b7 upstream.

The imx CTS trigger level is left at its reset value that is 32
chars. Since the RX FIFO has 32 entries, when CTS is raised, the
FIFO already is full. However, some serial port devices first empty
their TX FIFO before stopping when CTS is raised, resulting in lost
chars.

This patch sets the trigger level lower so that other chars arrive
after CTS is raised, there is still room for 16 of them.

Signed-off-by: Valentin Longchamp&lt;valentin.longchamp@epfl.ch&gt;
Tested-by: Philippe Rétornaz&lt;philippe.retornaz@epfl.ch&gt;
Acked-by: Wolfram Sang&lt;w.sang@pengutronix.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</pre>
</div>
</content>
</entry>
<entry>
<title>mmc: atmel-mci: remove data error interrupt after xfer</title>
<updated>2010-05-26T21:29:15+00:00</updated>
<author>
<name>Nicolas Ferre</name>
<email>nicolas.ferre@atmel.com</email>
</author>
<published>2010-05-11T21:06:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=ee7a0b92fcc8d1ab43cff3dd75baeb2f646a93ff'/>
<id>ee7a0b92fcc8d1ab43cff3dd75baeb2f646a93ff</id>
<content type='text'>
commit abc2c9fdf636c4335a8d72ac3c5ae152bca44b68 upstream.

Disable data error interrupts while we are actually recording that there
is not such errors.  This will prevent, in some cases, the warning message
printed at new request queuing (in atmci_start_request()).

Signed-off-by: Nicolas Ferre &lt;nicolas.ferre@atmel.com&gt;
Cc: Haavard Skinnemoen &lt;hskinnemoen@atmel.com&gt;
Cc: &lt;linux-mmc@vger.kernel.org&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@suse.de&gt;

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commit abc2c9fdf636c4335a8d72ac3c5ae152bca44b68 upstream.

Disable data error interrupts while we are actually recording that there
is not such errors.  This will prevent, in some cases, the warning message
printed at new request queuing (in atmci_start_request()).

Signed-off-by: Nicolas Ferre &lt;nicolas.ferre@atmel.com&gt;
Cc: Haavard Skinnemoen &lt;hskinnemoen@atmel.com&gt;
Cc: &lt;linux-mmc@vger.kernel.org&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@suse.de&gt;

</pre>
</div>
</content>
</entry>
<entry>
<title>mmc: atmel-mci: prevent kernel oops while removing card</title>
<updated>2010-05-26T21:29:15+00:00</updated>
<author>
<name>Nicolas Ferre</name>
<email>nicolas.ferre@atmel.com</email>
</author>
<published>2010-05-11T21:06:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=eac2ef18972dbc56c2540c7302a6c7a1437352ef'/>
<id>eac2ef18972dbc56c2540c7302a6c7a1437352ef</id>
<content type='text'>
commit 009a891b22395fc86e5f34057d79fffee4509ab5 upstream.

The removing of an SD card in certain circumstances can lead to a kernel
oops if we do not make sure that the "data" field of the host structure is
valid.  This patch adds a test in atmci_dma_cleanup() function and also
calls atmci_stop_dma() before throwing away the reference to data.

Signed-off-by: Nicolas Ferre &lt;nicolas.ferre@atmel.com&gt;
Cc: Haavard Skinnemoen &lt;hskinnemoen@atmel.com&gt;
Cc: &lt;linux-mmc@vger.kernel.org&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@suse.de&gt;

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commit 009a891b22395fc86e5f34057d79fffee4509ab5 upstream.

The removing of an SD card in certain circumstances can lead to a kernel
oops if we do not make sure that the "data" field of the host structure is
valid.  This patch adds a test in atmci_dma_cleanup() function and also
calls atmci_stop_dma() before throwing away the reference to data.

Signed-off-by: Nicolas Ferre &lt;nicolas.ferre@atmel.com&gt;
Cc: Haavard Skinnemoen &lt;hskinnemoen@atmel.com&gt;
Cc: &lt;linux-mmc@vger.kernel.org&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@suse.de&gt;

</pre>
</div>
</content>
</entry>
<entry>
<title>mmc: atmel-mci: fix two parameters swapped</title>
<updated>2010-05-26T21:29:15+00:00</updated>
<author>
<name>Nicolas Ferre</name>
<email>nicolas.ferre@atmel.com</email>
</author>
<published>2010-05-11T21:06:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=85e346fae9b44a4acfe4d63afae62eae4c25e586'/>
<id>85e346fae9b44a4acfe4d63afae62eae4c25e586</id>
<content type='text'>
commit ebb1fea9b3adf25d7e2f643c614163af4f93a17f upstream.

Two parameters were swapped in the calls to atmci_init_slot().

Signed-off-by: Nicolas Ferre &lt;nicolas.ferre@atmel.com&gt;
Reported-by: Anders Grahn &lt;anders.grahn@hd-wireless.se&gt;
Cc: Haavard Skinnemoen &lt;hskinnemoen@atmel.com&gt;
Cc: &lt;linux-mmc@vger.kernel.org&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@suse.de&gt;

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commit ebb1fea9b3adf25d7e2f643c614163af4f93a17f upstream.

Two parameters were swapped in the calls to atmci_init_slot().

Signed-off-by: Nicolas Ferre &lt;nicolas.ferre@atmel.com&gt;
Reported-by: Anders Grahn &lt;anders.grahn@hd-wireless.se&gt;
Cc: Haavard Skinnemoen &lt;hskinnemoen@atmel.com&gt;
Cc: &lt;linux-mmc@vger.kernel.org&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@suse.de&gt;

</pre>
</div>
</content>
</entry>
<entry>
<title>ACPI: sleep: eliminate duplicate entries in acpisleep_dmi_table[]</title>
<updated>2010-05-26T21:29:14+00:00</updated>
<author>
<name>Alex Chiang</name>
<email>achiang@canonical.com</email>
</author>
<published>2010-05-11T16:21:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=e053045d37ac1f3d62be0e9cc81f54d5b9980c9e'/>
<id>e053045d37ac1f3d62be0e9cc81f54d5b9980c9e</id>
<content type='text'>
commit 7d6fb7bd1919517937ec390f6ca2d7bcf4f89fb6 upstream.

Duplicate entries ended up acpisleep_dmi_table[] by accident.
They don't hurt functionality, but they are ugly, so let's get
rid of them.

Signed-off-by: Alex Chiang &lt;achiang@canonical.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commit 7d6fb7bd1919517937ec390f6ca2d7bcf4f89fb6 upstream.

Duplicate entries ended up acpisleep_dmi_table[] by accident.
They don't hurt functionality, but they are ugly, so let's get
rid of them.

Signed-off-by: Alex Chiang &lt;achiang@canonical.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</pre>
</div>
</content>
</entry>
<entry>
<title>fbdev: bfin-t350mcqb-fb: fix fbmem allocation with blanking lines</title>
<updated>2010-05-26T21:29:14+00:00</updated>
<author>
<name>Michael Hennerich</name>
<email>michael.hennerich@analog.com</email>
</author>
<published>2010-05-11T21:07:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=ec9dd41fc73ca85b0afb21ce4bbf563afeb08d6d'/>
<id>ec9dd41fc73ca85b0afb21ce4bbf563afeb08d6d</id>
<content type='text'>
commit de145b44b95b9d3212a82d1c0f29b09778ef33c5 upstream.

The current allocation does not include the memory required for blanking
lines.  So avoid memory corruption when multiple devices are using the DMA
memory near each other.

Signed-off-by: Michael Hennerich &lt;michael.hennerich@analog.com&gt;
Signed-off-by: Mike Frysinger &lt;vapier@gentoo.org&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@suse.de&gt;

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commit de145b44b95b9d3212a82d1c0f29b09778ef33c5 upstream.

The current allocation does not include the memory required for blanking
lines.  So avoid memory corruption when multiple devices are using the DMA
memory near each other.

Signed-off-by: Michael Hennerich &lt;michael.hennerich@analog.com&gt;
Signed-off-by: Mike Frysinger &lt;vapier@gentoo.org&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@suse.de&gt;

</pre>
</div>
</content>
</entry>
</feed>
