linux-toradex.git/drivers/dma/ioat, branch tegra-9.12.14

ioat: fix infinite timeout checking in ioat2_quiesce

2010-02-23T15:37:49+00:00

commit 7e55a70c5b9a57c12f49c44b0847c9343d4f54e4 upstream.

Fix typo in ioat2_quiesce. check 'tmo' is zero, not 'end'.  Also applies
to 2.6.32.3

Signed-off-by: Dan Williams 
Signed-off-by: Greg Kroah-Hartman

ioat2,3: put channel hardware in known state at init

2010-01-06T23:03:59+00:00

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 
Tested-by: Roland Dreier 
Acked-by: Simon Horman 
Signed-off-by: Dan Williams 
Signed-off-by: Greg Kroah-Hartman

ioat3: fix p-disabled q-continuation

2010-01-06T23:03:58+00:00

commit cd78809f6191485a90ea6c92c2b58900ab5c156f upstream.

When continuing a pq calculation the driver needs 3 extra sources.  The
driver can perform a 3 source calculation with a single descriptor, but
needs an extended descriptor to process up to 8 sources in one
operation.  However, in the p-disabled case only one extra source is
needed.  When continuing a p-disabled operation there are occasions
(i.e. 0 < src_cnt % 8 < 3) where the tail operation does not need an
extended descriptor.  Properly account for this fact otherwise invalid
'dmacount' values will be written to hardware usually causing the
channel to halt with 'invalid descriptor' errors.

Signed-off-by: Dan Williams 
Signed-off-by: Greg Kroah-Hartman

ioat3: fix pq completion versus channel deallocation race

2009-11-20T06:21:03+00:00

The completion of a pq operation is notified with a null descriptor
appended to the end of the chain.  This descriptor needs to be visible
to dma clients otherwise the client is precluded from ensuring all
operations are quiesced before freeing channel resources, i.e. due to
descriptor polling it may get the completion notification ahead of the
interrupt delivered by the null descriptor.

Signed-off-by: Dan Williams

async_tx: build-time toggling of async_{syndrome,xor}_val dma support

2009-11-20T06:21:03+00:00

ioat3.2 does not support asynchronous error notifications which makes
the driver experience latencies when non-zero pq validate results are
expected.  Provide a mechanism for turning off async_xor_val and
async_syndrome_val via Kconfig.  This approach is generally useful for
any driver that specifies ASYNC_TX_DISABLE_CHANNEL_SWITCH and would like
to force the async_tx api to fall back to the synchronous path for
certain operations.

Signed-off-by: Dan Williams

ioat2,3: report all uncorrectable errors

2009-11-20T06:21:03+00:00

Modify is_ioat_bug() to catch all errors that are uncorrectable, or not
currently handled.

Signed-off-by: Dan Williams

ioat3: specify valid address for disabled-Q or disabled-P

2009-11-20T00:08:45+00:00

Although disabled, hardware still checks address validity, so duplicate
the known address.

Signed-off-by: Dan Williams

ioat2,3: disable asynchronous error notifications

2009-11-20T00:07:57+00:00

Error interrupts and error completions may cause channel hangs, so
poll the channel status register after a timeout.

Signed-off-by: Dan Williams

ioat3: dca and raid operations are incompatible

2009-11-20T00:07:10+00:00

RAID operations cause a system hang on platforms with DCA
(Direct-Cache-Access) enabled.  So turn off RAID capabilities in this
case.

Signed-off-by: Dan Williams

ioat: silence "dca disabled" messages

2009-11-17T18:34:31+00:00

Turning off dca is not an "error", and the dca-enabled state can be
viewed from sysfs.

Signed-off-by: Dan Williams