ioat2,3: put channel hardware in known state at init
authorDan Williams <dan.j.williams@intel.com>
Sat, 19 Dec 2009 22:36:02 +0000 (15:36 -0700)
committerGreg Kroah-Hartman <gregkh@suse.de>
Wed, 6 Jan 2010 23:03:59 +0000 (15:03 -0800)
commit8b9f03819c4165799c463b14a30b23f228d13cdb
treeeb947a8fc76e4cc84a95ca1101c9f71be7979b3a
parente05a6f0307a79b77319eed3c892a9c09613f1a28
ioat2,3: put channel hardware in known state at init

commit a6d52d70677e99bdb89b6921c265d0a58c22e597 upstream.

Put the ioat2 and ioat3 state machines in the halted state with all
errors cleared.

The ioat1 init path is not disturbed for stability, there are no
reported ioat1 initiaization issues.

Reported-by: Roland Dreier <rdreier@cisco.com>
Tested-by: Roland Dreier <rdreier@cisco.com>
Acked-by: Simon Horman <horms@verge.net.au>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
drivers/dma/ioat/dma.c
drivers/dma/ioat/dma.h
drivers/dma/ioat/dma_v2.c
drivers/dma/ioat/dma_v2.h
drivers/dma/ioat/dma_v3.c
drivers/dma/ioat/registers.h