Re: [RFC 2/5] dt-bindings: brcm: Add reserved-dma-region for iPROC

On 15/03/18 12:03, Jitendra Bhivare wrote: On Thu, Mar 15, 2018 at 12:15 AM, Robin Murphy wrote: On 12/03/18 07:03, Jitendra Bhivare wrote: On Tue, Mar 6, 2018 at 5:12 PM, Robin Murphy wrote: On 06/03/18 04:59, Jitendra Bhivare wrote: With

Re: [RFC 2/5] dt-bindings: brcm: Add reserved-dma-region for iPROC

On Thu, Mar 15, 2018 at 12:15 AM, Robin Murphy wrote: > On 12/03/18 07:03, Jitendra Bhivare wrote: >> >> On Tue, Mar 6, 2018 at 5:12 PM, Robin Murphy wrote: >>> >>> On 06/03/18 04:59, Jitendra Bhivare wrote: With SoC wide DMA mask of

Re: [RFC 2/5] dt-bindings: brcm: Add reserved-dma-region for iPROC

On 12/03/18 07:03, Jitendra Bhivare wrote: On Tue, Mar 6, 2018 at 5:12 PM, Robin Murphy wrote: On 06/03/18 04:59, Jitendra Bhivare wrote: With SoC wide DMA mask of 40-bit, the mappings for entire IOVA space can't be specified in the PAXBv2 PCIe RC of SoC. The holes in

Re: [RFC 2/5] dt-bindings: brcm: Add reserved-dma-region for iPROC

On Tue, Mar 6, 2018 at 5:12 PM, Robin Murphy wrote: > On 06/03/18 04:59, Jitendra Bhivare wrote: >> >> With SoC wide DMA mask of 40-bit, the mappings for entire IOVA space can't >> be specified in the PAXBv2 PCIe RC of SoC. The holes in IOVA space needs >> to >> be reserved

Re: [RFC 2/5] dt-bindings: brcm: Add reserved-dma-region for iPROC

On 06/03/18 04:59, Jitendra Bhivare wrote: With SoC wide DMA mask of 40-bit, the mappings for entire IOVA space can't be specified in the PAXBv2 PCIe RC of SoC. The holes in IOVA space needs to be reserved to prevent any IOVA allocations in those spaces. Can you clarify why? If this is the PCI

[RFC 2/5] dt-bindings: brcm: Add reserved-dma-region for iPROC

With SoC wide DMA mask of 40-bit, the mappings for entire IOVA space can't be specified in the PAXBv2 PCIe RC of SoC. The holes in IOVA space needs to be reserved to prevent any IOVA allocations in those spaces. reserved-dma-region property is added to specify the ranges which should never be