Hi Lorenzo,
>[+hanjun, tomasz, sinan]
>
>It is quite a key patchset, I would be glad if they can test on their
>respective platforms with IORT.
>
>On Mon, Jan 23, 2017 at 09:48:10PM +0530, Sricharan R wrote:
>> This is an equivalent to the DT's handling of the iommu master's probe
>> with
On 2017/1/24 0:18, Sricharan R wrote:
This series calls the dma ops configuration for the devices
at a generic place so that it works for all busses.
The dma_configure_ops for a device is now called during
the device_attach callback just before the probe of the
bus/driver is called. Similarly
Hi Will,
>Hi all,
>
>A number of people have expressed interest in having the SMMU come up in
>a passthrough configuration, and then allow subsequent translation for
>things such as VFIO. Rather than do this in each SMMU driver, it's much
>cleaner to allow the default domain to be configured to
Hi Lorenzo, Sricharan,
On 01/24/2017 08:37 PM, Lorenzo Pieralisi wrote:
[+hanjun, tomasz, sinan]
It is quite a key patchset, I would be glad if they can test on their
respective platforms with IORT.
ACPI patches are conflict with my acpi platform msi patches (I need
them to enable devices on
Hi Magnus,
On Tue, Jan 24, 2017 at 10:38 AM, Magnus Damm wrote:
> On Mon, Jan 23, 2017 at 9:50 PM, Geert Uytterhoeven
> wrote:
>> On Mon, Jan 23, 2017 at 1:12 PM, Magnus Damm wrote:
>>> From: Magnus Damm
Hi Geert,
On Mon, Jan 23, 2017 at 9:50 PM, Geert Uytterhoeven
wrote:
> Hi Magnus,
>
> On Mon, Jan 23, 2017 at 1:12 PM, Magnus Damm wrote:
>> From: Magnus Damm
>>
>> Match on r8a7795 ES2 and enable a certain DMA
Hi Robin,
>> Consider failure of iommu_get_domain_for_dev() as non-critical and
>> get rid of the warning printout. This allows IOMMU properties to be
>> included in the DTB even though the kernel is configured with
>> CONFIG_IOMMU_API=n or in case a particular IOMMU driver refuses to
>> enable