On Tue, Mar 06, 2018 at 04:41:56AM +, Nipun Gupta wrote:
> Sorry for asking a trivial question - looking into dma_configure() I see that
> PCI is used in the start and the end of the API.
> In the end part pci_put_host_bridge_device() is called.
> So are two bus callbacks something like
On Wed, Mar 7, 2018 at 5:50 PM, Robin Murphy wrote:
> On 02/03/18 10:10, Vivek Gautam wrote:
>>
>> If we fail after initializing domain_context, we should destroy
>> the context to free up resources.
>
>
> Have another think about why the "problem" this patch caters for
On Wed, Mar 7, 2018 at 6:17 PM, Robin Murphy wrote:
> On 02/03/18 10:10, Vivek Gautam wrote:
>>
>> From: Sricharan R
>>
>> Finally add the device link between the master device and
>> smmu, so that the smmu gets runtime enabled/disabled only when
On Thu, Mar 8, 2018 at 1:58 AM, Robin Murphy wrote:
> On 07/03/18 13:52, Tomasz Figa wrote:
>>
>> On Wed, Mar 7, 2018 at 9:38 PM, Robin Murphy wrote:
>>>
>>> On 02/03/18 10:10, Vivek Gautam wrote:
From: Sricharan R
On Mon, Mar 05, 2018 at 07:59:21PM +0530, Nipun Gupta wrote:
> The existing IOMMU bindings cannot be used to specify the relationship
> between fsl-mc devices and IOMMUs. This patch adds a binding for
> mapping fsl-mc devices to IOMMUs, using a new iommu-parent property.
>
> Signed-off-by: Nipun
On 07/03/18 13:52, Tomasz Figa wrote:
On Wed, Mar 7, 2018 at 9:38 PM, Robin Murphy wrote:
On 02/03/18 10:10, Vivek Gautam wrote:
From: Sricharan R
The smmu device probe/remove and add/remove master device callbacks
gets called when the smmu
On Wed, Mar 7, 2018 at 12:32 AM, Vivek Gautam
wrote:
> Qualcomm's arm-smmu 500 implementation supports runtime pm
> so enable the same.
That's a driver detail unrelated to the binding.
>
> Signed-off-by: Vivek Gautam
> ---
>
> Based on
On Wed, Mar 7, 2018 at 9:38 PM, Robin Murphy wrote:
> On 02/03/18 10:10, Vivek Gautam wrote:
>>
>> From: Sricharan R
>>
>> The smmu device probe/remove and add/remove master device callbacks
>> gets called when the smmu is not linked to its master,
On 06/03/18 03:21, Jeffy Chen wrote:
Add clock property, since we are going to control clocks in rockchip
iommu driver.
Reviewed-by: Robin Murphy
Signed-off-by: Jeffy Chen
Reviewed-by: Rob Herring
---
Changes in v7: None
On 06/03/18 03:02, Jeffy Chen wrote:
Move request_irq to the end of rk_iommu_probe().
Acked-by: Robin Murphy
Suggested-by: Robin Murphy
Signed-off-by: Jeffy Chen
Reviewed-by: Tomasz Figa
---
On 06/03/18 03:02, Jeffy Chen wrote:
Add missing iommu_device_sysfs_remove in error path.
Acked-by: Robin Murphy
(strictly you don't need to introduce the additional return, but it's
only a couple of lines and definitely not worth respinning just for that)
On 06/03/18 03:02, Jeffy Chen wrote:
Removal of IOMMUs cannot be done reliably.
This is similar to exynos iommu driver.
Acked-by: Robin Murphy
Signed-off-by: Jeffy Chen
Reviewed-by: Tomasz Figa
---
Changes in v7: None
On 02/03/18 10:10, Vivek Gautam wrote:
From: Sricharan R
Finally add the device link between the master device and
smmu, so that the smmu gets runtime enabled/disabled only when the
master needs it. This is done from add_device callback which gets
called once when the
On 02/03/18 10:10, Vivek Gautam wrote:
From: Sricharan R
The smmu device probe/remove and add/remove master device callbacks
gets called when the smmu is not linked to its master, that is without
the context of the master device. So calling runtime apis in those
On 02/03/18 10:10, Vivek Gautam wrote:
If we fail after initializing domain_context, we should destroy
the context to free up resources.
Have another think about why the "problem" this patch caters for cannot
ever happen (hint: consider how domain->smmu is used in
[CC Alex Williamson]
It looks like the last patch to this file was taken by Alex.
Perhaps he would be willing to take this one too if it it was
reposted with him CCed.
On Tue, Mar 06, 2018 at 04:55:44PM +, Fabrizio Castro wrote:
> Dear All,
>
> I am very sorry to bother you, do you know who
16 matches
Mail list logo