Subject: [RFC] merge dma_direct_ops and dma_noncoherent_ops
While most architectures are either always or never dma coherent for a
given build, the arm, arm64, mips and soon arc architectures can have
different dma coherent settings on a per-device basis. Additionally
some mips builds can decide
Let's try this again as plain text...
For a PCIe device with SR-IOV support enabled (e.g. the PF device ID is 0xf001
at :07:00.0 and the 16 VFs have device ID 0xf002 at :07:01.0 through
:07:02.7), if the hardware attempts a DMA read/write of memory that was
mapped by the PF devfn bu
On Feb 25, 2014 2:28 AM, "Will Deacon" wrote:
>
> On Mon, Feb 24, 2014 at 03:12:21PM +, srikanth TS wrote:
> > Hi Will Deacon,
>
> Hello,
>
> > Currently SMMU driver expecting all stream ID used by respective master
> > should be defined in the DT.
> >
> > We want to know how to handle in the
Hi Will Deacon,
Currently SMMU driver expecting all stream ID used by respective master
should be defined in the DT.
We want to know how to handle in the case of virtual functions dynamically
created and destroyed.
Is PCI driver responsible for creating stream ID respective BDand
requesting SM
