Re: [RFC PATCH v0.001] PCI: Add support for tango PCIe controller

2017-03-21 Thread Mason
On 21/03/2017 15:23, Liviu Dudau wrote: > On Tue, Mar 21, 2017 at 02:01:57PM +0100, Mason wrote: > >> My PCIe controller is b/d/f 0/0/0. >> It ignores all PCI addresses that do not fall within the range >> defined in BAR0 of b/d/f 0/0/0. >> >> BAR0 has a configurable width of 2^(23+i) bytes, i < 8

Re: [RFC PATCH v0.001] PCI: Add support for tango PCIe controller

2017-03-21 Thread Liviu Dudau
On Tue, Mar 21, 2017 at 02:01:57PM +0100, Mason wrote: > On 21/03/2017 13:31, Liviu Dudau wrote: > > > On Tue, Mar 21, 2017 at 11:15:16AM +0100, Mason wrote: > >> > >> On 17/03/2017 17:11, Mason wrote: > >> > >>> + * QUIRK #5 > >>> + * Only transfers within the BAR are forwarded to the host. > >>>

Re: [RFC PATCH v0.001] PCI: Add support for tango PCIe controller

2017-03-21 Thread Mason
On 21/03/2017 13:31, Liviu Dudau wrote: > On Tue, Mar 21, 2017 at 11:15:16AM +0100, Mason wrote: >> >> On 17/03/2017 17:11, Mason wrote: >> >>> + * QUIRK #5 >>> + * Only transfers within the BAR are forwarded to the host. >>> + * By default, the DMA framework expects that >>> + * PCI address 0x800

Re: [RFC PATCH v0.001] PCI: Add support for tango PCIe controller

2017-03-21 Thread Liviu Dudau
On Tue, Mar 21, 2017 at 11:15:16AM +0100, Mason wrote: > [ Adding iommu ML ] > > On 17/03/2017 17:11, Mason wrote: > > > + * QUIRK #5 > > + * Only transfers within the BAR are forwarded to the host. > > + * By default, the DMA framework expects that > > + * PCI address 0x8000_ -> CPU address

Re: [RFC PATCH v0.001] PCI: Add support for tango PCIe controller

2017-03-21 Thread Thibaud Cornic
On 21/03/2017 13:43, Mason wrote: > On 21/03/2017 12:36, Robin Murphy wrote: > >> On 21/03/17 10:15, Mason wrote: >> >>> I suppose one may consider the above limitation ("Only transfers >>> within the BAR are forwarded to the host") as some form of weird >>> IOMMU? (There is, in fact, some remappin

Re: [RFC PATCH v0.001] PCI: Add support for tango PCIe controller

2017-03-21 Thread Mason
On 21/03/2017 12:36, Robin Murphy wrote: > On 21/03/17 10:15, Mason wrote: > >> I suppose one may consider the above limitation ("Only transfers >> within the BAR are forwarded to the host") as some form of weird >> IOMMU? (There is, in fact, some remapping logic in the controller >> setup which I

Re: [RFC PATCH v0.001] PCI: Add support for tango PCIe controller

2017-03-21 Thread Robin Murphy
On 21/03/17 10:15, Mason wrote: > [ Adding iommu ML ] > > On 17/03/2017 17:11, Mason wrote: > >> + * QUIRK #5 >> + * Only transfers within the BAR are forwarded to the host. >> + * By default, the DMA framework expects that >> + * PCI address 0x8000_ -> CPU address 0x8000_ >> + * which is

Re: [RFC PATCH v0.001] PCI: Add support for tango PCIe controller

2017-03-21 Thread Mason
[ Adding iommu ML ] On 17/03/2017 17:11, Mason wrote: > + * QUIRK #5 > + * Only transfers within the BAR are forwarded to the host. > + * By default, the DMA framework expects that > + * PCI address 0x8000_ -> CPU address 0x8000_ > + * which is where DRAM0 is mapped. I have an additional