| commit | c293537daaea858a1ae4ad05e30a8cc0d8a1deb2 | |
| author | Stuart Hayes <stuart_hayes@yahoo.com> | |
| Wed, 2 Mar 2011 12:42:05 +0000 (2 13:42 +0100) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Sun, 27 Mar 2011 18:30:51 +0000 (27 11:30 -0700) | ||
| tree | 36bf723f1e857807b3a625c65698b48fa4206ca6 | treesnapshot (tar.gz zip) |
| parent | 221b9dc74a436532a905bddb2304e23799c8788a | commitdiff |
dcdbas: force SMI to happen when expected
commit dd65c736d1b5312c80c88a64bf521db4959eded5 upstream.
The dcdbas driver can do an I/O write to cause a SMI to occur. The SMI handler
looks at certain registers and memory locations, so the SMI needs to happen
immediately. On some systems I/O writes are posted, though, causing the SMI to
happen well after the "outb" occurred, which causes random failures. Following
the "outb" with an "inb" forces the write to go through even if it is posted.
Signed-off-by: Stuart Hayes <stuart_hayes@yahoo.com>
Acked-by: Doug Warzecha <douglas_warzecha@dell.com>
Cc: Chuck Ebbert <cebbert@redhat.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
commit dd65c736d1b5312c80c88a64bf521db4959eded5 upstream.
The dcdbas driver can do an I/O write to cause a SMI to occur. The SMI handler
looks at certain registers and memory locations, so the SMI needs to happen
immediately. On some systems I/O writes are posted, though, causing the SMI to
happen well after the "outb" occurred, which causes random failures. Following
the "outb" with an "inb" forces the write to go through even if it is posted.
Signed-off-by: Stuart Hayes <stuart_hayes@yahoo.com>
Acked-by: Doug Warzecha <douglas_warzecha@dell.com>
Cc: Chuck Ebbert <cebbert@redhat.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| drivers/firmware/dcdbas.c | diffblobblamehistory |