The rk3288 has several iommus. Each iommu belongs to a single master
device. There is one device (ISP) that has two slave iommus, but that
case is not yet supported by this driver.
At subsys init, the iommu driver registers itself as the iommu driver for
the platform bus. The master devices
The rk3288 has several iommus. Each iommu belongs to a single master
device. There is one device (ISP) that has two slave iommus, but that
case is not yet supported by this driver.
At subsys init, the iommu driver registers itself as the iommu driver for
the platform bus. The master devices
Hi Linus,
The following changes since commit fe82dcec644244676d55a1384c958d5f67979adb:
Linux 3.17-rc7 (2014-09-28 14:29:07 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git
tags/iommu-updates-v3.18
for you to fetch changes up to
Hi Will,
On Monday 22 September 2014 18:50:27 Will Deacon wrote:
On Mon, Sep 22, 2014 at 10:29:10AM +0100, Thierry Reding wrote:
On Thu, Sep 18, 2014 at 02:17:33PM +0300, Laurent Pinchart wrote:
On Friday 12 September 2014 17:34:53 Will Deacon wrote:
This patch extends of_dma_configure so
Hi Arnd,
On Tuesday 23 September 2014 09:44:25 Arnd Bergmann wrote:
On Tuesday 23 September 2014 09:02:39 Thierry Reding wrote:
I see two problems with using deferred probing here:
- we don't actually need to defer the probing but the binding to the
driver when no dma ops are set,
Hi Will,
On Monday 22 September 2014 18:13:52 Will Deacon wrote:
On Thu, Sep 18, 2014 at 12:13:13PM +0100, Laurent Pinchart wrote:
Hi Will,
Hi Laurent,
Thank you for the patch.
Sorry for the delay in replying, I was at Connect last week and the email
has backed up.
No worries.
On Tuesday 14 October 2014 16:07:38 Laurent Pinchart wrote:
On Tuesday 23 September 2014 09:44:25 Arnd Bergmann wrote:
On Tuesday 23 September 2014 09:02:39 Thierry Reding wrote:
I see two problems with using deferred probing here:
- we don't actually need to defer the probing but
On Tue, Oct 14, 2014 at 03:20:46PM +0200, Arnd Bergmann wrote:
On Tuesday 14 October 2014 16:07:38 Laurent Pinchart wrote:
On Tuesday 23 September 2014 09:44:25 Arnd Bergmann wrote:
On Tuesday 23 September 2014 09:02:39 Thierry Reding wrote:
I see two problems with using deferred
Hi Thierry,
On Tuesday 14 October 2014 15:37:59 Thierry Reding wrote:
On Tue, Oct 14, 2014 at 03:20:46PM +0200, Arnd Bergmann wrote:
On Tuesday 14 October 2014 16:07:38 Laurent Pinchart wrote:
On Tuesday 23 September 2014 09:44:25 Arnd Bergmann wrote:
On Tuesday 23 September 2014 09:02:39
On Tue, Oct 14, 2014 at 06:01:58PM +0300, Laurent Pinchart wrote:
Hi Thierry,
On Tuesday 14 October 2014 15:37:59 Thierry Reding wrote:
On Tue, Oct 14, 2014 at 03:20:46PM +0200, Arnd Bergmann wrote:
On Tuesday 14 October 2014 16:07:38 Laurent Pinchart wrote:
On Tuesday 23 September
Hi Thierry,
On Tuesday 14 October 2014 17:05:29 Thierry Reding wrote:
On Tue, Oct 14, 2014 at 06:01:58PM +0300, Laurent Pinchart wrote:
On Tuesday 14 October 2014 15:37:59 Thierry Reding wrote:
On Tue, Oct 14, 2014 at 03:20:46PM +0200, Arnd Bergmann wrote:
On Tuesday 14 October 2014
This series introduces support for performing iova-to-phys translations via
the ARM SMMU hardware on supported implementations. We also make use of
some new generic macros for polling hardware registers.
v5..v6:
- iopoll: use shift instead of divide
- arm-smmu: no changes, resending series
Currently, we provide the iommu_ops.iova_to_phys service by doing a
table walk in software to translate IO virtual addresses to physical
addresses. On SMMUs that support it, it can be useful to ask the SMMU
itself to do the translation. This can be used to warm the TLBs for an
SMMU. It can also be
Save msi chip in pci_sys_data instead of assign
msi chip to every pci bus in .add_bus().
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
drivers/pci/host/pcie-designware.c | 15 ---
1 files changed, 4 insertions(+), 11 deletions(-)
diff --git
Use MSI chip framework instead of arch MSI functions to configure
MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework.
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
arch/tile/include/asm/pci.h | 10 ++
arch/tile/kernel/pci_gx.c | 13 +++--
2 files
Commit 465665f78a7 (mips: Kill pointless destroy_irq()) removed
the destroy_irq(). So remove the leftover one in xlp_setup_msix()
to fix build error.
arch/mips/pci/msi-xlp.c: In function 'xlp_setup_msix':
arch/mips/pci/msi-xlp.c:447:3: error: implicit declaration of function
'destroy_irq'..
cc1:
Commit 0e4ccb1505a9 (PCI: Add x86_msi.msi_mask_irq() and msix_mask_irq())
introduced two __weak arch functions arch_msix_mask_irq() and
arch_msi_mask_irq() to work around a bug when running xen in x86.
These two functions made msi code more complex. This patch reverts
the commit and introduces a
Save msi chip in pci_sys_data instead of assign
msi chip to every pci bus in .add_bus().
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
drivers/pci/host/pcie-rcar.c | 13 +++--
1 files changed, 3 insertions(+), 10 deletions(-)
diff --git a/drivers/pci/host/pcie-rcar.c
Use MSI chip framework instead of arch MSI functions to configure
MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework.
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
arch/sparc/kernel/pci.c | 14 --
arch/sparc/kernel/pci_impl.h | 12
2
Use MSI chip framework instead of arch MSI functions to configure
MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework.
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
Hi Michael,
I dropped the Acked-by , because this version has a
lot changes compared to last. So, I guess
Now we can clean up MSI weak arch functions in x86.
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
arch/x86/include/asm/pci.h |5 +
arch/x86/include/asm/x86_init.h |4
arch/x86/kernel/apic/io_apic.c | 21 +
arch/x86/kernel/x86_init.c | 24
Use MSI chip framework instead of arch MSI functions to configure
MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework.
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
drivers/iommu/irq_remapping.c | 11 ---
1 files changed, 8 insertions(+), 3 deletions(-)
diff
Now msi chip is saved in pci_sys_data in arm,
we could clean the bus-msi assignment in
pci core.
Signed-off-by: Yijing Wang wangyij...@huawei.com
CC: Thierry Reding thierry.red...@gmail.com
CC: Thomas Petazzoni thomas.petazz...@free-electrons.com
---
drivers/pci/probe.c |1 -
1 files
Use MSI chip framework instead of arch MSI functions to configure
MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework.
Signed-off-by: Yijing Wang wangyij...@huawei.com
Acked-by: David Vrabel david.vra...@citrix.com
CC: Konrad Rzeszutek Wilk konrad.w...@oracle.com
---
Now there are a lot of weak arch functions in MSI code.
Thierry Reding Introduced MSI chip framework to configure MSI/MSI-X in arm,
that's a better solution than overriding lots of existing weak arch
functionsin.
This series use MSI chip framework to refactor MSI code across all platforms
to
Use MSI chip framework instead of arch MSI functions to configure
MSI/MSI-X IRQ. So we can manage MSI/MSI-X irq in a unified framework.
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
arch/mips/include/asm/netlogic/xlp-hal/pcibus.h |1 +
arch/mips/pci/msi-xlp.c |
MSI chip will be saved in pci_sys_data, now we can
clean up pcibios_add_bus() and pcibios_remove_bus()
in arm, and use pci_find_msi_chip() to get msi chip
in core MSI code.
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
arch/arm/include/asm/mach/pci.h |4
arch/arm/kernel/bios32.c
Now there are a lot of __weak arch functions in MSI code.
These functions make MSI driver complex. Thierry introduced
MSI chip framework to configure MSI/MSI-X irq in arm. Use
MSI chip framework to refactor all other platform MSI
code to eliminate weak arch MSI functions. This patch add
Save msi chip in pci_sys_data instead of assign
msi chip to every pci bus in .add_bus().
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
drivers/pci/host/pci-mvebu.c | 10 +++---
1 files changed, 3 insertions(+), 7 deletions(-)
diff --git a/drivers/pci/host/pci-mvebu.c
Use MSI chip framework instead of arch MSI functions to configure
MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework.
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
Hi Sebastian,
I dropped the Acked-by , because this version has a
lot changes compared to last. So, I
Saving msi chip in pci_sys_data can make pci bus and
devices don't need to know msi chip detail, it also
make pci enumeration code be decoupled from msi chip.
In fact, all pci devices under the same pci hostbridge
share same msi chip. So msi chip should be seen as one
of resources or attributes to
Save msi chip in pci_sys_data instead of assign
msi chip to every pci bus in .add_bus().
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
drivers/pci/host/pci-tegra.c | 13 +++--
1 files changed, 3 insertions(+), 10 deletions(-)
diff --git a/drivers/pci/host/pci-tegra.c
Now we use struct msi_chip in all platforms to configure
MSI/MSI-X. We can clean up the unused arch functions.
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
Hi Lucas,
I dropped the reviewed-by, because this version has a lot changes
compared to last one, I guess you may want to check it
Use MSI chip framework instead of arch MSI functions to configure
MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework.
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
arch/arm/mach-iop13xx/include/mach/pci.h |4
arch/arm/mach-iop13xx/iq81340mc.c|3 +++
Use MSI chip framework instead of arch MSI functions to configure
MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework.
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
arch/mips/pci/pci-xlr.c | 17 +++--
1 files changed, 15 insertions(+), 2 deletions(-)
diff
Use MSI chip framework instead of arch MSI functions to configure
MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework.
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
arch/ia64/include/asm/pci.h | 10 ++
arch/ia64/kernel/msi_ia64.c | 14 ++
From: Yijing Wang wangyij...@huawei.com
Date: Wed, 15 Oct 2014 11:07:13 +0800
Use MSI chip framework instead of arch MSI functions to configure
MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework.
Signed-off-by: Yijing Wang wangyij...@huawei.com
Acked-by: David S. Miller
Now only s390/MSI use default_msi_mask_irq() and
default_msix_mask_irq(), replace them with the common
msi mask irq functions __msi_mask_irq() and __msix_mask_irq().
Remove default_msi_mask_irq() and default_msix_mask_irq().
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
Use MSI chip framework instead of arch MSI functions to configure
MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework.
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
arch/x86/include/asm/pci.h | 13 +
arch/x86/kernel/apic/io_apic.c | 19
39 matches
Mail list logo
