Unacceptable levels of debug info will happen when the DMA driver defined in the DT/ACPI is a blacklisted module. Another cause for log polution would be the defer probing of the DMA driver taking too long - in which case the message that this commit removes would be cluttering the logs due to the init daemons activity.
Unified · Split
| @@ -284,7 +284,6 @@ static void pl011_dma_probe(struct uart_amba_port *uap) · 283 unmodified lines | |||
| 284 | chan = dma_request_slave_channel_reason(dev, "tx"); | 284 | chan = dma_request_slave_channel_reason(dev, "tx"); |
| 285 | if (IS_ERR(chan)) { | 285 | if (IS_ERR(chan)) { |
| 286 | if (PTR_ERR(chan) == -EPROBE_DEFER) { | 286 | if (PTR_ERR(chan) == -EPROBE_DEFER) { |
| 287 | dev_info(uap->port.dev, "DMA driver not ready\n"); | ||
| 288 | uap->dma_probed = false; | 287 | uap->dma_probed = false; |
| 289 | return; | 288 | return; |
| 290 | } | 289 | } |