Hi again,
Felipe Balbi writes:
> David Woodhouse writes:
>> On Tue, 2016-04-19 at 14:38 +0300, Felipe Balbi wrote:
>>>
>>> The reason for that I'm using a manually created platform_device and
>>> that misses dev->archdata which the underlying/parent PCI device has.
>>
>> Typically we'd expect
Hi,
David Woodhouse writes:
> On Tue, 2016-04-19 at 14:38 +0300, Felipe Balbi wrote:
>>
>> The reason for that I'm using a manually created platform_device and
>> that misses dev->archdata which the underlying/parent PCI device has.
>
> Typically we'd expect you to use the parent device for DMA
On Tue, 2016-04-19 at 14:38 +0300, Felipe Balbi wrote:
>
> The reason for that I'm using a manually created platform_device and
> that misses dev->archdata which the underlying/parent PCI device has.
Typically we'd expect you to use the parent device for DMA, as in your
second option.
That said,
Hi folks,
Today I noticed two issues with dwc3 on PCI-based systems which, while
debugging, I uncovered some details which we might want to change,
however I need a little guidance here.
The first problem is that when running with intel-iommu disable and
falling back to swiotlb, I can easily run
