diff for duplicates of <332b42e3-67c6-9471-e18f-4d54954e3be3@gmail.com> diff --git a/a/1.txt b/N1/1.txt index ae8c169..e75804e 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -22,41 +22,41 @@ On 09/26/2018 03:56 AM, Robin Murphy wrote: >>>>>>>>>>> <jim2101024@gmail.com> wrote: >>>>>>>>>>>> The Broadcom STB PCIe host controller is intimately related >>>>>>>>>>>> to the ->>>>>>>>>>>> memory subsystem. This close relationship adds complexity +>>>>>>>>>>>> memory subsystem.? This close relationship adds complexity >>>>>>>>>>>> to how cpu ->>>>>>>>>>>> system memory is mapped to PCIe memory. Ideally, this +>>>>>>>>>>>> system memory is mapped to PCIe memory.? Ideally, this >>>>>>>>>>>> mapping is an ->>>>>>>>>>>> identity mapping, or an identity mapping off by a constant. +>>>>>>>>>>>> identity mapping, or an identity mapping off by a constant.? >>>>>>>>>>>> Not so in >>>>>>>>>>>> this case. >>>>>>>>>>>> >>>>>>>>>>>> Consider the Broadcom reference board BCM97445LCC_4X8 which >>>>>>>>>>>> has 6 GB ->>>>>>>>>>>> of system memory. Here is how the PCIe controller maps the +>>>>>>>>>>>> of system memory.? Here is how the PCIe controller maps the >>>>>>>>>>>> system memory to PCIe memory: >>>>>>>>>>>> ->>>>>>>>>>>> memc0-a@[ 0....3fffffff] <=> pci@[ +>>>>>>>>>>>> ?? memc0-a@[??????? 0....3fffffff] <=> pci@[??????? >>>>>>>>>>>> 0....3fffffff] ->>>>>>>>>>>> memc0-b@[100000000...13fffffff] <=> pci@[ +>>>>>>>>>>>> ?? memc0-b@[100000000...13fffffff] <=> pci@[ >>>>>>>>>>>> 40000000....7fffffff] ->>>>>>>>>>>> memc1-a@[ 40000000....7fffffff] <=> pci@[ +>>>>>>>>>>>> ?? memc1-a@[ 40000000....7fffffff] <=> pci@[ >>>>>>>>>>>> 80000000....bfffffff] ->>>>>>>>>>>> memc1-b@[300000000...33fffffff] <=> pci@[ +>>>>>>>>>>>> ?? memc1-b@[300000000...33fffffff] <=> pci@[ >>>>>>>>>>>> c0000000....ffffffff] ->>>>>>>>>>>> memc2-a@[ 80000000....bfffffff] <=> +>>>>>>>>>>>> ?? memc2-a@[ 80000000....bfffffff] <=> >>>>>>>>>>>> pci@[100000000...13fffffff] ->>>>>>>>>>>> memc2-b@[c00000000...c3fffffff] <=> +>>>>>>>>>>>> ?? memc2-b@[c00000000...c3fffffff] <=> >>>>>>>>>>>> pci@[140000000...17fffffff] >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> So is describing this as >>>>>>>>>>> >>>>>>>>>>> dma-ranges = <0x0 0x0 0x0 0x0 0x0 0x40000000>, ->>>>>>>>>>> <0x0 0x40000000 0x1 0x0 0x0 0x40000000>, ->>>>>>>>>>> <0x0 0x80000000 0x0 0x40000000 0x0 0x40000000>, ->>>>>>>>>>> <0x0 0xc0000000 0x3 0x0 0x0 0x40000000>, ->>>>>>>>>>> <0x1 0x0 0x0 0x80000000 0x0 0x40000000>, ->>>>>>>>>>> <0x1 0x40000000 0x0 0xc0000000 0x0 0x40000000>; +>>>>>>>>>>> ????????????? <0x0 0x40000000 0x1 0x0 0x0 0x40000000>, +>>>>>>>>>>> ????????????? <0x0 0x80000000 0x0 0x40000000 0x0 0x40000000>, +>>>>>>>>>>> ????????????? <0x0 0xc0000000 0x3 0x0 0x0 0x40000000>, +>>>>>>>>>>> ????????????? <0x1 0x0 0x0 0x80000000 0x0 0x40000000>, +>>>>>>>>>>> ????????????? <0x1 0x40000000 0x0 0xc0000000 0x0 0x40000000>; >>>>>>>>>>> >>>>>>>>>>> not working for you? I haven't tried this myself, but since >>>>>>>>>>> DT permits @@ -78,9 +78,9 @@ On 09/26/2018 03:56 AM, Robin Murphy wrote: >>>>>>>>> Optional property: >>>>>>>>> - dma-ranges: <prop-encoded-array> encoded as arbitrary number >>>>>>>>> of triplets of ->>>>>>>>> (child-bus-address, parent-bus-address, length). Each +>>>>>>>>> ???????? (child-bus-address, parent-bus-address, length). Each >>>>>>>>> triplet specified ->>>>>>>>> describes a contiguous DMA address range. +>>>>>>>>> ???????? describes a contiguous DMA address range. >>>>>>>>> """ >>>>>>>>> >>>>>>>> @@ -106,10 +106,10 @@ On 09/26/2018 03:56 AM, Robin Murphy wrote: >>>>>> sure this is working for PCIe devices, although, conceptually it >>>>>> should, >>>>>> yes. ->>>>> Sorry for my delay in responding. One problem is that +>>>>> Sorry for my delay in responding.? One problem is that >>>>> of_dma_configure() only looks at the first dma-range given and then >>>>> converts it to dev->dma_pfn_offset which is respected by the DMA API. ->>>>> However, we often have multiple dma-ranges, not just one. This is the +>>>>> However, we often have multiple dma-ranges, not just one.? This is the >>>>> big issue. >>>>> >>>> @@ -122,7 +122,7 @@ On 09/26/2018 03:56 AM, Robin Murphy wrote: >>> https://lists.linuxfoundation.org/pipermail/iommu/2017-April/021325.html >>> >>> In the thread "Oza Oza", a Broadcom coworker probably dealing with the ->>> same exact problem as I, enumerates three problems. #1 and #2 are +>>> same exact problem as I,? enumerates three problems.?? #1 and #2 are >>> the exact same ones I've just given: the "dma-ranges" prop of the RC >>> DT node is "skipped", and of_dma_get_range() only considers the first >>> entry in any "dma-ranges". @@ -160,7 +160,7 @@ possible layering problem too... >>>>> driver on "bridge->parent->of_node", which is our RC device, >>>>> Of_dma_configure() calls of_dma_range() on the of_get_next_parent() of >>>>> our RC's device node and this misses the dma-ranges property which is ->>>>> contained within the RC. I think I could workaround this but there is +>>>>> contained within the RC.? I think I could workaround this but there is >>>>> no getting around the first problem. >>>>> >>>> diff --git a/a/content_digest b/N1/content_digest index 669599e..f02d292 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -11,22 +11,10 @@ "ref\0CANCKTBtbwSqfSU0b_d6Yi7TV3R_ijEpPE8a4bpgpkcOxJOa_zQ@mail.gmail.com\0" "ref\07accc1a7-647b-1f92-13f8-2fab315ddc45@gmail.com\0" "ref\07b25b09e-6f99-8a9b-d548-03becd9de8b5@arm.com\0" - "From\0Florian Fainelli <f.fainelli@gmail.com>\0" - "Subject\0Re: [PATCH v5 04/12] PCI: brcmstb: add dma-range mapping for inbound traffic\0" + "From\0f.fainelli@gmail.com (Florian Fainelli)\0" + "Subject\0[PATCH v5 04/12] PCI: brcmstb: add dma-range mapping for inbound traffic\0" "Date\0Mon, 1 Oct 2018 11:13:12 -0700\0" - "To\0Robin Murphy <robin.murphy@arm.com>" - Florian Fainelli <f.fainelli@gmail.com> - Jim Quinlan <jim2101024@gmail.com> - " ard.biesheuvel@linaro.org\0" - "Cc\0Christoph Hellwig <hch@lst.de>" - linux-kernel@vger.kernel.org - Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> - linux-pci <linux-pci@vger.kernel.org> - bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com> - Gregory Fong <gregory.0xf0@gmail.com> - Bjorn Helgaas <bhelgaas@google.com> - Brian Norris <computersforpeace@gmail.com> - " moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE <linux-arm-kernel@lists.infradead.org>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On 09/26/2018 03:56 AM, Robin Murphy wrote:\n" @@ -53,41 +41,41 @@ ">>>>>>>>>>> <jim2101024@gmail.com> wrote:\n" ">>>>>>>>>>>> The Broadcom STB PCIe host controller is intimately related\n" ">>>>>>>>>>>> to the\n" - ">>>>>>>>>>>> memory subsystem.\302\240 This close relationship adds complexity\n" + ">>>>>>>>>>>> memory subsystem.? This close relationship adds complexity\n" ">>>>>>>>>>>> to how cpu\n" - ">>>>>>>>>>>> system memory is mapped to PCIe memory.\302\240 Ideally, this\n" + ">>>>>>>>>>>> system memory is mapped to PCIe memory.? Ideally, this\n" ">>>>>>>>>>>> mapping is an\n" - ">>>>>>>>>>>> identity mapping, or an identity mapping off by a constant.\302\240\n" + ">>>>>>>>>>>> identity mapping, or an identity mapping off by a constant.?\n" ">>>>>>>>>>>> Not so in\n" ">>>>>>>>>>>> this case.\n" ">>>>>>>>>>>>\n" ">>>>>>>>>>>> Consider the Broadcom reference board BCM97445LCC_4X8 which\n" ">>>>>>>>>>>> has 6 GB\n" - ">>>>>>>>>>>> of system memory.\302\240 Here is how the PCIe controller maps the\n" + ">>>>>>>>>>>> of system memory.? Here is how the PCIe controller maps the\n" ">>>>>>>>>>>> system memory to PCIe memory:\n" ">>>>>>>>>>>>\n" - ">>>>>>>>>>>> \302\240\302\240 memc0-a@[\302\240\302\240\302\240\302\240\302\240\302\240\302\240 0....3fffffff] <=> pci@[\302\240\302\240\302\240\302\240\302\240\302\240\302\240\n" + ">>>>>>>>>>>> ?? memc0-a@[??????? 0....3fffffff] <=> pci@[???????\n" ">>>>>>>>>>>> 0....3fffffff]\n" - ">>>>>>>>>>>> \302\240\302\240 memc0-b@[100000000...13fffffff] <=> pci@[\n" + ">>>>>>>>>>>> ?? memc0-b@[100000000...13fffffff] <=> pci@[\n" ">>>>>>>>>>>> 40000000....7fffffff]\n" - ">>>>>>>>>>>> \302\240\302\240 memc1-a@[ 40000000....7fffffff] <=> pci@[\n" + ">>>>>>>>>>>> ?? memc1-a@[ 40000000....7fffffff] <=> pci@[\n" ">>>>>>>>>>>> 80000000....bfffffff]\n" - ">>>>>>>>>>>> \302\240\302\240 memc1-b@[300000000...33fffffff] <=> pci@[\n" + ">>>>>>>>>>>> ?? memc1-b@[300000000...33fffffff] <=> pci@[\n" ">>>>>>>>>>>> c0000000....ffffffff]\n" - ">>>>>>>>>>>> \302\240\302\240 memc2-a@[ 80000000....bfffffff] <=>\n" + ">>>>>>>>>>>> ?? memc2-a@[ 80000000....bfffffff] <=>\n" ">>>>>>>>>>>> pci@[100000000...13fffffff]\n" - ">>>>>>>>>>>> \302\240\302\240 memc2-b@[c00000000...c3fffffff] <=>\n" + ">>>>>>>>>>>> ?? memc2-b@[c00000000...c3fffffff] <=>\n" ">>>>>>>>>>>> pci@[140000000...17fffffff]\n" ">>>>>>>>>>>>\n" ">>>>>>>>>>>\n" ">>>>>>>>>>> So is describing this as\n" ">>>>>>>>>>>\n" ">>>>>>>>>>> dma-ranges = <0x0 0x0 0x0 0x0 0x0 0x40000000>,\n" - ">>>>>>>>>>> \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240 <0x0 0x40000000 0x1 0x0 0x0 0x40000000>,\n" - ">>>>>>>>>>> \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240 <0x0 0x80000000 0x0 0x40000000 0x0 0x40000000>,\n" - ">>>>>>>>>>> \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240 <0x0 0xc0000000 0x3 0x0 0x0 0x40000000>,\n" - ">>>>>>>>>>> \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240 <0x1 0x0 0x0 0x80000000 0x0 0x40000000>,\n" - ">>>>>>>>>>> \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240 <0x1 0x40000000 0x0 0xc0000000 0x0 0x40000000>;\n" + ">>>>>>>>>>> ????????????? <0x0 0x40000000 0x1 0x0 0x0 0x40000000>,\n" + ">>>>>>>>>>> ????????????? <0x0 0x80000000 0x0 0x40000000 0x0 0x40000000>,\n" + ">>>>>>>>>>> ????????????? <0x0 0xc0000000 0x3 0x0 0x0 0x40000000>,\n" + ">>>>>>>>>>> ????????????? <0x1 0x0 0x0 0x80000000 0x0 0x40000000>,\n" + ">>>>>>>>>>> ????????????? <0x1 0x40000000 0x0 0xc0000000 0x0 0x40000000>;\n" ">>>>>>>>>>>\n" ">>>>>>>>>>> not working for you? I haven't tried this myself, but since\n" ">>>>>>>>>>> DT permits\n" @@ -109,9 +97,9 @@ ">>>>>>>>> Optional property:\n" ">>>>>>>>> - dma-ranges: <prop-encoded-array> encoded as arbitrary number\n" ">>>>>>>>> of triplets of\n" - ">>>>>>>>> \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240 (child-bus-address, parent-bus-address, length). Each\n" + ">>>>>>>>> ???????? (child-bus-address, parent-bus-address, length). Each\n" ">>>>>>>>> triplet specified\n" - ">>>>>>>>> \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240 describes a contiguous DMA address range.\n" + ">>>>>>>>> ???????? describes a contiguous DMA address range.\n" ">>>>>>>>> \"\"\"\n" ">>>>>>>>>\n" ">>>>>>>>\n" @@ -137,10 +125,10 @@ ">>>>>> sure this is working for PCIe devices, although, conceptually it\n" ">>>>>> should,\n" ">>>>>> yes.\n" - ">>>>> Sorry for my delay in responding.\302\240 One problem is that\n" + ">>>>> Sorry for my delay in responding.? One problem is that\n" ">>>>> of_dma_configure() only looks at the first dma-range given and then\n" ">>>>> converts it to dev->dma_pfn_offset which is respected by the DMA API.\n" - ">>>>> However, we often have multiple dma-ranges, not just one.\302\240 This is the\n" + ">>>>> However, we often have multiple dma-ranges, not just one.? This is the\n" ">>>>> big issue.\n" ">>>>>\n" ">>>>\n" @@ -153,7 +141,7 @@ ">>> https://lists.linuxfoundation.org/pipermail/iommu/2017-April/021325.html\n" ">>>\n" ">>> In the thread \"Oza Oza\", a Broadcom coworker probably dealing with the\n" - ">>> same exact problem as I,\302\240 enumerates three problems.\302\240\302\240 #1 and #2 are\n" + ">>> same exact problem as I,? enumerates three problems.?? #1 and #2 are\n" ">>> the exact same ones I've just given: the \"dma-ranges\" prop of the RC\n" ">>> DT node is \"skipped\", and of_dma_get_range() only considers the first\n" ">>> entry in any \"dma-ranges\".\n" @@ -191,7 +179,7 @@ ">>>>> driver on \"bridge->parent->of_node\", which is our RC device,\n" ">>>>> Of_dma_configure() calls of_dma_range() on the of_get_next_parent() of\n" ">>>>> our RC's device node and this misses the dma-ranges property which is\n" - ">>>>> contained within the RC.\302\240 I think I could workaround this but there is\n" + ">>>>> contained within the RC.? I think I could workaround this but there is\n" ">>>>> no getting around the first problem.\n" ">>>>>\n" ">>>>\n" @@ -212,4 +200,4 @@ "-- \n" Florian -778923cb41df03c0c0b47dfd6c8bc1f536e9a08b8ede7317e8766e18c5a08dfa +9cb0cc4c60a3fd2fb876925af8a1c44bdb45f4bebfa1a3e7a090dcf3655390d0
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.