diff options
| author | Simon Glass <sjg@chromium.org> | 2015-03-25 12:21:53 -0600 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2015-04-18 11:11:19 -0600 |
| commit | 2c03c4633b092d695d04bd38053da4d7dc59a9a5 (patch) | |
| tree | a9cbb4c80fbb9a902056440555e009446a63906a /include | |
| parent | e23eb614a415afa6bc2b3609b4f7a07c0f425744 (diff) | |
| download | talos-obmc-uboot-2c03c4633b092d695d04bd38053da4d7dc59a9a5.tar.gz talos-obmc-uboot-2c03c4633b092d695d04bd38053da4d7dc59a9a5.zip | |
dm: core: Support allocating driver-private data for DMA
Some driver want to put DMA buffers in their private data. Add a flag
to tell driver model to align driver-private data to a cache boundary so
that DMA will work correctly in this case.
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Marek Vasut <marex@denx.de>
Diffstat (limited to 'include')
| -rw-r--r-- | include/dm/device.h | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/include/dm/device.h b/include/dm/device.h index 698095493e..f27b34b699 100644 --- a/include/dm/device.h +++ b/include/dm/device.h @@ -30,6 +30,9 @@ struct driver_info; /* DM is responsible for allocating and freeing parent_platdata */ #define DM_FLAG_ALLOC_PARENT_PDATA (1 << 3) +/* Allocate driver private data on a DMA boundary */ +#define DM_FLAG_ALLOC_PRIV_DMA (1 << 4) + /** * struct udevice - An instance of a driver * |
