On Fri, Dec 13, 2019 at 2:48 AM Lad Prabhakar <prabhakar.csengg@xxxxxxxxx> wrote: > > From: "Lad, Prabhakar" <prabhakar.mahadev-lad.rj@xxxxxxxxxxxxxx> > > this patch adds support to parse PCI outbound-ranges, the > outbound-regions are similar to pci ranges except it doesn't > have pci address, below is the format for bar-ranges: > > outbound-ranges = <flags upper32_cpuaddr lower32_cpuaddr > upper32_size lower32_size>; You can't just make up a new ranges property. Especially one that doesn't follow how 'ranges' works. We already have 'dma-ranges' to translate device to memory addresses. Explain the problem or feature you need, not the solution you came up with. Why do you need this and other endpoint bindings haven't? Rob