search for: arm_iommu_sync_single_for_cpu

...ess the only way is to handle it all by ourselves here. :/ > ... and it really sucks. Basically if we cannot use the DMA API here > we will lose the convenience of having a portable API that does just > the right thing for the underlying platform. Without it we would have > to duplicate arm_iommu_sync_single_for_cpu/device() and we would only > have support for ARM. > > The usage of the DMA API that we are doing might be illegal, but in > essence it does exactly what we need - at least for ARM. What are the > alternatives? Convert TTM to use the dma api? :-) ~Maarten

On 06/24/2014 07:33 PM, Alexandre Courbot wrote: > On 06/24/2014 07:02 PM, Russell King - ARM Linux wrote: >> On Tue, Jun 24, 2014 at 06:54:26PM +0900, Alexandre Courbot wrote: >>> From: Lucas Stach <dev at lynxeye.de> >>> >>> On architectures for which access to GPU memory is non-coherent, >>> caches need to be flushed and invalidated explicitly

...to handle it all by ourselves here. :/ > > ... and it really sucks. Basically if we cannot use the DMA API here > > we will lose the convenience of having a portable API that does just > > the right thing for the underlying platform. Without it we would have > > to duplicate arm_iommu_sync_single_for_cpu/device() and we would only > > have support for ARM. > > > > The usage of the DMA API that we are doing might be illegal, but in > > essence it does exactly what we need - at least for ARM. What are the > > alternatives? > Convert TTM to use the dma api? :-) Actual...

...:/ > >> > ... and it really sucks. Basically if we cannot use the DMA API here > >> > we will lose the convenience of having a portable API that does just > >> > the right thing for the underlying platform. Without it we would have > >> > to duplicate arm_iommu_sync_single_for_cpu/device() and we would only > >> > have support for ARM. > >> > > >> > The usage of the DMA API that we are doing might be illegal, but in > >> > essence it does exactly what we need - at least for ARM. What are the > >> > alternatives? &gt...

...by ourselves here. :/ >> > ... and it really sucks. Basically if we cannot use the DMA API here >> > we will lose the convenience of having a portable API that does just >> > the right thing for the underlying platform. Without it we would have >> > to duplicate arm_iommu_sync_single_for_cpu/device() and we would only >> > have support for ARM. >> > >> > The usage of the DMA API that we are doing might be illegal, but in >> > essence it does exactly what we need - at least for ARM. What are the >> > alternatives? >> Convert TTM to use...

...e only way is to handle it all by ourselves here. :/ > > ... and it really sucks. Basically if we cannot use the DMA API here > we will lose the convenience of having a portable API that does just > the right thing for the underlying platform. Without it we would have > to duplicate arm_iommu_sync_single_for_cpu/device() and we would only > have support for ARM. > > The usage of the DMA API that we are doing might be illegal, but in > essence it does exactly what we need - at least for ARM. What are the > alternatives? It may seem /to you/ as a driver developer to be the easiest thing in t...

...gt; done for it. Guess the only way is to handle it all by ourselves here. :/ ... and it really sucks. Basically if we cannot use the DMA API here we will lose the convenience of having a portable API that does just the right thing for the underlying platform. Without it we would have to duplicate arm_iommu_sync_single_for_cpu/device() and we would only have support for ARM. The usage of the DMA API that we are doing might be illegal, but in essence it does exactly what we need - at least for ARM. What are the alternatives?

...by ourselves here. :/ >> > ... and it really sucks. Basically if we cannot use the DMA API here >> > we will lose the convenience of having a portable API that does just >> > the right thing for the underlying platform. Without it we would have >> > to duplicate arm_iommu_sync_single_for_cpu/device() and we would only >> > have support for ARM. >> > >> > The usage of the DMA API that we are doing might be illegal, but in >> > essence it does exactly what we need - at least for ARM. What are the >> > alternatives? >> Convert TTM to use...

...re. :/ >>> > ... and it really sucks. Basically if we cannot use the DMA API here >>> > we will lose the convenience of having a portable API that does just >>> > the right thing for the underlying platform. Without it we would have >>> > to duplicate arm_iommu_sync_single_for_cpu/device() and we would only >>> > have support for ARM. >>> > >>> > The usage of the DMA API that we are doing might be illegal, but in >>> > essence it does exactly what we need - at least for ARM. What are the >>> > alternatives? >>...

...> > ... and it really sucks. Basically if we cannot use the DMA API here >> >> > we will lose the convenience of having a portable API that does just >> >> > the right thing for the underlying platform. Without it we would have >> >> > to duplicate arm_iommu_sync_single_for_cpu/device() and we would only >> >> > have support for ARM. >> >> > >> >> > The usage of the DMA API that we are doing might be illegal, but in >> >> > essence it does exactly what we need - at least for ARM. What are the >> >> &g...

...ndle it all by ourselves here. :/ >> >> ... and it really sucks. Basically if we cannot use the DMA API here >> we will lose the convenience of having a portable API that does just >> the right thing for the underlying platform. Without it we would have >> to duplicate arm_iommu_sync_single_for_cpu/device() and we would only >> have support for ARM. >> >> The usage of the DMA API that we are doing might be illegal, but in >> essence it does exactly what we need - at least for ARM. What are the >> alternatives? > > It may seem /to you/ as a driver developer...