ernel.crashing.org;
> ga...@kernel.crashing.org; linux-kernel@vger.kernel.org; linuxppc-
> d...@lists.ozlabs.org; linux-...@vger.kernel.org; ag...@suse.de; Wood
> Scott-B07421; io...@lists.linux-foundation.org
> Subject: RE: [PATCH 1/7] powerpc: Add interface to get msi region
> infor
...@kernel.crashing.org; linux-kernel@vger.kernel.org; linuxppc-
d...@lists.ozlabs.org; linux-...@vger.kernel.org; ag...@suse.de; Wood
Scott-B07421; io...@lists.linux-foundation.org
Subject: RE: [PATCH 1/7] powerpc: Add interface to get msi region
information
-Original Message-
From
d...@lists.ozlabs.org; linux-...@vger.kernel.org; ag...@suse.de;
> io...@lists.linux-foundation.org; Bhushan Bharat-R65777
> Subject: Re: [PATCH 1/7] powerpc: Add interface to get msi region information
>
> On Thu, 2013-09-19 at 12:59 +0530, Bharat Bhushan wrote:
> > @@ -376,
On Tue, 2013-10-08 at 17:25 -0600, Bjorn Helgaas wrote:
> >> - u32 msiir_offset; /* Offset of MSIIR, relative to start of CCSR */
> >> + dma_addr_t msiir; /* MSIIR Address in CCSR */
> >
> > Are you sure dma_addr_t is right here, versus phys_addr_t? It implies
> > that it's the output of
>> - u32 msiir_offset; /* Offset of MSIIR, relative to start of CCSR */
>> + dma_addr_t msiir; /* MSIIR Address in CCSR */
>
> Are you sure dma_addr_t is right here, versus phys_addr_t? It implies
> that it's the output of the DMA API, but I don't think the DMA API is
> used in the MSI
On Thu, 2013-09-19 at 12:59 +0530, Bharat Bhushan wrote:
> @@ -376,6 +405,7 @@ static int fsl_of_msi_probe(struct platform_device *dev)
> int len;
> u32 offset;
> static const u32 all_avail[] = { 0, NR_MSI_IRQS };
> + static int bank_index;
>
> match =
.kernel.org; linuxppc-
> d...@lists.ozlabs.org; linux-...@vger.kernel.org; ag...@suse.de; Wood Scott-
> B07421; io...@lists.linux-foundation.org
> Subject: Re: [PATCH 1/7] powerpc: Add interface to get msi region information
>
> On Tue, Oct 08, 2013 at 10:47:49AM -0600, Bjorn Helgaas
On Tue, 2013-10-08 at 10:47 -0600, Bjorn Helgaas wrote:
> On Thu, Oct 3, 2013 at 11:19 PM, Bhushan Bharat-R65777
> wrote:
>
> >> I don't know enough about VFIO to understand why these new interfaces are
> >> needed. Is this the first VFIO IOMMU driver? I see
> >> vfio_iommu_spapr_tce.c and
>
On Tue, Oct 08, 2013 at 10:47:49AM -0600, Bjorn Helgaas wrote:
> I still have no idea what an "aperture type IOMMU" is,
> other than that it is "different."
An aperture based IOMMU is basically any GART-like IOMMU which can only
remap a small window (the aperture) of the DMA address space. DMA
On Thu, Oct 3, 2013 at 11:19 PM, Bhushan Bharat-R65777
wrote:
>> I don't know enough about VFIO to understand why these new interfaces are
>> needed. Is this the first VFIO IOMMU driver? I see vfio_iommu_spapr_tce.c
>> and
>> vfio_iommu_type1.c but I don't know if they're comparable to the
On Thu, Oct 3, 2013 at 11:19 PM, Bhushan Bharat-R65777
r65...@freescale.com wrote:
I don't know enough about VFIO to understand why these new interfaces are
needed. Is this the first VFIO IOMMU driver? I see vfio_iommu_spapr_tce.c
and
vfio_iommu_type1.c but I don't know if they're
On Tue, Oct 08, 2013 at 10:47:49AM -0600, Bjorn Helgaas wrote:
I still have no idea what an aperture type IOMMU is,
other than that it is different.
An aperture based IOMMU is basically any GART-like IOMMU which can only
remap a small window (the aperture) of the DMA address space. DMA
outside
On Tue, 2013-10-08 at 10:47 -0600, Bjorn Helgaas wrote:
On Thu, Oct 3, 2013 at 11:19 PM, Bhushan Bharat-R65777
r65...@freescale.com wrote:
I don't know enough about VFIO to understand why these new interfaces are
needed. Is this the first VFIO IOMMU driver? I see
...@lists.ozlabs.org; linux-...@vger.kernel.org; ag...@suse.de; Wood Scott-
B07421; io...@lists.linux-foundation.org
Subject: Re: [PATCH 1/7] powerpc: Add interface to get msi region information
On Tue, Oct 08, 2013 at 10:47:49AM -0600, Bjorn Helgaas wrote:
I still have no idea what an aperture
On Thu, 2013-09-19 at 12:59 +0530, Bharat Bhushan wrote:
@@ -376,6 +405,7 @@ static int fsl_of_msi_probe(struct platform_device *dev)
int len;
u32 offset;
static const u32 all_avail[] = { 0, NR_MSI_IRQS };
+ static int bank_index;
match =
- u32 msiir_offset; /* Offset of MSIIR, relative to start of CCSR */
+ dma_addr_t msiir; /* MSIIR Address in CCSR */
Are you sure dma_addr_t is right here, versus phys_addr_t? It implies
that it's the output of the DMA API, but I don't think the DMA API is
used in the MSI driver.
On Tue, 2013-10-08 at 17:25 -0600, Bjorn Helgaas wrote:
- u32 msiir_offset; /* Offset of MSIIR, relative to start of CCSR */
+ dma_addr_t msiir; /* MSIIR Address in CCSR */
Are you sure dma_addr_t is right here, versus phys_addr_t? It implies
that it's the output of the DMA API,
-...@vger.kernel.org; ag...@suse.de;
io...@lists.linux-foundation.org; Bhushan Bharat-R65777
Subject: Re: [PATCH 1/7] powerpc: Add interface to get msi region information
On Thu, 2013-09-19 at 12:59 +0530, Bharat Bhushan wrote:
@@ -376,6 +405,7 @@ static int fsl_of_msi_probe(struct
crashing.org;
> ga...@kernel.crashing.org; linux-kernel@vger.kernel.org; linuxppc-
> d...@lists.ozlabs.org; linux-...@vger.kernel.org; ag...@suse.de; Wood Scott-
> B07421; io...@lists.linux-foundation.org; Bhushan Bharat-R65777
> Subject: Re: [PATCH 1/7] powerpc: Add interface to get msi
...@kernel.crashing.org; linux-kernel@vger.kernel.org; linuxppc-
d...@lists.ozlabs.org; linux-...@vger.kernel.org; ag...@suse.de; Wood Scott-
B07421; io...@lists.linux-foundation.org; Bhushan Bharat-R65777
Subject: Re: [PATCH 1/7] powerpc: Add interface to get msi region information
On Thu, Sep 19
On Thu, Sep 19, 2013 at 12:59:17PM +0530, Bharat Bhushan wrote:
> This patch adds interface to get following information
> - Number of MSI regions (which is number of MSI banks for powerpc).
> - Get the region address range: Physical page which have the
> address/addresses used for
On Thu, Sep 19, 2013 at 12:59:17PM +0530, Bharat Bhushan wrote:
This patch adds interface to get following information
- Number of MSI regions (which is number of MSI banks for powerpc).
- Get the region address range: Physical page which have the
address/addresses used for generating
22 matches
Mail list logo