Using an abstract number as the DW eDMA chip identifier isn't practical because there can be more than one DW eDMA controller on the platform. Some may be detected as the PCIe Endpoints, and others may be embedded in DW PCIe Root Port/Endpoint controllers. An abstract number in, for instance, the IRQ handlers list, doesn't give a notion regarding their reference to the particular DMA controller. To preserve the code simplicity and support multi-eDMA platforms, use the parental device name to create the DW eDMA controller name.
Showing the changes to include/linux/dma (1 of 4 files). Show all
Unified · Split
| @@ -76,7 +76,6 @@ enum dw_edma_chip_flags { · 75 unmodified lines | |||
| 76 | */ | 76 | */ |
| 77 | struct dw_edma_chip { | 77 | struct dw_edma_chip { |
| 78 | struct device *dev; | 78 | struct device *dev; |
| 79 | int id; | ||
| 80 | int nr_irqs; | 79 | int nr_irqs; |
| 81 | const struct dw_edma_core_ops *ops; | 80 | const struct dw_edma_core_ops *ops; |
| 82 | u32 flags; | 81 | u32 flags; |