On Fri, Mar 08, 2024 at 03:06:01PM +0000, Dave Stevenson wrote: > Assuming I'm correct with the above, the question is how to implement > a solution that corrects the behaviour whilst still supporting the old > DT, and preferably isn't spread far and wide through the code. > Worst case is to require all DMA users and the DMA controller to look > for the dma-ranges property, observe the range isn't present, and drop > back to the current behaviour. > Slightly nicer is to use the knowledge that "ranges" and "dma-ranges" > in this case should be identical, so have the DMA controller driver > attempt a lookup with "ranges" if "dma-ranges" fails. Either of those solutions seems fine to me.
Attachment:
signature.asc
Description: PGP signature
