Commit ae40d5c5 authored by Vinod Koul's avatar Vinod Koul

Merge branch 'topic/doc' into for-linus

parents 40303764 881053f7
...@@ -111,39 +111,35 @@ The first thing you need to do in your driver is to allocate this ...@@ -111,39 +111,35 @@ The first thing you need to do in your driver is to allocate this
structure. Any of the usual memory allocators will do, but you'll also structure. Any of the usual memory allocators will do, but you'll also
need to initialize a few fields in there: need to initialize a few fields in there:
- channels: should be initialized as a list using the - ``channels``: should be initialized as a list using the
INIT_LIST_HEAD macro for example INIT_LIST_HEAD macro for example
- src_addr_widths: - ``src_addr_widths``:
should contain a bitmask of the supported source transfer width should contain a bitmask of the supported source transfer width
- dst_addr_widths: - ``dst_addr_widths``:
should contain a bitmask of the supported destination transfer width should contain a bitmask of the supported destination transfer width
- directions: - ``directions``:
should contain a bitmask of the supported slave directions should contain a bitmask of the supported slave directions
(i.e. excluding mem2mem transfers) (i.e. excluding mem2mem transfers)
- residue_granularity: - ``residue_granularity``:
granularity of the transfer residue reported to dma_set_residue.
- Granularity of the transfer residue reported to dma_set_residue.
This can be either: This can be either:
- Descriptor - Descriptor:
your device doesn't support any kind of residue
- Your device doesn't support any kind of residue
reporting. The framework will only know that a particular reporting. The framework will only know that a particular
transaction descriptor is done. transaction descriptor is done.
- Segment - Segment:
your device is able to report which chunks have been transferred
- Your device is able to report which chunks have been transferred
- Burst
- Your device is able to report which burst have been transferred - Burst:
your device is able to report which burst have been transferred
- dev: should hold the pointer to the ``struct device`` associated - ``dev``: should hold the pointer to the ``struct device`` associated
to your current driver instance. to your current driver instance.
Supported transaction types Supported transaction types
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment