Add linux-samsung-...@vger.kernel.org mailing list.
On 7 January 2015 at 18:31, Hongbo Zhang wrote:
> Hi Cho KyongHo, Joerg et al,
> I found the latest Exynos IOMMU driver doesn't work, the line 481:
> BUG_ON(!has_sysmmu(dev));
> in function __exynos_sysmmu_enable() in file exynos-iommu.c trigger
On Thursday 08 January 2015 18:44:31 Murali Karicheri wrote:
> The grep of dma-ranges for arch/arm shows the size used is mask + 1 as
>
> ./boot/dts/keystone.dtsi: dma-ranges = <0x8000 0x8
> 0x
> 0x8000>;
> ./boot/dts/keystone.dtsi: dma-ranges;
On 01/08/2015 05:24 PM, Arnd Bergmann wrote:
On Thursday 08 January 2015 14:26:36 Murali Karicheri wrote:
On 01/08/2015 03:40 AM, Arnd Bergmann wrote:
On Wednesday 07 January 2015 17:37:56 Rob Herring wrote:
On Wed, Jan 7, 2015 at 12:49 PM, Murali Karicheri wrote:
+ ret = of_dma_get_
On Thu, 2015-01-08 at 14:36 -0800, Roland Dreier wrote:
> Hi,
>
> So we've managed to find one magic setup and workload that reproduces
> this reliably, and I've done a bit more debugging that leads me to
> believe we probably need Intel's help to really get to the bottom of
> this.
Can you share
On 01/08/2015 05:27 PM, Arnd Bergmann wrote:
On Thursday 08 January 2015 09:56:39 Arnd Bergmann wrote:
There is another interesting case, which is a USB host controller or
something similar behind a PCI bus. These are quite common and also
need to be handled in some form. Let's do just PCI first
On 01/08/2015 05:25 PM, Arnd Bergmann wrote:
On Thursday 08 January 2015 14:52:13 Murali Karicheri wrote:
Could you add this as as a follow up patch as I don't have a platformm
that support IOMMU and as such my understanding of the IOMMU is limited?
I can help test the change to make sure it h
Hi,
So we've managed to find one magic setup and workload that reproduces
this reliably, and I've done a bit more debugging that leads me to
believe we probably need Intel's help to really get to the bottom of
this.
One question though: you mentioned that you saw this behavior until
you turned of
On Thursday 08 January 2015 09:56:39 Arnd Bergmann wrote:
> There is another interesting case, which is a USB host controller or
> something similar behind a PCI bus. These are quite common and also
> need to be handled in some form. Let's do just PCI first for now, but
> be aware that this will co
On Thursday 08 January 2015 14:52:13 Murali Karicheri wrote:
>
> Could you add this as as a follow up patch as I don't have a platformm
> that support IOMMU and as such my understanding of the IOMMU is limited?
>
> I can help test the change to make sure it has no side effect on
> Keystone that
On Thursday 08 January 2015 14:26:36 Murali Karicheri wrote:
> On 01/08/2015 03:40 AM, Arnd Bergmann wrote:
> > On Wednesday 07 January 2015 17:37:56 Rob Herring wrote:
> >> On Wed, Jan 7, 2015 at 12:49 PM, Murali Karicheri
> >> wrote:
> >>
> >>> + ret = of_dma_get_range(np,&dma_addr,&paddr
+Andreas
On Wed, Jan 7, 2015 at 12:53 PM, Will Deacon wrote:
> On Wed, Jan 07, 2015 at 06:35:41PM +, Mitchel Humpherys wrote:
>> On Wed, Jan 07 2015 at 10:04:20 AM, Will Deacon wrote:
>> > On Wed, Jan 07, 2015 at 05:52:46PM +, Mitchel Humpherys wrote:
>> >> On Wed, Jan 07 2015 at 02:13:0
On 01/08/2015 11:06 AM, Will Deacon wrote:
On Wed, Jan 07, 2015 at 06:49:53PM +, Murali Karicheri wrote:
Add of_pci_dma_configure() to allow updating the dma configuration
of the pci device using the configuration from DT of the parent of
the root bridge device.
Signed-off-by: Murali Karich
On 01/08/2015 03:40 AM, Arnd Bergmann wrote:
On Wednesday 07 January 2015 17:37:56 Rob Herring wrote:
On Wed, Jan 7, 2015 at 12:49 PM, Murali Karicheri wrote:
+ ret = of_dma_get_range(np,&dma_addr,&paddr,&size);
+ if (ret< 0) {
+ dma_addr = offset = 0;
+
On 01/07/2015 06:30 PM, Rob Herring wrote:
On Wed, Jan 7, 2015 at 12:49 PM, Murali Karicheri wrote:
Function of_iommu_configure() is called from of_dma_configure() to
setup iommu ops using DT property. This API is currently used for
platform devices for which DMA configuration (including iommu
Hi Antonios,
Tested-by: Eric Auger
Best Regards
Eric
On 01/06/2015 11:48 AM, Antonios Motakis wrote:
> This patch series aims to implement VFIO support for platform devices that
> reside behind an IOMMU. Examples of such devices are devices behind an ARM
> SMMU, or behind a Samsung Exynos Syst
Hello Joonyoung,
On 01/07/2015 10:55 AM, Joonyoung Shim wrote:
>>>
>>> I don't think iommu support and power domain issue are related. I also
>>> get displaying stripes via hdmi but it is just power domain issue
>>> regardless iommu support.
>>>
>>> I observed 8th bit from 0x1445000C register of m
On Fri, Nov 21, 2014 at 03:08:27PM -0700, Alex Williamson wrote:
> I'd like to make vfio-pci capable of manipulating the device exposed
> to the user such that if the host can only support a single MSI
> vector then we hide the fact that the device itself may actually be
> able to support more. Wh
On Wed, Jan 07, 2015 at 06:49:53PM +, Murali Karicheri wrote:
> Add of_pci_dma_configure() to allow updating the dma configuration
> of the pci device using the configuration from DT of the parent of
> the root bridge device.
>
> Signed-off-by: Murali Karicheri
> ---
> drivers/of/of_pci.c
On Thu, Jan 08, 2015 at 08:56:39AM +, Arnd Bergmann wrote:
> On Wednesday 07 January 2015 18:04:41 Murali Karicheri wrote:
> > On 01/07/2015 04:18 PM, Arnd Bergmann wrote:
> > > On Wednesday 07 January 2015 13:49:50 Murali Karicheri wrote:
> > >> PCI devices on Keystone doesn't have correct dma
On 01/07/2015 06:08 PM, Bjorn Helgaas wrote:
On Wed, Jan 7, 2015 at 5:05 PM, Murali Karicheri wrote:
On 01/07/2015 01:49 PM, Murali Karicheri wrote:
PCI devices on Keystone doesn't have correct dma_pfn_offset set. This
patch
add capability to set the dma configuration such as dma-mask,
dma_pf
Hi Thierry,
Generally I agree with the issues you describe in the current design.
One task in our 2015 workplan is to change the whole method amdkfd is loaded, so
it can independently load at any time, regardless of the order of loading
between it and radeon and amd_iommu_v2. To reach that goal,
On Wed, Jan 07, 2015 at 07:29:15PM +, Arnd Bergmann wrote:
> On Wednesday 07 January 2015 18:57:05 Will Deacon wrote:
> > Sorry for the delay on this, I had to do a bit of digging.
> >
> > On Mon, Dec 22, 2014 at 01:36:01PM +, Arnd Bergmann wrote:
> > > Do you think it's possible that we m
On Wednesday 07 January 2015 18:04:41 Murali Karicheri wrote:
> On 01/07/2015 04:18 PM, Arnd Bergmann wrote:
> > On Wednesday 07 January 2015 13:49:50 Murali Karicheri wrote:
> >> PCI devices on Keystone doesn't have correct dma_pfn_offset set. This patch
> >> add capability to set the dma configur
On Wednesday 07 January 2015 17:37:56 Rob Herring wrote:
> On Wed, Jan 7, 2015 at 12:49 PM, Murali Karicheri wrote:
>
> > + ret = of_dma_get_range(np, &dma_addr, &paddr, &size);
> > + if (ret < 0) {
> > + dma_addr = offset = 0;
> > + size = dev->coherent_dm
24 matches
Mail list logo
